BNMR: Custom Status page: Difference between revisions

From DaqWiki
Jump to navigation Jump to search
en>Suz
mNo edit summary
en>Suz
mNo edit summary
Line 60: Line 60:
<span style="color: green; background-color: #CCCCCC; font-style:italic; font-size: 90; padding:0.25em;
<span style="color: green; 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;">ShowWindows</span>  
padding-left: 0.5em;padding-right: 0.5em;border:1px solid #808080;border-radius: 5px;margin-bottom:1px;">ShowWindows</span>  
|button opens the page shown in Figure 4.  
|button displays the help information on displaying the frontend and other client consoles.
|}
|}
<br><br>
 
;Figure 4: Client windows page
[[Image:Show_client_windows_page.png|left|thumb]]
<br clear=all>




Line 71: Line 68:
The page update information is also visible in Figure 1. The custom status page updates completely with a full page reload every minute. In between, it updates the information using innerHTML. This is called a partial reload. The time between partial reloads can be set by the user by clicking on the link  "Page update 10 sec (min 5s)"  (Figure 1). This minimum time is 5s.  The ODB data is read each time a partial reload is done. The times of the last ODB data read, last full reload etc are also shown in Figure 1. A countdown to the next full reload is also visible.
The page update information is also visible in Figure 1. The custom status page updates completely with a full page reload every minute. In between, it updates the information using innerHTML. This is called a partial reload. The time between partial reloads can be set by the user by clicking on the link  "Page update 10 sec (min 5s)"  (Figure 1). This minimum time is 5s.  The ODB data is read each time a partial reload is done. The times of the last ODB data read, last full reload etc are also shown in Figure 1. A countdown to the next full reload is also visible.


=== Status Line ===
The Status lines on the Custom Status Page show the status of the run and some of the important settings (Figure 4).
[[Image:Bnqr_status_lines.png|Figure 4:<br>Status lines from the BNQR Custom Status Page]]
<br clear=all>
The first line shows the selected PPG Mode. This changes when the mode is changed by pressing one of the PPG Mode buttons. The run number is shown in yellow for a '''test''' run, green for a '''real''' run (see [[BNMR: Run numbering]]).
{| border="0"  cellpadding="2" cellspacing="2" style="border-collapse:collapse; color:black; background-color:white" 
|-
!Table 2: Run number
!style="color:white"| spacer
!Table 3: Run State
|-
|
{| border="1"  cellpadding="2" cellspacing="2" style="border-collapse:collapse; color:black; background-color:aliceblue" 
|rowspan="2" style="font-weight:bold"|Run number
|style="background-color:lime"| 45059
|style="font-weight:bold"| real
|-
|style="background-color:yellow"| 30102
|style="font-weight:bold"| test
|}
|style="color:white"| spacer
|
{| border="1"  cellpadding="2" cellspacing="2" style="border-collapse:collapse; color:black; background-color:aliceblue" 
|-
| rowspan="3"|Run Status
|style="background-color:red"| Stopped
|-
|style="background-color:yellow"| On Hold
|-
|style="background-color:lime"| Running
|}
|}
The run state is shown (red for stopped, green for running, yellow for [[on hold]]). The time the run started is shown and, if running, the run duration, otherwise the time the run stopped.
The next line shows the Status, which may show an information message.  Below this is a line showing the directory of the saved files. Next are a number of boxes showing important settings. Most are provided with a checkbox so the user can change the values.


; Table 4 Status values
{| border="1" style="border-collapse:collapse; color:black; background-color:aliceblue" 
|+ Status boxes
! Parameter TRUE !! Parameter FALSE !! Checkbox
|-
|style="background-color:yellow"| Single channel mode
|style="background-color:orange"| Dual channel mode || yes
|-
|style="background-color:lime"| Alarms Active
|style="background-color:red"| Alarms Active || yes
|-
|style="background-color:lime"|Helicity Check
|style="background-color:red"| Helicty Check  || yes
|-
|style="background-color:lime"|Helicity Flip
|style="background-color:red"| Helicity Flip|| no
|-
|style="background-color:lime"|Single/Dual Mode<br>Switch Check
|style="background-color:red"| Single/Dual Mode<br>Switch Check || yes
|-
|}


