How To Run QaBetaTools?

Under Construction 

•  To obtain a working release 10.0.0 for running the QaBetaTools package you need to do the following steps :

If you're unfamiliar with manipulating BaBar releases, first follow at least the " Logging In" and "Quick Tour" sections of the BaBar Offline Workbook to get started, and pick up the instructions below at "addpkg QaBetaTools".
These instructions are aimed mainly at people who are testing a production release. If standard data is not already available to test, and you are a member of the QA group, refer to the instructions for QA's use of ProdTools to generate it. QA test collections should normally be available early in the test cycle of new releases (8.5 and later).

The assembly method for BetaApps was changed in release 8.5 and these instructions are still preliminary! Instructions for an earlier version can be found here.

You'll find it convenient to have a pointer to your BaBar work space, eg:
setenv MYWORK $BFROOT/work/d/dyaeb
newrel -s $MYWORK -t 10.0.0 my10.0.0
cd my10.0.0
srtpath 10.0.0 SunOS5
    (you will have to choose the machine architecture)
NOTE: as of March 2001 tersk is SunOS5.7 while shire is SunOS5.6

the sp3testboot alias points you to the SP3 Test federation, where the test data for this example resides.
Test collections are announced in the IR2 Production Meeting HN forum and are generally kept on disk for a limited time (~2 weeks).

you need a functional workdir :
addpkg workdir
cd workdir
gmake setup
cd ..

then you can add QaBetaTools :
addpkg QaBetaTools V00-01-57

Now you have two options:

• build an executable to run on RECO


Don't miss setting BetaMC, it _may_ still be needed at run-time!
setenv BetaMC yes

depending on your default setup and what is already in your test release, what you want to accomplish, and Beta defaults which change from time to time only some of the following may be necessary. Non-experts beware!
setenv BetaDisplayMicro no
setenv BetaDisplayAll no
setenv BetaFBogus no
setenv BetaKanga no
setenv BetaSim yes
setenv BetaReco yes
setenv BetaMCAll yes
setenv BetaBdbAll yes
setenv BetaPhysAll yes
 
 

• build an executable to run on MICRO


You will need to set the following environment variables:
unsetenv BetaMC
setenv BetaDisplayMicro no
setenv BetaDisplayAll no
setenv BetaFBogus no
setenv BetaKanga no
setenv BetaSim no
setenv BetaReco no
setenv BetaMCAll no
setenv BetaMCMicro yes
setenv BetaBdbAll no
setenv BetaBdbMicro yes
setenv BetaPhysAll no
setenv BetaPhysMicro yes
 

Whatever you did above, the following should be done.
gmake clean
The following is also needed if you want to debug any of your code
setenv ROPT -noOptimize
bsub -q bldrecoq -o gmake.log gmake lib
but if you're working with optimised libraries, you must link with the optimisation flag set...
unsetenv ROPT
bsub -q bldrecoq -o gmake.log gmake QaBetaTools.all
cd QaBetaTools

•  Now you need to edit the script, SendQaBetaJobs, which runs QaBetaTools automatically.

Features of the script, provided by Mehdi, include :
• the user can specify a set of QA modules to be executed, interactively or in batch
• the staging of default (or user-specified) runs for each module is automated
• different forms of input can be accommodated by setting the type of tcl script to be run
• the output (.bout and .hbook files) is written to a user-specified directory
There are a number of options which you must set first. It's also possible to run these jobs directly from a workdir. In any case, refer to SendQaBetaJobs for guidance.

• Execute the QaBetaTools package as follows:

 

 

SendQaBetaJobs 10.0.0

you can check the progress of the jobs with
bjobs
bpeek (jobnumber)
 

• Viewing the Results

 

 

The output files are written below the directory you specified with the MGR environment variable in SendQaBetaJobs, eg.
ls $MYWORK/Qa10.0.0/SunOS5/QaBetaMassPeaks/

Aslund@
PARENT@
QaBetaMassPeaks.kumac
QaBetaMassPeaks150910.bout
QaBetaUtils.kumac@
RELEASE@
bfield.dat@
crnEvent.data@
dat@
db@
efficiency
gp0.f@
kumac@
last.kumac
my.log
qabeta@
reco150910.hbook
runtime.db
runtime.input
seed

The .bout file shows the log of the job, and can be checked to see that the job completed successfully.
The hbook file can be checked in PAW with the kumac which is provided. Refer to part (2) of the QaBetaTools/ /BFROOT/www/Computing/Programming/QA/QaBetaTools/README_AutoQaBeta document for specific instructions for each type of job.

---

For any comments