Keys in the ODB /Logger tree
See also /Logger ODB tree and the MIDAS logger utility mlogger.
/Logger/Channels subtree
Type: DIR
This is a subdirectory under the /Logger ODB tree which contains settings for individual logging channels. By default, only channel "0" is created, but multiple logging channels can be created. See Keys in the ODB /Logger/Channels tree.
/Logger/Data dir
Type: STRING
Default: Path of experiment given in exptab
This key specifies in which directory files produced by the MIDAS logger utility (mlogger) should be written. Once mlogger is running , the key Data dir will be pointing to the location of
- the data file(s) (unless overruled by the Filename key(s) ),
- the message log file (unless overruled by Message File),
- the ODB dump files (unless overruled by ODB Dump File),
- and the optional
- elog files (unless overruled by Elog dir),
- history files (unless overruled by History Dir)
When multiple logging channels are enabled, by default, the data path for all the defined logging channels is set to the same location, given by the Data dir key. However, the data from individual logging channels can also be saved in different locations, using the ODB key /Logger/Channels/<channel-number>/Settings/Filename for each defined logging channel (channel number 0,1...).
The Filename key for each enabled logging channel can contain the full path of the location of the .mid, .ybs, .asc data file.
If the latter key contains the full directory path (i.e. contains the OS specific DIR_SEPARATOR (e.g. "/" for Linux or "\" for Windows), then the global key Data dir will be overruled by the setting for that particular channel.
For example,
- If key Filename contains "run%05.mid". key Data dir will not be overruled
- If key Filename contains "/data1/ch1log/run%05.mid". key Data dir will be overruled
/Logger/Message File
Type: STRING
Default: midas.log
Specifies the filename of the MIDAS Message log file .
/Logger/Auto restart
Type: BOOL
Default: "n"
When this flag is set to "y" (i.e. TRUE), a new run is automatically restarted when the previous run has been stopped by the MIDAS logger (mlogger) due to an event or byte limit.
/Logger/Auto restart delay
Type: INT
Default: 0
Providing Auto restart key is set TRUE, the automatic start of the next run will be delayed by this number of milliseconds.
/Logger/Run duration
Type: INT
Default: 0
This key allows for runs with a certain duration. To use this option, the user creates and sets this variable to a non-zero integer value (in seconds). After a run has lasted for this duration, it will be stopped automatically by the MIDAS logger (mlogger). To automatically produce sequences of runs all with the same duration, also set the
/Logger/Auto restart key to "y"
/Logger/Write data
Type: BOOL
Default: "y"
Data logging is enabled when this key is set to "y". It can be set to "n" (FALSE) temporarily to make a short test run without data logging.
This key is a predefined key for enabling data logging.
Note that the Active key Active key (in the appropriate logging channel subtree must also be set to "y" for the data from that channel to be logged.
/Logger/ODB Dump
Type: BOOL
Default: "n"
If this flag is set to "y", a dump of the complete ODB will be written to the file specified by
ODB Dump file at the end of each run.
- The ODB contents is always saved into a file "last.xml" at the beginning of each run regardless of the setting of this key.
- The ODB contents can also be saved into the data stream as an event (see ODB Dump per logging channel).
/Logger/ODB Dump File
Type: STRING
Default: run%05d.odb
Specifies the filename in which the dump of the complete ODB will be written at the end of each run if the ODB Dump key is set to "y". If this filename has the extension ".xml" or ".XML" the file will be written in XML format, otherwise in ASCII format. For a description of the format see db_copy_xml() or db_copy()respectively.
If this filename contains a "%", the "%" will be replaced by the current run number (cf. format string of printf() C function). The format specifier "%05d" from the example would be evaluated to a five digit run number with leading zeros e.g. run00002.odb. The ODB dump file can be used for off-line analysis to check run parameters etc. (See also ODB Dump per logging channel).
- Note: The location of the ODB dump files can also be specified in this field. If the ODB Dump File string contains a DIR_SEPARATOR, it is considered as an absolute path. If no DIR_SEPARATOR is present, the dump file will be written to the location given by Data dir key.
/Logger/WriteFileHistory
Type: BOOL
Default: "y"
New feature - no information as yet.
/Logger/Tape message
Type: BOOL
Default: "y"
If set to "y", MIDAS messages during mounting tapes and writing of EOF marks are generated. This can be useful all users in a counting house to be informed about the tape status.
/Logger/ODBC Debug
Type: INT
Default: "y"
Optional key created if ODBC is installed (see Building Options). Used by the MIDAS SQL History system. Set to 1 to see all SQL commands. Default value is 0.
/Logger/ODBC DSN
Type: STRING
Default: ""
Optional key created if ODBC is installed (see Building Options). Default value is blank. See MIDAS SQL History system for details.
/Logger/History dir
Type: STRING
Default:
This optional key is used to reassign the location of the saved history files from the default location given by the Data dir key.
/Logger/Elog dir
Type: STRING
Default:
This optional key is used to reassign the location of the saved Elog files from the default location given by the Data dir key.
/Logger/Subrun duration
Type: INT
Default:
This optional key contains the duration in seconds for each subrun. After this time, a new subrun will be started by the MIDAS logger mlogger.
/Logger/Next subrun
Type: BOOL
Default: "n"
This key allows the user to manually request a new subrun. The MIDAS logger (mlogger) will stop the present subrun and start a new one. The key Next subrun will be set false.
/Logger/SQL subtree
Type: DIR
Optional directory for Logging to a mySQL database. This ODB subtree will be created if mySQL support has been built into the MIDAS logger.