Mlogger: Difference between revisions

From MidasWiki
Jump to navigation Jump to search
No edit summary
(The midas documentation has moved to https://midas.triumf.ca/docs/)
Tag: Replaced
 
(15 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== mlogger - MIDAS Logger ==
The midas documentation has moved. See [https://midas.triumf.ca/docs/develop/reference/reference/programs/#mlogger mlogger] on the Programs and options page and [https://midas.triumf.ca/docs/develop/features/storing_data/data_logging/ Data logging: overview] for the new documentation about the mlogger program.
 
The MIDAS Logger, <span style="color:darkcyan;">''mlogger''</span> is supplied in the MIDAS package. This utility can perform several functions (selected by the user via the
[[/Logger ODB tree]] ) including:
 
* logging System messages to a Message file or as message events
* logging information to a mySQL database
* writing information to an electronic logbook
* collecting and logging history events
* logging experimental data from one or more [[frontend]]s to storage device(s) such as disk or tape
*  multiple Logging Channels can be defined
*    several different storage devices, formats and compression levels can be selected
*        data can be logged to different subdirectories on disk
*        data can be logged to a remote computer, using the FTP mode
*        events can be selected for logging by Event ID or Trigger mask
*        Event Filtering can be implemented
*        runs can be automatically stopped and restarted after a certain number of events, or a certain time
*        the complete ODB contents can be saved
**            into a file at the beginning and/or end of run
**            and/or into the data stream
 
The mlogger utility runs on the backend computer, receiving events from the buffer manager. It supports three type of storage devices so far, i.e.
 
*    Disk,
*    Tape
*    FTP channel to a remote computer.
 
Data can currently be written in five different formats :
 
*    MIDAS binary,
*    ASCII,
*    ROOT
*    DUMP
 
The user may of course write their own custom data logger to save the data in any format they choose.
 
== Starting mlogger utility ==
 
    Arguments
        [-h ] : help
        [-e exptname ] : experiment name (see [[odbedit]] - ODB Editor and run control utility)
        [-D ] : start program as a daemon (UNIX only).
        [-s] : Save mode (debugging: protect ODB).
        [-v] : Verbose (not to be used in conjunction with -D).
    Usage
    >mlogger -D
 
Notes
* When <span style="color:darkcyan;">''mlogger''</span>  is started for the first time, it creates the [[/Logger ODB tree|/Logger]], the [[/History ODB tree|/History]] and the[[/Elog ODB tree| /Elog]] ODB trees with default values.
* The <span style="color:darkcyan;">''mlogger''</span> application requires an existing  [[/Equipment ODB tree]].
* Once <span style="color:darkcyan;">''mlogger''</span> is running, you should be able to monitor its state with [[mstat]] or with [[mhttpd]].

Latest revision as of 22:01, 30 October 2026

The midas documentation has moved. See mlogger on the Programs and options page and Data logging: overview for the new documentation about the mlogger program.