Difference between revisions of "Data Monitoring Procedures"
(→Running Over Archived Data) |
(→Saving Online Monitoring Data) |
||
| Line 2: | Line 2: | ||
==Saving Online Monitoring Data== | ==Saving Online Monitoring Data== | ||
| + | |||
| + | All online monitoring plugins will be run as data is taken. | ||
| + | They will be accessible within the counting house via RootSpy, and | ||
| + | for each run and file, a ROOT file containing the histograms will be saved. | ||
| + | These files will then | ||
==Running Over Archived Data== | ==Running Over Archived Data== | ||
Revision as of 16:51, 21 October 2014
Saving Online Monitoring Data
All online monitoring plugins will be run as data is taken. They will be accessible within the counting house via RootSpy, and for each run and file, a ROOT file containing the histograms will be saved. These files will then
Running Over Archived Data
The procedure for writing the data out is given in, e.g., Raid-to-Silo Transfer Strategy. Once the DAQ writes out the data to the raid disk, cron jobs will copy the file to tape, and within ~20 min., we will have access to the file on tape at /mss/halld/$RUN_PERIOD/rawdata/RunXXXXXX.
At this stage we can run the online plugins on these files to confirm what we were seeing in the online monitoring. Manual scripts, and eventually cron jobs can be set up to look for new run numbers and run the plugin over a sample of files.
