/opt/usatlas/kit_rel.
source /path_to_kit/cmtsite/setup.sh [or .csh] -tag=release_number[,projectName]
export CMTPATH=${working_directory}:${CMTPATH} for zsh/bash/ksh; setenv CMTPATH ${working_directory}:${CMTPATH} for tcsh source /path_to_kit/AtlasOffline/release_number/AtlasOfflineRunTime/cmt/setup.sh [or .csh] AtlasOffline with your projectName if it is different from AtlasOffline
projectName is optional and it default project is AtlasOffline. The last command sets full run-time environment. The middle one is needed if you like to add your own package on top of the release. For release 13.0.10, path_to_kit is /opt/usatlas/kit_rel/13.0.10.
If no additional package is required, the above setup can be simpler. That is, you can skip the middle step and combine the other two commands:
source /path_to_kit/cmtsite/setup.sh [or .csh] -tag=release_number,setup[,projectName]
projectName must be specified as AtlasProduction for production patched releases such as 13.0.30.5, bnl_cvs or bnl_cmt to use BNL local cvs repository for checkout.
For example, after the kit setup you can check a specific version of package AthenaROOTAccess:
bnl_cmt co -r AthenaROOTAccess-00-00-38-06 PhysicsAnalysis/AthenaROOTAccess
requirements to set up all releases, and ATLAS nightlies.
Please note that this site is a content mirror of the BNL USATLAS TWiki. To edit the content of this page, click the Edit this page button at the top of the page and log in with your BNL USATLAS account.