Using Athena at BNL

You will need a computing account at BNL and you will have to create a register a public key. Then you can login to BNL:

>> ssh -X user@atlasgw.bnl.gov
You will be prompted for password for your security key. Once inside the gateway, do:
>> rterm -i
You will be prompted for you BNL account password.

Following the advice of the USATLAS TWiki, my cmthome/requirements file at BNL is

#---------------------------------------------------------------------
set CMTSITE STANDALONE
macro PROJ_RELEASE   "latest" \
         12.0.6         "12.0.6" \
         13.0.30        "13.0.30" \
         13.0.40        "13.0.40" \
         13.1.0         "13.1.0" \
         13.2.0         "13.2.0"

macro PROJ_BASE_RELEASE   "$(PROJ_RELEASE)" \
         13.0.25.2      "13.0.25"

macro PROJ_SUBDIR    "$(PROJ_BASE_RELEASE)" \
         bugfix      "bugfix/$(PROJ_BASE_RELEASE)" \
         dev         "dev/$(PROJ_BASE_RELEASE)"

set SITEROOT /opt/usatlas/kit_rel/${PROJ_SUBDIR}
macro ATLAS_DIST_AREA ${SITEROOT}
macro ATLAS_TEST_AREA ${HOME}/testarea/${PROJ_BASE_RELEASE}
#macro ATLAS_GROUP_AREA "/afs/cern.ch/atlas/groups/PAT/Tutorial/EventViewGroupArea/EVTags-13.0.30.1"
apply_tag oneTest
apply_tag setupCMT
apply_tag setup
apply_tag noCVSROOT
apply_tag 32
use AtlasLogin AtlasLogin-* $(ATLAS_DIST_AREA)
set PATHENA_GRID_SETUP_SH /afs/usatlas.bnl.gov/lcg/current/etc/profile.d/grid_env.sh
macro setup_slc3compat "" \
      gcc323  "/opt/usatlas/kit_rel/SLC3/setup_slc3compat"
setup_script $(setup_slc3compat)
#---------------------------------------------------------------------
I have added the ATLAS_GROUP_AREA line in order to use EventView in release 13.0.30, but for release 13.0.40, the Group Area is not needed and I have commented it out. You should also set the CVSROOT in your .bashrc file so that you can check out packages.
export CVSROOT=/afs/usatlas.bnl.gov/software/cvs
echo "CVSROOT set for BNL to " $CVSROOT

I find it convenient when setting up athena and running jobs, to define the following functions in my .bashrc file:

function setup {
    source ${HOME}/cmthome/setup.sh -tag=$*
    shift
}
function makeit {
    cmt config
    source ./setup.sh
    gmake
}
function run {
    nohup athena.py $* &> $1.log &
    tail -f $1.log
}
Using the above to set up athena, all I have to do is run setup follow by the comma separated tags, e.g.
>> setup 13.0.30,groupArea
or
>> setup 13.0.40

The makeit function, explained in my notes on Checking Out a Package, is used to compile a package.

And to run an athena job, all I do is

>> run example_jobOptions.py
This creates a log file of the athena ouput, example_jobOptions.py.log and prints it to the screen real time using tail -f.

In general, refer to the Computing Workbook for learning how to setup and run athena.

Back to top


-- RyanReece - 11 Jan 2008
Edit | Attach | Watch | Print version | History: r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r2 - 2008-01-11 - RyanReece
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback