Difference between revisions of "Data Monitoring Procedures"

From GlueXWiki
Jump to: navigation, search
(Created page with "__TOC__ ==Saving Online Monitoring Data== ==Running Over Archived Data== ==Extracting Monitoring Data==")
 
(Running Over Archived Data)
Line 4: Line 4:
  
 
==Running Over Archived Data==
 
==Running Over Archived Data==
 +
 +
The procedure for writing the data out is given in, e.g.,
 +
[https://halldweb1.jlab.org/wiki/index.php/Raid-to-Silo_Transfer_Strategy 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.
  
 
==Extracting Monitoring Data==
 
==Extracting Monitoring Data==

Revision as of 16:50, 21 October 2014

Saving Online Monitoring Data

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.

Extracting Monitoring Data