Difference between revisions of "Offline Monitoring Incoming Data"

From GlueXWiki
Jump to: navigation, search
(Created page with "== Saving Online Monitoring Data == The procedure for writing the data out is given in, e.g., [https://halldweb.jlab.org/wiki/index.php/Raid-to-Silo_Transfer_Strategy Raid-to...")
 
Line 18: Line 18:
  
 
== Offline ==
 
== Offline ==
<!--
 
=== Setting up the environment ===
 
The file
 
/home/gxproj1/setup_jlab.csh
 
is sourced through .tcshrc.
 
This file is the same as what is linked to by
 
/home/gluex/setup_jlab_commissioning.csh,
 
except HALLD_HOME, HDDS_HOME, and JANA_CALIB_URL are set separately so that this
 
user can have a separate build.
 
 
To obtain the builds from the previous Friday's runs,
 
execute
 
/home/gxproj1/halld/monitoring/newruns/setup_previous.sh [year] [month] [day]
 
The build revisions from the previous Friday are archived in files
 
/work/halld/data_monitoring/run_conditions/soft_comm_[year]_[month]_[day].xml
 
and the script will build libraries based on those stored revision numbers.
 
-->
 
  
 
<!--
 
<!--
=== Using cron to run automatically ===
 
Within /home/gluex/halld/monitoring/cron/ there is a file cron_plugins
 
that can be executed via
 
crontab cron_plugins
 
This will set up a cron job to call the script scan_for_jobs.sh, which will
 
check in the rawdata directory and call generatejobs_plugins_rawdata.sh for
 
any run that is more than 5 min old. The cron job is set up to run every 10 min.
 
-->
 
 
 
=== Running the cron job ===
 
=== Running the cron job ===
  
Line 73: Line 47:
 
crontab -r
 
crontab -r
 
</pre>
 
</pre>
 
<!--
 
The cron job will run the script scan_for_jobs.sh,
 
which runs generatejobs_plugins_rawdata.sh for any
 
new runs that it had not seen before. All previous
 
runs are recorded in the file filelists/files_current.txt
 
so clear this to run over runs, or set the parameters
 
MINRUN and MAXRUN which will set the range of runs submitted.
 
 
-->
 
-->

Revision as of 17:10, 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