Logging to a ASCII file: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 3: | Line 3: | ||
==== Links ==== | ==== Links ==== | ||
<div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"> | <div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"> | ||
* [[mlogger]] | |||
* [[keys in the ODB /Logger tree | ODB /Logger tree ]] | * [[keys in the ODB /Logger tree | ODB /Logger tree ]] | ||
* [[keys in the ODB /Logger/Runlog/SQL subtree |ODB /Logger/Runlog/SQL subtree]] | * [[keys in the ODB /Logger/Runlog/SQL subtree |ODB /Logger/Runlog/SQL subtree]] | ||
* [[keys in the ODB /Logger/Runlog/ASCII subtree |ODB /Logger/Runlog/ASCII subtree]] | * [[keys in the ODB /Logger/Runlog/ASCII subtree |ODB /Logger/Runlog/ASCII subtree]] | ||
</div> | </div> | ||
Latest revision as of 03:11, 17 November 2022
Links
The MIDAS logger (mlogger) is able to record information in an ASCII file.
Under two dedicated subdirectories Links BOR and Links EOR , 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 elements are ODB links allowing the user to extend the list with any parameter in the ODB database.
The following example shows a /Logger/Runlog/ASCII tree as created by mlogger. See ODB /Logger/Runlog/ASCII subtree for an explanation of the meaning of each key.
Example /Logger/Runlog/ASCII subtree
[local:midas]Runlog>ls -lr ASCII
Key name Type #Val Size Last Opn Mode Value
ASCII DIR
Write data BOOL 1 4 >99d 0 RWD n
filename STRING 1 80 >99d 0 RWD runlog.log
Links BOR DIR
Run number -> /Runinfo/Run number
INT32 1 4 11h 0 RWD 1517
Start time -> /Runinfo/Start time
STRING 1 32 11h 0 RWD Mon Oct 31 13:39:21 2022
Links EOR DIR
Stop time -> /Runinfo/Stop time
STRING 1 32 3h 0 RWD Tue Nov 8 09:27:59 2022
Comment -> /Experiment/Edit on start/Comment
STRING 1 128 11h 0 RWD FEP Hit Finder