Difference: AtlasEdinburghLocalSoftware (15 vs. 16)

Revision 162013-06-03 - WahidBhimji

Line: 1 to 1
 
META TOPICPARENT name="AtlasEdinburghGroup"

Running ATLAS software at Edinburgh

Line: 6 to 6
  This page describes the steps needed to access and run ATLAS software from all local desktops in the Edinburgh group.
Deleted:
<
<

Software access via AFS

AFS (and the corresponding kinit and aklog credential tools) are now available as part of the standard desktop build. Once authenticated the main ATLAS software directory can be accessed by navigating to: /afs/cern.ch/atlas/software

 

Using DQ2, ROOT, Ganga, Panda and Athena Locally.

These packages can be used through ATLASLocalRootBase, this is separate to the particular releases installed below.

Line: 53 to 48
  D3PDs can be stored in /Disk/speyside7/Grid/grid-files (not backed up)
Deleted:
<
<

Local installation

A copy of all the official releases since 15.4.0 are available on our dedicated group storage. For any local analysis and simulation work it is preferred to work with the local copy rather using AFS. This will be become more important once ATLAS jobs can be submitted to the Edinburgh condor batch system.

Current List of Installed Releases

All AtlasProduction kits from 15.4.0 onwards are available on local storage. The latest version available is 15.6.0.

These kits are currently available in the following directory structure:

/Disk/speyside4/atlas/SW/[arch]/[SL-version]/AtlasProduction/[Release-version]/

(e.g. /Disk/speyside4/atlas/SW/x86_64/SL5/AtlasProduction/15.4.0)

All new releases will be installed once the availability announcement has been made via the atlas-releaseKit-announce mail list. Please let me know if anyone needs a local copy of any atlas software for releases before 15.4.0.

Nightly builds

The following nightly development releases are available:

  • 15.X.0-SLHC

These are currently available in the following directory structure:

/Disk/speyside4/atlas/SW/[arch]/[SL-version]/AtlasProduction/nightlies/[Dev-release]/rel[0-6]

(e.g. /Disk/speyside4/atlas/SW/i686/SL4/AtlasProduction/nightlies/15.X.0-SLHC/rel0)

The nightly development software is rotated on a weekly basis through directories rel0 to rel6. A daily cron script (not finalised) will run the necessary pacman commands to retrieve the latest dev releases. A symlink is also available in the [Dev-release] directory to point to the latest release available (also updated daily)

Other nightly releases can be added on request. Please let me know if you need other development releases added to the local filesystem.

SL5 compatibility

SL5 RPMs

The following list of rpms allow SLC4/32bit binaries to be run on SLC5 machines.

  • compat-gcc-34
  • compat-gcc-34-c++
  • compat-gcc-34-g77
  • compat-glibc
  • compat-glibc-headers
  • compat-libf2c-34
  • compat-libgcc-296
  • compat-libstdc++-296
  • compat-libstdc++-33
  • compat-readline43
  • libgfortran-4.1.2
  • lapack-3.0-37.el5
  • ghostscript-8.15.2
  • libXpm-3.5.5
  • glibc-devel-2.5
  • giflib
  • compat-openldap
  • openssl097a-0.9.7a-9.el5_2.1
  • compat-db-4.2.52-5.1

These are all available as part of the standard build.

GCC issues

A different version of gcc is required for the ATLAS software than the one available in the local standard build (which is currently gcc-4.1). The required gcc versions are available in:

/Disk/speyside4/atlas/SW/[arch]/[SL-version]/[gccversion]

e.g. /Disk/speyside4/atlas/SW/i686/SL5/gcc43

To use this version of gcc you will need to source the setup file in the directory:

source /Disk/speyside4/atlas/SW/i686/SL5/gcc43/setup.sh

Submitting local batch jobs

This is currently work in progress. Once the software has been validated for local interactive jobs a request will be put in to central support to attach the ATLAS software area to all workstations running condor. At the present time over 300 nodes are available through this batch system.

Jobs requiring high memory

We are due to have a dedicated ATLAS server in place by the end of October. This machine has up to 48GB available for simulation studies.

Data output

There is a generous amount of local storage available (>10TB) for offline data on our present and new dedicated storage servers. Once the local batch system is attached any job output should be stored on these servers rather than in a home directory or the desktop scratch area. The output location is yet to be defined (it is likely to be atlas/data/*) so suggestions are welcome for how to best order the directory hierarchy.

 

Accessing files from ECDF_LOCALGROUPDISK locally

TFile::Open("root://srm.glite.ecdf.ed.ac.uk//dpm... ")

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