Data Logger: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
The Midas data logger serves multiple purpose of logging. | The Midas data logger serves multiple purpose of logging. | ||
# Its main task is to log experimental data to storage device[[Event_Filtering|(s)]] | # Its main task is to log experimental data to storage device[[Event_Filtering|(s)]], with prior data compression is necessary. | ||
# Serves the logging of the overall Midas system messages | # Serves the logging of the overall Midas system messages | ||
# Collect and log the history events | # Collect and log the history events | ||
| Line 17: | Line 17: | ||
A built in compression (gzip) can be enabled | A built in compression (gzip) can be enabled | ||
[[/Logger ODB tree]] | |||
[[Data Logger]] | |||
Revision as of 18:19, 15 February 2014
The Midas data logger serves multiple purpose of logging.
- Its main task is to log experimental data to storage device(s), with prior data compression is necessary.
- Serves the logging of the overall Midas system messages
- Collect and log the history events
- Can log special information to an external mySQL database
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.
- Disk,
- Tape
- FTP channel to a remote computer.
Data can currently be written in five different formats :
- MIDAS binary,
- ASCII,
- ROOT
- DUMP
A built in compression (gzip) can be enabled