acas0XXX.usatlas.bnl.govfarm nodes (XXX is a 3-digit number, for example 001 - 009). There is also the general purpose interactive Linux workstation at
atlas00.usatlas.bnl.govwith larger selection of programs (e.g.
firefox, xfigthat are not installed on
$HOMEvariable. Home directories are backed up but of rather limited size (500 MB is standard). There is a scratch (not backed-up) NFS system at
/usatlas/scratch/<username>for temporary file storage. When the scratch area becomes full the older and larger files are automatically purged. ACF has also established AFS cell,
/afs/usatlas.bnl.gov, for sharing files with remote institutions. Users have personal AFS areas at
/afs/usatlas.bnl.gov/users/<username>and all ATLAS software is installed on AFS.
X,Y,Z=0-9. The "production" ATLAS releases have
Y=0, all other releases are "development". There are also releases of patches named as
1X.0.Z.KLand Physics Analysis releases named as
X,Z,K,L,M,N=0-9). ATLAS software releases depend on many external packages (about 50). The main OO framework, ATHENA, is based on the GAUDI architecture that is technically also an external package. At the U.S. ATLAS Tier I Computing Facility the stable and selected nightly ATLAS software releases are downloaded from pacman distribution kits at
/afs/usatlas.bnl.gov/software/downloads/releases/. In addition ATLAS production releases are installed on NFS by OSG group at
/usatlas/projects/OSG/atlas_app/atlas_relFurther details are available at our page ATLAS software releases and how to use them . An ATLAS software release consists of an install area (
InstallArea) and directories of packages. An install area contains references (soft links) to binaries, includes and share files dispersed in the release tree. ATLAS releases are managed by CMT release tool. The packages are organized according to CMT principles and can be simple packages (with no subpackages) or containers of simple packages and/or subcontainers. A CMT package consists of areas with sources, binaries, and
cmtdirectory with CMT configuration (usually stored in single
requirementsfile). Theoretically CMT allows multiple versions of one package in the release, however in ATLAS releases all packages have a single version.
Please note that this site is a content mirror of the BNL US ATLAS 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 US ATLAS computing account name and password.