Data Logger: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
The Midas [[mlogger|data logger]] serves multiple purposes related to data logging. | The Midas [[mlogger|data logger]] serves multiple purposes related to data logging. | ||
# On the fly data compression (if required) | # On the fly data compression (if required) | ||
# 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 events, see '''[[History System]]'''' | ||
Revision as of 18:43, 15 February 2014
The Midas data logger serves multiple purposes related to data logging.
- On the fly data compression (if required)
- Log experimental data to storage device(s)
- Handles the overall Midas System messages logging
- Collect and log the history events, see History System'
- 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).