Difference between revisions of "Status Page"

From MidasWiki
Jump to navigation Jump to search
Line 22: Line 22:
 
To connect to the MIDAS web server [[mhttpd]] main status page for an experiment see  [[mhttpd#Usage|Usage]]. An example of the status page is shown [[#Example Status Page|below]]. Note that it is possible for the user to set up web access restrictions to the experiment (see [[Security]]).
 
To connect to the MIDAS web server [[mhttpd]] main status page for an experiment see  [[mhttpd#Usage|Usage]]. An example of the status page is shown [[#Example Status Page|below]]. Note that it is possible for the user to set up web access restrictions to the experiment (see [[Security]]).
  
= Refresh =
+
= Page Refresh =
 
It is important to note that the refresh of the Status Page is not "event driven" but is controlled by a timer whose rate is adjustable through the Config button. This means the information at any given time may reflect the experiment state of up to n seconds in the past, where n is the timer setting of the refresh parameter.
 
It is important to note that the refresh of the Status Page is not "event driven" but is controlled by a timer whose rate is adjustable through the Config button. This means the information at any given time may reflect the experiment state of up to n seconds in the past, where n is the timer setting of the refresh parameter.
  
Line 53: Line 53:
 
* [[/Script ODB tree#Script-button|script-buttons]]
 
* [[/Script ODB tree#Script-button|script-buttons]]
 
* [[Frontend user code#Manual Trigger|manually-triggered event]] buttons
 
* [[Frontend user code#Manual Trigger|manually-triggered event]] buttons
* [[alias-buttons]] and [[custom-page-buttons]]
+
* [[/Alias ODB tree#Alias-Button|alias-buttons]] and [[/Custom ODB tree#Custom-Button|custom-buttons]]
  
 
If a  [[Frontend Operation#Frontend|frontend]] contains a [[Frontend user code##Manual Trigger|manually-triggered event]],
 
If a  [[Frontend Operation#Frontend|frontend]] contains a [[Frontend user code##Manual Trigger|manually-triggered event]],
 
this will cause a button to be created on the status page that when pressed, will trigger that event.  
 
this will cause a button to be created on the status page that when pressed, will trigger that event.  
  
In the [[#Example|example]], button
+
In the [[#Example|example]],
 
<span style="color: #444444; background-color: #CCCCCC; font-style:italic; font-size: 90; padding:0.25em;
 
<span style="color: #444444; background-color: #CCCCCC; font-style:italic; font-size: 90; padding:0.25em;
 
padding-left: 0.5em;padding-right: 0.5em;border:1px solid #808080;border-radius: 5px;margin-bottom:1px;">test</span> is a script-button,
 
padding-left: 0.5em;padding-right: 0.5em;border:1px solid #808080;border-radius: 5px;margin-bottom:1px;">test</span> is a script-button,
 
<span style="color: #444444; background-color: #CCCCCC; font-style:italic; font-size: 90; padding:0.25em;
 
<span style="color: #444444; background-color: #CCCCCC; font-style:italic; font-size: 90; padding:0.25em;
padding-left: 0.5em;padding-right: 0.5em;border:1px solid #808080;border-radius: 5px;margin-bottom:1px;">ppg-cycle</span> is a custom-page-button, the other buttons on the line are all alias-buttons.
+
padding-left: 0.5em;padding-right: 0.5em;border:1px solid #808080;border-radius: 5px;margin-bottom:1px;">ppg-cycle</span> is a custom-button, the other buttons on the line are all alias-buttons.
 +
 
 +
 
 +
= Run Status Information =
 +
The run status information displays important information, such as the run status, alarm system status and data directory. The run may also be started/stopped using the button provided. The colour or information changes depending whether the run is active or not (e.g. run elapsed time or run stop time). By default, the experiment name is also shown here. The user may choose to display other useful information in this area (see [[/Experiment ODB tree#Status items subtree|Status items]].
 +
 
 +
The last item in this area is a one-line display of the last Midas message. More messages can be viewed on the Message page.
 +
 
 +
== Equipment Information ==
 +
This area shows the status (by colour) of any  [[Frontend Operation#Equipments in Frontend|defined Equipments]] (unless [[/Equipment ODB tree#Hidden|hidden]]). Green means active, red stopped and yellow disabled. The names of the equipments
 +
are links to the <span style="color: purple; font-style:italic;">/Equipment/<equipment-name>/Variables</span> subtree. If the Equipment sends data to the ODB (see [[/Equipment ODB tree#Log history|Log History]] and  [[Equipment List Parameters#ReadOn|RO_ODB flag]]), clicking on this link will display the contents of the  <span style="color: purple; font-style:italic;">/Equipment/<equipment-name>/Variables</span> subtree  with the name of each variable if the [[/Equipment ODB tree#<Names> subtree|<Names subtree]] has been set up (see example).

Revision as of 13:31, 7 August 2014

Links

Purpose

The purpose of the mhttpd main status page is to allow the user to control and monitor the experiment.

Access the status page

To connect to the MIDAS web server mhttpd main status page for an experiment see Usage. An example of the status page is shown below. Note that it is possible for the user to set up web access restrictions to the experiment (see Security).

Page Refresh

It is important to note that the refresh of the Status Page is not "event driven" but is controlled by a timer whose rate is adjustable through the Config button. This means the information at any given time may reflect the experiment state of up to n seconds in the past, where n is the timer setting of the refresh parameter.

Features of the status page

The status page is divided into several parts

  • Menu Buttons
    • Run Control buttons
    • Page Switch Buttons
    • Optional (user-defined) buttons
  • Run Status information
    • Optional display of status items
    • Optional Run Description and Comment
    • Last system message
  • Equipment Information and Event rates
  • Data Logging Information
  • Active client list


Example Status Page

Main status page of pol experiment


Menu Buttons

The top row of Menu buttons on the main status page include the run control buttons (Start/Stop/Pause/Resume depending on the run state) and the page switch buttons (e.g. Messages, Elog, Alarms, Programs, History, Sequencer, MSCB, Help). Clicking on a page switch button will replace the Status page with the requested page. All the pages contain a Status button to return to the Status page. The ODB button allows the user to access and edit the ODB and the Config button allows the Status page refresh time to be changed.

Not all the available buttons may be visible on the main status page. For example, the MSCB button will only be visible if MSCB support has been built into Midas. Keys in the /Experiment ODB tree controls which menu buttons are visible on the status page. The user may change these as required. The Menu Buttons key lists the buttons to appear on the page. The Start/Stop buttons and Pause/Resume buttons may be suppressed using the Start-Stop Buttons and Pause-Resume Buttons keys respectively.

Optional Buttons

Below the Menu Buttons, there may be up to three rows of optional user-added buttons. These may include

If a frontend contains a manually-triggered event, this will cause a button to be created on the status page that when pressed, will trigger that event.

In the example, test is a script-button, ppg-cycle is a custom-button, the other buttons on the line are all alias-buttons.


Run Status Information

The run status information displays important information, such as the run status, alarm system status and data directory. The run may also be started/stopped using the button provided. The colour or information changes depending whether the run is active or not (e.g. run elapsed time or run stop time). By default, the experiment name is also shown here. The user may choose to display other useful information in this area (see Status items.

The last item in this area is a one-line display of the last Midas message. More messages can be viewed on the Message page.

Equipment Information

This area shows the status (by colour) of any defined Equipments (unless hidden). Green means active, red stopped and yellow disabled. The names of the equipments are links to the /Equipment/<equipment-name>/Variables subtree. If the Equipment sends data to the ODB (see Log History and RO_ODB flag), clicking on this link will display the contents of the /Equipment/<equipment-name>/Variables subtree with the name of each variable if the <Names subtree has been set up (see example).