Release installed at TRIUMF from a kit

From ATLAS-TRIUMF

Jump to: navigation, search

Contents

[edit] Introduction

In order to avoid having everyone in the group install every release on their workstation, we are now installing Athena releases under the "atlas" account on trshare.

Note: for LCG compatibility, we have set up a soft link so that /triumfcs/trshare/atlas/software points to /triumfcs/trshare/atlas/AtlasSoftware/AthenaReleases. You may find this useful...

Since quotas were introduced, I have not managed to get the Multi kit to install on trshare. However, it is in the mirror at /triumfcs/trshare/atlas/AtlasSoftware/AtlasMirror/ATLAS.mirror, so you can install it on your own computer if you like.

It is assumed that you have a fairly standard TRIUMF configuration and in particular that you are automounting /triumfcs/trshare. Installing the kit on an NFS-mounted partition is discouraged by the ATLAS software gurus anyway.

Small detail to note: if you are installing on a 64-bit machine, this wiki page is very helpful and necessary.

[edit] This should work for project releases installed on trshare

Copy the create_cmthome.sh setup script to your home directory or some other convenient place. Look for the most recent kit installed in /triumfcs/trshare/atlas/AtlasSoftware/AthenaReleases (to get the most recent cmt version - they are backwards compatible, but not forwards). Suppose it is 12.0.5 and you stored the script in your home directory:

cd /triumfcs/trshare/atlas/AtlasSoftware/AthenaReleases/12.0.5

source ~/create-cmthome.sh 1205

Note that if you already have a ~/cmthome.1205 directory, it will be renamed ~/cmthome.1205.bak. You might want to copy it somewhere safe before running this script a second time, though... If all goes well, it will create a ~/cmthome.1205 directory for you with all the right CMT versions for the kits installed. There are some assumptions (e.g. your test area will be called testarea) so you might want to edit it first if you want something different.

Now, when you log on and want to run Athena, you must set up the runtime environment and everything else for a particular release and project. Here is a setupAthena.sh script which you can modify appropriately. Save it in your home directory, and source it when you want to run Athena. It takes optional arguments for the release, project, cmthome directory extension and cvs checkout method, so you can do

source setupAthena.sh -r 13.0.10 -d clusterMultiSL4 -a ssh -p AtlasProduction
(for example), and it will use release 13.0.10 from the Multi release you installed above, and set up the AtlasProduction project, with CVS checkout using ssh (the alternative is ksh, which sets up Kerberos authentication for checkout).

[edit] If you sometimes run against your own kit and sometimes trshare

In that case, after running create-cmthome.sh, rename the new cmthome directory (e.g. cmthome.trshare or cmthome.localMulti) and change all cmthome in the setupAthena.sh script to cmthome.trshare. Then you can have multiple versions, setupAthena_trshare.sh and setupAthena_local.sh, which just have different ATLAS_ROOT and cmthome.whatever values.

[edit] Obsolete from here on, your mileage may vary

To build or run against these releases, do the following:

[edit] This version should work for releases included in Multi

Recently it has been impossible to install the Multi release on trshare. We are going to try to move to a better scheme, but the simplest solution will probably turn out to be putting the ATLAS.mirror somewhere on the Tier 1 site and installing to local machines from that. So, for now, this does NOT work.

Copy this SetupMultiOnTrshare file to somewhere convenient on your account - if you do not want to modify it, that place should be ~/cmthome, and source it (optionally with the release number) e.g.
source SetupMultiOnTrshare 12.0.2
. As a second option you can specify the project, but only do that if you are an expert... the default is much more forgiving in most cases. To see what releases are available with this script, do
ls -ltr /triumfcs/trshare/atlas/AtlasSoftware/AthenaReleases/Multi/AtlasOffline

[edit] This version works for Monolithic releases (i.e. up to 11.2.0 and including everything on the 11.0.X branch)

Copy this SetupReleaseOnTrshare file to somewhere convenient on your account, and source it (optionally with the release number, e.g. source SetupRelease 11.2.0; currently 11.2.0, 11.0.3, 11.0.4, 11.0.41, 11.0.42 and 11.0.5 are the monolithic releases installed on trshare).

You should now be able to do cd $workdir, which will take you to ${HOME}/AthenaWork/${release} and you can work as you did with releases installed on your own computer.

[edit] This version works (for now) for Project builds (11.3.0 onwards)

NOTE: We no longer have standalone installations of releases included in Multi, so please migrate to the script above; you might want to keep this one, though, in case the same thing happens again which happened for 12.2.0, which for a while was not included in Multi... (it's there now)

Copy this SetupProjectRelease file to somewhere convenient on your account - if you do not want to modify it, that place should be ~/cmthome, and source it (optionally with the release number, e.g. source SetupRelease 11.3.0; currently there are no project-based releases installed on trshare outside Multi. As a second option you can specify the project, but only do that if you are an expert... the default is much more forgiving in most cases). 11.3.0 is not very useful for anything, but functionality is gradually returning as we approach 12.0.0.

By the way... we learned the hard way that if you use csh or tcsh as your main shell, you can't source a zsh/bash/sh script and have it work properly, even if the first line of the script says it is a zsh/bash/sh script. So I'm assuming that you are using bash or zsh, one of the Bourne family of shells.

[edit] Databases

This works much the same as in the instructions set up a local replica database for your private installation, except that the replica is installed on trshare.


[edit] Replica From 12.0.0 On

To use the sqlite replica installed for releases 12.0.0 onward, just use the latest version of the release setup script SetupProjectRelease, and add the following links in your run directories:

ln -s ${DBRELEASE_PATH}2.1/sqlite130 sqlite130
ln -s ${DBRELEASE_PATH}2.1/geomDB geomDB

[edit] SQLite replica (versions 11.X.Y)

To use the sqlite replica with pre-12 releases, add the following lines to the end of your job options:

RDBAccessSvc = Service( "RDBAccessSvc" )
RDBAccessSvc.UseDBConnSvc = FALSE
RDBAccessSvc.Technology   = "sqlite"
RDBAccessSvc.HostName     = "/triumfcs/trshare/atlas/AtlasSoftware/geomDB_sqlite"

[edit] MySQL Server

I have also installed the full MySQL replica rpm (11.0.3 version which as far as I know is the latest) on my machine, isabel. In principle it may be possible to use it from other machines by putting

LArCondCnvDbServer = "isabel"

at the beginning of your job options, before your AtlasGeoModel includes and in particular, before the line include( "AtlasGeoModel/GeoModelInit.py" ).

Then you also have to put these lines at the very end of your job options:

# for server indirection
RDBAccessSvc.UseDBConnSvc = FALSE
RDBAccessSvc = Service( "RDBAccessSvc" )
RDBAccessSvc.Technology   = "mysql"        # or oracle                                                                                     
RDBAccessSvc.HostName     = "isabel"
# SchemaName specifies the schema name for oracle                                                                                    
# and database name for mysql                                                                                                        
RDBAccessSvc.SchemaName   = "ATLASDD"

IOVDbSvc.serverName = LArCondCnvDbServer
# Port specifies the connection port                                                                                                 
RDBAccessSvc.Port         = "3306"
# User specifies the user name                                                                                                       
RDBAccessSvc.User         = "atlasdd_reader"
# Password specifies the password for this user                                                                                      
RDBAccessSvc.Password     = "reader"

# you can always set you OutputLevel
RDBAccessSvc.OutputLevel = 3
IOVDbSvc.OutputLevel = 3

--Isabel 09:50, 23 January 2006 (PST)

--Isabel 14:46, 1 March 2007 (PST) (major revision)

Personal tools