Creating a Test Release

This proceeds in much the same manner as at other sites, for details see the offline work book.

The following instructions have to be followed both in the case you're logged-in our SUN box (babar1) or on one of the two front end PCs of our PC farm (bfa or bfb).
It is recommended that you create your test release within a directory below your home directory. This will ensure that your code gets backed up (a good thing). However the libraries and executable will be very large, so it's best to store them in a scratch area. In order to optimise link times you should use a scratch area which is local to babar1 (or to bfa/b). For this purpose a scratch area has been provided for you in:

/local-scratch/< your-user-name >

For example you could create a test release using the analysis-14 release (based on 12.3.0 release) on bfa. Get an AFS token from RAL typing:

> klog

on babar1, and then supplying your RAL AFS password when prompted. If your RAL AFS user name is different from your local user name then use:

> klog -principal < afs-user-name >

Install the Test Release in your home directory doing the following:

> mkdir $HOME/physics
> cd $HOME/physics
> newrel -t -s /local-scratch/$USER analysis-14 < user-directory >
> cd < user-directory > 
> srtpath analysis-14 Linux24

Then, from the test release directory, do the following:

> gmake installdirs

This comand will make the needed links from your test release directory to the /local-scratch/ directory. Then add the following two packages:

> addpkg workdir
> addpkg BetaUser

The first package contains all the data card files (in BaBar jargon, '.tcl' files) and scripts to run a User job and the second one is the package where you're supposed to implement your analysis user code.

The final step is to go into the workdir/ directory and type:

> gmake setup

This will make the needed links to the bin/ and lib/ directories in your /local-scratch/ area, and the links to the RELEASE directory at RAL (where the release you're importing at RH lives) and PARENT directory (where there's the local copy of the release, that you have just imported).

Moreover, download and source the following file before compiling the BetaUser executable (called BetaApp): this will set some environment variables to enable/disable some MC modules. More informations are available here.