Scripts for managing ATLAS Test Releases

These scripts help with setting up and using test releases. The setup is slightly different from that documented in the Computing Workbook in that each release has its own cmthome directory, and the requirements file is created from a template (either a default, or one in your main ~/cmthome directory). This allows the setup for each release to be independent without complicated AtlasLogin hacking.

Run with no arguments (except atlmake) or with -h (except atladdpkg) for help.

Example

To set up a release, use

% mkdir ~/testarea/15.6.1
% cd ~/testarea/15.6.1
% ~adye/bin/atlnewrel 15.6.1
% source ~/testarea/15.6.1/cmthome/setup.sh

The generated requirements file includes the release tag by default, so you don't need to specify that whith setup.sh.

For a Production Cache, use, eg.

% ~adye/bin/atlnewrel 15.6.1 15.6.1.6,AtlasProduction

Once again, -tag=15.6.1.6,AtlasProduction is saved in the generated requirements file, so you don't need to remember that on the setup.sh.

% atladdpkg PhysicsAnalysis/AnalysisCommon/UserAnalysis
% atlmake
% cd WorkArea/run
% get_files AnalysisSkeleton_topOptions.py
% athena.py AnalysisSkeleton_topOptions.py

atlmake rebuilds everything. If you change (or add) just one package, you can use pkgmake. They can be run from any directory, so you don't need to move out of WorkArea/run to rebuild.

-- TimAdye - 11-Jan-2010