Difference between revisions of "Automatic Tests of GlueX Software"

From GlueXWiki
Jump to: navigation, search
(b1π reconstruction)
(b1π reconstruction)
Line 4: Line 4:
 
* The tests are run in the directory /u/scratch/gluex/b1pi on the JLab CUE. Each time the test is run a new directory, named by date, is created in this directory, for example, /u/scratch/gluex/b1pi/2010-08-23.
 
* The tests are run in the directory /u/scratch/gluex/b1pi on the JLab CUE. Each time the test is run a new directory, named by date, is created in this directory, for example, /u/scratch/gluex/b1pi/2010-08-23.
 
* The analysis is that described on the [[HOWTO simulate and analyze b1pi events]] wiki page. Ten thousand events are generated.
 
* The analysis is that described on the [[HOWTO simulate and analyze b1pi events]] wiki page. Ten thousand events are generated.
* The script run is /group/halld/Software/scripts/b1pi_macros/b1pi_cron.sh. It is scheduled as a cron job for the [[GlueX shared account on the JLab CUE|"gluex" account]] on jlabl1.jlab.org. The job runs at 8:00 am on Mondays and Thursdays.
+
* A cron job is scheduled for the [[GlueX shared account on the JLab CUE|"gluex" account]] on jlabl1.jlab.org. The job runs at 8:00 am on Mondays and Thursdays. The script run by the cron daemon is
 +
  /group/halld/Software/scripts/b1pi_macros/b1pi_cron.sh
 
* The programs run are all from the [[Nightly Builds of GlueX Software|nightly build]] done on that day.
 
* The programs run are all from the [[Nightly Builds of GlueX Software|nightly build]] done on that day.
* The one cron job on jlabl1 runs the test on the various platforms, as username gluex, serially. The current platforms are:
+
* The cron job on jlabl1 mentioned above runs the test on the various platforms, as username gluex, serially. On each platform, the script run is
 +
/group/halld/Software/scripts/b1pi_macros/b1pi_one.csh
 +
* The platforms are:
 
** jlabl3.jlab.org (Red Hat Enterprise Linux Client release 5.9)
 
** jlabl3.jlab.org (Red Hat Enterprise Linux Client release 5.9)
 
** ifarm1102.jlab.org (CentOS release 5.3)
 
** ifarm1102.jlab.org (CentOS release 5.3)

Revision as of 12:41, 3 June 2013

Twice a week, tests of the reconstruction code in the sim-recon package are done on several platforms at the lab.

b1π reconstruction

  • The tests are run in the directory /u/scratch/gluex/b1pi on the JLab CUE. Each time the test is run a new directory, named by date, is created in this directory, for example, /u/scratch/gluex/b1pi/2010-08-23.
  • The analysis is that described on the HOWTO simulate and analyze b1pi events wiki page. Ten thousand events are generated.
  • A cron job is scheduled for the "gluex" account on jlabl1.jlab.org. The job runs at 8:00 am on Mondays and Thursdays. The script run by the cron daemon is
 /group/halld/Software/scripts/b1pi_macros/b1pi_cron.sh
  • The programs run are all from the nightly build done on that day.
  • The cron job on jlabl1 mentioned above runs the test on the various platforms, as username gluex, serially. On each platform, the script run is
/group/halld/Software/scripts/b1pi_macros/b1pi_one.csh
  • The platforms are:
    • jlabl3.jlab.org (Red Hat Enterprise Linux Client release 5.9)
    • ifarm1102.jlab.org (CentOS release 5.3)
    • ifarm12s01.jlab.org (CentOS release 6.2)
    • roentgen.jlab.org (Red Hat Enterprise Linux Workstation release 6.3)
  • Log files of the test are created in the top-level directory, for example, /u/scratch/gluex/b1pi/2010-08-23/b1pi_jlabl3.log.
  • The tests for the individual platforms are run in separate directories, for example, /u/scratch/gluex/b1pi/2010-08-23/Linux_Fedora8-i686-gcc4.1.2. The low-level directory name is given from the output of the osrelease.pl script. Output files are all contained in these directories.
  • Plots of selected histograms, both PDF and PNG versions, are archived to a web-accessible directory under /group/halld/www/halldweb1/html/b1pi, with the directory named by date.
  • The ssh scheme to run on the various platforms is that same as that used by the nightly build.

Single track reconstruction