You are looking at the HTML representation of the XML format.
HTML is good for debugging, but is unsuitable for application use.
Specify the format parameter to change the output format.
To see the non HTML representation of the XML format, set format=xml.
See the complete documentation, or API help for more information.
<?xml version="1.0"?>
<api>
  <query-continue>
    <allpages gapcontinue="Reverse_Engineering_Gene_Regulatory_Networks_by_Integrating_Multiple_Types_of_High-Dimensional_Biological_Datasets" />
  </query-continue>
  <query>
    <pages>
      <page pageid="771" ns="0" title="Refining Concurrency in XINU Operating System for Inter-Core Communication and Non-Blocking Data Structures">
        <revisions>
          <rev contentformat="text/x-wiki" contentmodel="wikitext" xml:space="preserve">'''Project Description'''
----
As the number of multi-core systems in our world grows, it becomes increasingly important for students to work on hardware-supported multi-core systems.  We hope to continue adding functionality to our current XINU operating system with the hopes of open sourcing our multi-core variant in the future for schools everywhere to utilize and build upon.  The focus of this summer will be to overall the current multi-core lock-system in place.

'''Project Goal'''
----
	The Embedded XINU system has given Marquette Students a rare opportunity to learn about multi-core topics with actual hardware to support this functionality.  Since Spring 2018, this has shown to have tremendous results.  As multi-core systems are every where in the world today, this is a huge development.  
	It is because of this, we will work to refine the functionality of embedded, multi-core XINU.  We will do this by reviewing the previous work done and picking up where previous researchers left off with the hopes of continuing to push the boundaries of what Marquette’s system courses can ask of it’s students when designing projects.  
	Long term, I hope to work with my colleagues and Dr. Dennis Brylow to “finish off” all of the core functionality of Embedded XINU with the intention of open-sourcing it.  This is an opportunity to provide other universities with an updated version of XINU which will reach more computing students across the globe.

'''Tentative Milestones'''
----
Week 1: 
* Complete Data Science Bootcamp, Solidify Project, and Meet with XINU team

Week 2-5: 
* Implement proper inter-core communication to prevent race-conditions and deadlocks + Research on Production Grade Concurrency

* Overhaul current Spin-lock solution when working on multiple cores to have it work for a wider variety of scenarios + Continued Research

Weeks 6-10:
*  Implementing Non-Blocking Data Structures into XINU for concurrency without the need for locks + Finish Research Paper</rev>
        </revisions>
      </page>
      <page pageid="855" ns="0" title="Revamping the current state of TABOT">
        <revisions>
          <rev contentformat="text/x-wiki" contentmodel="wikitext" xml:space="preserve">'''Student Researcher:''' [[User:Agebhard|Alex Gebhard]],[[User:JForden | Jack Forden]],[[User:ANakvosaite | Agne Nakvosaite]]

'''Mentor:'''  [[User:Brylow|Dennis Brylow]]

==Project Description :==

The current state of TABOT is to act as an incentive for students. As it stands students submit their code to TABOT which runs a nightly test case script which compares their code output to predetermined result from the correct implementation of the assignment. In the case of a failed testcase, the students incorrect output is appended to their TABOT result email, along with what the expected output should have been. While this system has motivated some students to start their assignments earlier a common theme of feedback from past students is the confusing nature of the TABOT email. Since the current state of the TABOT email only provides students with the expected output, another common complaint is that students don't know what the testcases are actually doing.

Our goal over the summer is to expand upon the currently existing structures that TABOT provides. We additionally want to look into the feasibility of adding a linting script that would promote better &quot;standardized&quot; code. This linting process would promote better coding practices and general readability. Studies have shown that when students adhere to these coding practices there is a notable increase in their grade averages compared to students who do not([https://dl.acm.org/doi/pdf/10.1145/3105726.3106182 Investigating Static Analysis Errors]).

==Project Goals :==
*Create a web-based TABOT website 
*Upon Student submission, testcases would run and be reflected in the website UI
*Upon Student submission, their code is submitted to a linting program that would analyze their code and provide &quot;best coding practice&quot; suggestions on how to improve the readability of their code.
*These suggestions would then be mapped to their submission and each line that flagged in the linter would be correspondingly highlighted in the student's submission(visible in the UI)
*For each linting flag, A student will also be given the link to the syntax error and why it is not the best practice, as a way to provide a real life example of why making the change actually matters.(ex:[https://vald-phoenix.github.io/pylint-errors/plerr/errors/basic/C0103  incorrect variable name])
*Upon demand a student should be able to click on a failed testcase and get a brief synopses of what the testcase is testing.</rev>
        </revisions>
      </page>
    </pages>
  </query>
</api>