Difference between revisions of "Software Test Data Recon"
From GlueXWiki
(→Adding a New Run Period) |
(→Output Files) |
||
| (7 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
= Overview = | = Overview = | ||
| − | * This is done by a cron job that runs on | + | * This is done by a cron job that runs on ifarm1101 on the gluex account. |
* The software scripts can be found in the repository at: | * The software scripts can be found in the repository at: | ||
<pre> | <pre> | ||
https://halldsvn.jlab.org/repos/trunk/scripts/monitoring/recon_test/ | https://halldsvn.jlab.org/repos/trunk/scripts/monitoring/recon_test/ | ||
</pre> | </pre> | ||
| + | |||
| + | = Initialization = | ||
| + | * First, the workflow "recon_tests" was created for the gluex account. | ||
| + | * Next, this workflow was told to start running, even without any jobs: this way all the cron job has to do is add a new job | ||
= Adding a New Run Period = | = Adding a New Run Period = | ||
| − | '''1 | + | '''1)''' Pick a full file from a good run (production, status_approved) to analyze. Then, add it to the list near the end of your own local copy of the cron_exec.sh file so that it is processed. |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
<pre> | <pre> | ||
Submit_Job 2016-02 011529 000 #run-period, run#, file# | Submit_Job 2016-02 011529 000 #run-period, run#, file# | ||
</pre> | </pre> | ||
| − | ''' | + | '''2)''' Commit this change to the repository, and update the version on the gluex account. |
<pre> | <pre> | ||
ssh gluex@jlabl5 -Y | ssh gluex@jlabl5 -Y | ||
| Line 30: | Line 24: | ||
= Running the Cron Job = | = Running the Cron Job = | ||
| − | 1) Check to see if the cron job is added to the crontab file. If not, add it: | + | '''1)''' Check to see if the cron job is added to the crontab file. If not, add it: |
<pre> | <pre> | ||
| − | ssh gluex@ | + | ssh gluex@ifarm1101 -Y |
crontab -e | crontab -e | ||
# Add the line found in /group/halld/Software/scripts/monitoring/recon_test/cron_recontest | # Add the line found in /group/halld/Software/scripts/monitoring/recon_test/cron_recontest | ||
| + | </pre> | ||
| + | |||
| + | = Output Files = | ||
| + | * The location of the output files is determined by the job setup script | ||
| + | <pre> | ||
| + | /group/halld/Software/scripts/monitoring/recon_test/jobs_recon_test.config | ||
</pre> | </pre> | ||
Latest revision as of 16:47, 28 June 2017
Contents
Overview
- This is done by a cron job that runs on ifarm1101 on the gluex account.
- The software scripts can be found in the repository at:
https://halldsvn.jlab.org/repos/trunk/scripts/monitoring/recon_test/
Initialization
- First, the workflow "recon_tests" was created for the gluex account.
- Next, this workflow was told to start running, even without any jobs: this way all the cron job has to do is add a new job
Adding a New Run Period
1) Pick a full file from a good run (production, status_approved) to analyze. Then, add it to the list near the end of 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#
2) 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@ifarm1101 -Y crontab -e # Add the line found in /group/halld/Software/scripts/monitoring/recon_test/cron_recontest
Output Files
- The location of the output files is determined by the job setup script
/group/halld/Software/scripts/monitoring/recon_test/jobs_recon_test.config
