(Note this is what we have been calling "Run Control" in LBNE, but I have tried to avoid that term, because we have separated out the monitoring and control of individual DAQ processes inside artDAQ to the artDAQ section of these web pages (for now)).
The user interface is a mainly web-based control program, that allows the runs to be started and stopped, configuration changes to be made, and monitoring information (on the DAQ and the slow controls to be viewed). The aim is to have a one-stop portal to the whole detector to facilitate remote access for shift taking, expert intervention and general status information on the experiment. This has the advantage that access conrol (passwords etc.) can be done in one place, and can allow the system to prevent multiple people from having control at the same time (avoid them changing in a bad combination). Behind the scenes, the user interface is using a database driven web content management system, incuding the database tables with historical run information, configuration settings and DAQ/slow control monitoring variables. This group is also responsible for transfering the history information in these databases into the databases needed for the offline.
While we are busy setting up other groups, this one could (if needed) take a pause for a few weeks still. After that, we need to start with requirements for the User Interface for protoDUNE, and also look at possible synergy between the single and dual phase parts of ProtoDUNE.
Add Erik B's demo link + any info on IceCUBE run control interface. Add Django links
ddWe don't have a wiki website that has authoristion for lots of users yet, so we are using the following shared google-docs page (add once we are on sharepoint and have a password for this page. We want to hear your comments of fixes/additiomns to this page. For now, please E-mail them to Giles, sorry this is not very good.