Difference between revisions of "Automatic Tests of GlueX Software"

From GlueXWiki
Jump to: navigation, search
(add note to indicate group disk location of builds)
Line 3: Line 3:
 
== b1π reconstruction ==
 
== 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/halld_builds/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/halld_builds/2010-08-23.
 +
*: ''(n.b. the jobs now use builds stored ob the group disk in /group/halld/Software/builds/sim-recon/nightly)''
 
* 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 /home/gluex/bin/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 6:00 am on Mondays and Thursdays.
 
* The script run is /home/gluex/bin/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 6:00 am on Mondays and Thursdays.

Revision as of 07:18, 5 October 2012

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/halld_builds/2010-08-23.
    (n.b. the jobs now use builds stored ob the group disk in /group/halld/Software/builds/sim-recon/nightly)
  • The analysis is that described on the HOWTO simulate and analyze b1pi events wiki page. Ten thousand events are generated.
  • The script run is /home/gluex/bin/b1pi_cron.sh. It is scheduled as a cron job for the "gluex" account on jlabl1.jlab.org. The job runs at 6:00 am on Mondays and Thursdays.
  • The programs run are all from the 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:
    • jlabl3.jlab.org (RedHat Enterprise Linux 5)
    • ifarm1102.jlab.org (Linux CentOS 5).
  • Log files of the test are created in the top-level directory, for example, /u/scratch/gluex/halld_builds/2010-08-23/b1pi_jlabl3.log.
  • The tests for the individual platforms are run in separate directories, for example, /u/scratch/gluex/halld_builds/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.
  • The ssh scheme to run on the various platforms is that same as that used by the nightly build.

Single track reconstruction