Difference between revisions of "Software Test Data Recon"

From GlueXWiki
Jump to: navigation, search
(Adding a New Run Period)
(Adding a New Run Period)
Line 29: Line 29:
 
</pre>
 
</pre>
  
5) Check to see if the cron job is added to the crontab file.  If not, add it:
+
= Running the Cron Job =
 +
1) Check to see if the cron job is added to the crontab file.  If not, add it:
 
<pre>
 
<pre>
 
ssh gluex@ifarm1102 -Y
 
ssh gluex@ifarm1102 -Y

Revision as of 11:49, 4 October 2016

Overview

  • This is done by a cron job that runs on ifarm1102 on the gluex account.
  • The software scripts can be found in the repository at:
https://halldsvn.jlab.org/repos/trunk/scripts/monitoring/recon_test/

Adding a New Run Period

1) For each new run period, first create a new workflow:

swif create -workflow recon_tests_2016-02

2) Tell that workflow to start running (even though there are no jobs yet: this way all the cron job has to do is add a new job):

swif run -workflow recon_tests_2016-02

3) Pick a full file from a good run (production, status_approved) to analyze. Then, append it to your own local copy of the cron_exec.sh file so that it is processed.

Submit_Job 2016-02 011529 000     #run-period, run#, file#

4) Commit this change to the repository, and update the version on the gluex account.

ssh gluex@jlabl5 -Y
cd /group/halld/Software/scripts/monitoring/recon_test/
svn update

Running the Cron Job

1) Check to see if the cron job is added to the crontab file. If not, add it:

ssh gluex@ifarm1102 -Y
crontab -e
# Add the line found in /group/halld/Software/scripts/monitoring/recon_test/cron_recontest