Difference between revisions of "Offline Monitoring Incoming Data"
From GlueXWiki
(→Offline) |
|||
| Line 18: | Line 18: | ||
== Offline == | == Offline == | ||
| + | * The scripts for processing the incoming data are stored in svn at: | ||
| + | <pre> | ||
| + | https://halldsvn.jlab.org/repos/trunk/scripts/monitoring/incoming/ | ||
| + | </pre> | ||
| + | |||
| + | * If not already running, the cron job can be launched by running: | ||
| + | <pre> | ||
| + | crontab cron_incoming | ||
| + | </pre> | ||
<!-- | <!-- | ||
Revision as of 17:21, 3 February 2016
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.
Offline
- The scripts for processing the incoming data are stored in svn at:
https://halldsvn.jlab.org/repos/trunk/scripts/monitoring/incoming/
- If not already running, the cron job can be launched by running:
crontab cron_incoming
