Difference between revisions of "Automatic Tests of GlueX Software"

From GlueXWiki
Jump to: navigation, search
Line 3: Line 3:
 
* The tests are run in the directory /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, /scratch/gluex/halld_builds/2010-08-23.
 
* The tests are run in the directory /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, /scratch/gluex/halld_builds/2010-08-23.
 
* The analysis is that described on the [[HOWTO simulate and analyze b1pi events]] wiki page. One thousand events are generated.
 
* The analysis is that described on the [[HOWTO simulate and analyze b1pi events]] wiki page. One 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 ifarml3.jlab.org. The job runs at 6:00 am on Mondays.
+
* 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 ifarml3.jlab.org. The job runs at 6:00 am on Mondays and Thursdays.
 
* 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.
 
* One cron job on ifarml3 runs the builds on the various platforms, as username gluex, serially. The current platforms are:
 
* One cron job on ifarml3 runs the builds on the various platforms, as username gluex, serially. The current platforms are:

Revision as of 13:35, 2 June 2011

Once a week, a test of the reconstruction code in the sim-recon package is done on several platforms at the lab.

  • The tests are run in the directory /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, /scratch/gluex/halld_builds/2010-08-23.
  • The analysis is that described on the HOWTO simulate and analyze b1pi events wiki page. One 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 ifarml3.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.
  • One cron job on ifarml3 runs the builds on the various platforms, as username gluex, serially. The current platforms are:
    • ifarml5.jlab.org (Fedora 8)
    • jlabl3.jlab.org (RedHat Enterprise Linux 5)
    • ifarml6.jlab.org (CentOS 5).
  • Log files of the test are created in the top-level directory, for example, /scratch/gluex/halld_builds/2010-08-23/b1pi_jlabl3.log.
  • The tests for the individual platforms are run in separate directories, for example, /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.