Difference between revisions of "Data Monitoring Procedures"

From GlueXWiki
Jump to: navigation, search
(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==
 
  
 
The procedure for writing the data out is given in, e.g.,
 
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].
 
[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,
 
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
 
and within ~20 min., we will have access to the file on tape at
 
/mss/halld/$RUN_PERIOD/rawdata/RunXXXXXX.
 
/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.
+
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
 +
within a subdirectory for each run.
 +
 
 +
For immediate access to these files, the raid disk files may be accessed directly
 +
from the counting house, or the tape files will be available within ~20 min. of the
 +
file being written out.
 +
 
 +
==Running Over Archived Data==
 +
 
 +
Once the files are written to take 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.
 
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:54, 21 October 2014

Saving Online Monitoring 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.

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 within a subdirectory for each run.

For immediate access to these files, the raid disk files may be accessed directly from the counting house, or the tape files will be available within ~20 min. of the file being written out.

Running Over Archived Data

Once the files are written to take 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