Difference between revisions of "Data Logger"

From MidasWiki
Jump to navigation Jump to search
Line 3: Line 3:
 
# Log experimental data to storage device'''[[Event_Filtering|(s)]]'''
 
# Log experimental data to storage device'''[[Event_Filtering|(s)]]'''
 
# Handles the overall Midas '''[[Message_System|System messages]]''' logging
 
# Handles the overall Midas '''[[Message_System|System messages]]''' logging
# Collect and log the history events, see '''[[History System]]''''
+
# Collect and log the '''[[History System|history events]]'''  
# Can log special information to an external mySQL database, see '''[[Logging to a mySQL database|mySQL]]'''
+
# Can log special information to an external '''[[Logging to a mySQL database|mySQL]]''' database
  
 
The data logger configuration is available in the ODB. Please refer to '''[[/Logger ODB tree]]''' for full feature descriptions.
 
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).
 
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).

Revision as of 19:44, 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
  5. Can log special information to an external mySQL database

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).