Search results

The purpose of the [[mhttpd]] Start page is to ...Edit-on-start Parameters]]'' for the user to optionally edit, prior to the run starting.

== Note on Programs auto start, auto stop, auto restart == ...n has been added to the documentation on page [[/Programs ODB tree]] (Auto start,Auto stop, Auto restart).

* [[Edit-on-start Parameters]] ...is started (similar to the [[Edit-on-start Parameters]] that appear when a run is started). Edit-on-sequence parameters may be defined in the

...or: purple;">''/Logger/Runlog/ASCII''</span> ODB subtree is a subdirectory of the [[/Logger ODB tree]]. The ODB <span style="color: purple;">''/Logger/Ru ...DB that are to be saved in the ASCII file at Begin-of-run and or at End-of-run.

* [[Run States and Transitions]] ..."Start" and "Stop" are issued from the [[ODB|ODBedit command]]. Refer to [[Run States and Transitions]] for more details.

about the state of the current run. Several time fields are available for run time statistics. Run number INT 1 4 2h 0 RWD 8521

predefined links exist which will be used at begin-of-run (BOR) and end-of-run (EOR) respectively for storing parameter values into an ASCII file. These e ...tree |ODB /Logger/Runlog/ASCII subtree]] for an explanation of the meaning of each key.

=== Creation of run log file === ..., number of events, hardware settings etc. One possibility is to write the run log to a MySQL database through the ODB settings as described under [[Loggi

* mhttpd [[Start Page]] When a run is started, by default only the

* key <span style="color:purple; font-style:italic">Execute on start run</span> * key <span style="color:purple; font-style:italic">Execute on stop run</span>

Three Run States define the states of the MIDAS DAQ system: [[File:Transition.gif|center|frame|Representation of run states and associated transitions]]

...olor: purple;">''/Logger/Runlog/SQL''</span> ODB subtree is a subdirectory of the [[/Logger ODB tree]]. The ODB <span style="color: purple;">''/Logger/Ru The following sections explain the purpose of the keys in this subtree.

...ual data files. This feature might be helpful if a data file from a single run gets too large (>4 GB for example) and if shorter runs are not wanted for e ** or after a certain '''number of bytes''' :

...tyle:italic;">/Logger</span> ODB tree are used to '''customize logging''' of the data. There are also keys to customize the [[Message System |Messaging] ODB Dump File run%05d.json

...log.log''' file handled by the [[MIDAS Analyzer]]. The two main advantages of using the SQL are: * The recording is done by the logger and therefore is independent of the user analyzer.

...log.log''' file handled by the [[MIDAS Analyzer]]. The two main advantages of using the SQL are: * The recording is done by the logger and therefore is independent of the user analyzer.

This key in the [[#top|/System ODB tree]] controls the format of the prompt of the [[odbedit]] utility. The default prompt is The meanings of the prompt symbols are

...Sequencer Page, [[Sequencer|Sequencer scripts]] can be loaded, edited and run. : As of summer 2018, the sequencer runs as a separate process and must be started b

...ont-style:italic">Command</span> directory allows for programmatic control of the Sequencer. ...</span> ODB tree is created the first time that the msequencer program is run. It will be filled with default values.

The purpose of the [[mhttpd]] status page is to allow the user to control and monitor the ...ent can be accessed from the web (see [[mhttpd#Usage|usage]]). An example of the status page is shown in [[#Figure 1|Figure 1]]. By default, anyone can