Logging to a ASCII file: Difference between revisions
Jump to navigation
Jump to search
(Created page with "{{Pagelinks}} ==== Links ==== <div style="column-count:3;-moz-column-count:3;-webkit-column-count:3"> * ODB /Logger tree * keys in the...") |
No edit summary |
||
Line 14: | Line 14: | ||
Under two dedicated subdirectories | Under two dedicated subdirectories | ||
[[Keys in the ODB /Logger/Runlog/ | [[Keys in the ODB /Logger/Runlog/SQL subtree #/Logger/Runlog/SQL/Links BOR | Links BOR ]] and | ||
[[Keys in the ODB /Logger/Runlog/ASCII subtree #/Logger/Runlog/ASCII/Links EOR | Links EOR ]], | [[Keys in the ODB /Logger/Runlog/ASCII subtree #/Logger/Runlog/ASCII/Links EOR | 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 | 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 Page#symbolic link|ODB links]] allowing the user to extend the list with any parameter in the ODB database. | ||
The following example shows a <span style="color: purple;">''/Logger/Runlog/ | The following example shows a <span style="color: purple;">''/Logger/Runlog/ASCII''</span> tree as created by [[mlogger]]. See [[keys in the ODB /Logger/Runlog/ASCII subtree |ODB /Logger/Runlog/ASCII subtree]] for an explanation of the meaning of each key. | ||
=== Example /Logger/Runlog/ | === Example /Logger/Runlog/ASCII subtree === | ||
[local:midas | [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 | |||
Write data BOOL 1 4 | filename STRING 1 80 >99d 0 RWD runlog.log | ||
Links BOR DIR | Links BOR DIR | ||
Run number | 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 | Links EOR DIR | ||
Stop time | 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 | |||
[[Category: Logger Tree]] [[Category:Data Logging]] | [[Category: Logger Tree]] [[Category:Data Logging]] |
Revision as of 03:09, 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