Difference between revisions of "Data Logger"

From MidasWiki
Jump to navigation Jump to search
Line 1: Line 1:
The Midas data logger serves multiple purpose of logging.
+
The Midas [[mlogger|data logger]] serves multiple purposes related to data logging.
# Its main task is to log experimental data to storage device[[Event_Filtering|(s)]], with prior data compression is necessary.
+
# On the fly data compression (if required)
# Serves the logging of the overall Midas system messages
+
# Log experimental data to storage device '''[[Event_Filtering|(s)]]'''
# Collect and log the history events
+
# Handles the overall Midas '''[[Message_System|System messages]]''' logging
# Can log special information to an external mySQL database
+
# Collect and log the history events, see '''[[History System]]''''
 +
# Can log special information to an external mySQL database, see '''[[Logging to a mySQL database|mySQL]]'''
  
The associated utility handling this Data logging is the [[mlogger]]. It runs on the backend computer, receiving events from the buffer manager. It supports three type of storage devices so far, i.e.
+
The data logger configuration is available in the ODB. Please refer to '''[[/Logger ODB tree]]''' for full feature descriptions.
# Disk,
 
# Tape
 
# FTP channel to a remote computer.
 
  
Data can currently be written in five different formats :
+
The actual application handling this Data logging is the '''[[mlogger]]'''. It is intended to run on the backend computer (on the same node where the event buffers reside) for fast data access (no network involved).
* MIDAS binary,
 
* ASCII,
 
* ROOT
 
* DUMP
 
 
 
A built in compression (gzip) can be enabled
 
 
 
 
 
[[/Logger ODB tree]]
 
[[Data Logger]]
 

Revision as of 19:43, 15 February 2014

The Midas data logger serves multiple purposes related to data logging.

  1. On the fly data compression (if required)
  2. Log experimental data to storage device (s)
  3. Handles the overall Midas System messages logging
  4. Collect and log the history events, see History System'
  5. Can log special information to an external mySQL database, see mySQL

The data logger configuration is available in the ODB. Please refer to /Logger ODB tree for full feature descriptions.

The actual application handling this Data logging is the mlogger. It is intended to run on the backend computer (on the same node where the event buffers reside) for fast data access (no network involved).