== Programming Information ==
== Programming Information ==

Revision as of 17:08, 28 November 2016

Links

Introduction

When the webserver is used to connect to a MIDAS experiment, the standard MIDAS Status page is shown, unless it has been replaced by a Custom Status page. This is the case for the bnmr and bnqr experiments. A custom page written specifically for the bnmr and bnqr experiments replaces the standard MIDAS Status page. It is called the Custom Status page.

Note that the MIDAS client mhttpd must be running for the webserver to be available. To connect to the Custom Status page, see Getting Started.

Custom Status Page

The custom status page allows users to enter experimental parameters easily, including changing Experimental Modes and run type. A Custom Parameter page accessed from the custom status page allows users to enter run parameters easily. The custom status page for bnmr and bnqr experiments is shown in Figures 1 and 2 respectively.


Click a thumbnail to enlarge


Features of the Custom Status Page

The Custom Status Page provides status information specific to the bnmr or bnqr experiments. The option of reverting to the MIDAS standard status page is provided via the ToggleStatusPage button.

Command and Page Buttons

Figure 3 Command and Page Buttons
In the middle of the top line on the Custom Status page are found the standard Menu buttons to stop and start runs or to display different MIDAS pages. These standard buttons appear on most MIDAS pages (see MIDAS Status page for more information).

Below these buttons are buttons specific to the bnmr and bnqr experiment. Some are customscript buttons, that is, a script is run when the button is pressed. Others switch to a different custom page. The actions of these buttons are described in Table 1.

Table 1: Custom Buttons
Button Action

Autorun

toggles Autoruns on or off
rf_config runs client rf_config to test the validity of the input parameters without actually starting a run
ToggleStatusPage runs a perlscript causing the status page to revert to the standard Midas Status Page. After pressing this button, a popup window with a message "Now refresh page" will appear. After refreshing the page, the MIDAS status page will appear. From this page, the CustomStatus page can be reached by clicking on the custom button CustomStatus button. This will show the Custom status page as a regular Custom page. A message can be seen at the top of the custom page in this case "Using alias link "CustomStatus&" from Midas Main Status Page". To revert to running this page as the Custom Status Page, press the button once more and refresh the page.
RunParams gives access to the Custom Parameter page.

ShowWindows

button displays the help information on displaying the frontend and other client consoles.


Page Update Information

The page update information is also visible in Figure 1. The custom status page updates completely with a full page reload every minute. In between, it updates the information using innerHTML. This is called a partial reload. The time between partial reloads can be set by the user by clicking on the link "Page update 10 sec (min 5s)" (Figure 1). This minimum time is 5s. The ODB data is read each time a partial reload is done. The times of the last ODB data read, last full reload etc are also shown in Figure 1. A countdown to the next full reload is also visible.

Status Line

The Status lines on the Custom Status Page show the status of the run and some of the important settings (Figure 4). Figure 4: Status lines from the BNQR Custom Status Page
The first line shows the selected PPG Mode. This changes when the mode is changed by pressing one of the PPG Mode buttons. The run number is shown in yellow for a test run, green for a real run (see BNMR: Run numbering).

Table 2: Run number spacer Table 3: Run State
Run number 45059 real
30102 test
spacer
Run Status Stopped
On Hold
Running

The run state is shown (red for stopped, green for running, yellow for on hold). The time the run started is shown and, if running, the run duration, otherwise the time the run stopped. The next line shows the Status, which may show an information message. Below this is a line showing the directory of the saved files. Next are a number of boxes showing important settings. Most are provided with a checkbox so the user can change the values.


Table 4 Status values
Status boxes
Parameter TRUE Parameter FALSE Checkbox
Single channel mode Dual channel mode yes
Alarms Active Alarms Active yes
Helicity Check Helicty Check yes
Helicity Flip Helicity Flip no
Single/Dual Mode
Switch Check
Single/Dual Mode
Switch Check
yes

Programming Information

See Custom Pages.