Installing new ATLAS releases at SLAC
(originally - Originally from Peter Kim, now maintained by Andy Haas )--------------------------------------------------------
EXPERT only! ! ! Ask Andy Haas to install new releases for you!
0) HN/e-news announcement of new release pacman package
https://groups.cern.ch/group/hn-atlas-releaseKitAnnounce/default.aspx ------------------------------------------------------------------
1) Before starting a new install, set up the environment variables
RHEL4-32 bit: built on atlas-prod02.slac.stanford.edu
pacman version = 3.26
AFS: /afs/slac/g/atlas/d/ (currently soft linked to /b/)
export PATH=/bin:/usr/bin:/usr/etc:/usr/afsws/bin:/usr/afsws/etc:/usr/bin/X11:.
source /afs/slac/g/atlas/packages/pacman/3.26/setup.sh
RHEL5-32 bit: built on atlas-prod05.slac.stanford.edu
pacman version = 3.29
AFS: /afs/slac/g/atlas/c/
For some reason, it's necessary to unset PYTHONPATH
export
Code Block |
---|
export PATH=/bin:/usr/bin:/usr/etc:/usr/afsws/bin:/usr/afsws/etc:/usr/bin/X11:. |
...
unset PYTHONPATH |
...
. /afs/slac/g/atlas/packages/pacman/3.29/setup.sh |
...
|
2) Go to the target release partitions, /c/ or /d/.
cd :
Code Block |
---|
cd /afs/slac/g/atlas/ |
...
c (or d)
|
Makes sure there is enough space with '" fs lq * '.
There are 17 more AFS partitions mounted, in addition to the /c/ partition".
If more space is needed, send a request to unix-admin@slac.stanford.edu
(All examples below will assume installation in /c/)
---------------------------------------------------------------
3) Installing base release: x.x.x
Issue the pacman command found in the HN/e-news announcement, and direct to pacman.log
pacman -allow :
Code Block |
---|
pacman -allow any-platform trust-all-caches tar-overwrite |
...
-get http://atlas-computing.web.cern.ch/atlas-computing/links/kitsDirectory/projects/cache:AtlasProduction_ |
...
16_6_ |
...
6_i686_slc5_gcc43_opt |
>> pacman.log &
------------------------------------------------4) Installing AtlasProduction cache: x.x.x.x
After steps 1-3, setup the release:
. ~/reldirs/15
Code Block |
---|
asetup 16.6.6 |
...
|
Issue the pacman command found in the HN/e-news announcement, and direct to pacman.log. For example:
pacman -get then setup the release for cmt:
Code Block |
---|
pacman -get http://cern.ch/atlas-computing/links/kitsDirectory/Production/cache:AtlasProduction_ |
...
16_6_ |
...
6_ |
...
2_i686_slc5_gcc43_opt |
...
cd AtlasProduction/16.6. |
...
6. |
...
2/AtlasProductionRunTime/cmt/ ; cmt config ; cd - |
and do 'cmt config'.
Note2: If the AtlasProduction package requires a new DBRelease, it has to be downloaded manually.
Check the status of the Production cache in the corresponding web page,
http://atlas-computing.web.cern.ch/atlas-computing/projects/releases/status/15.6.5.1/AtlasProduction/
which usually lists the DBRelease version number.
If it uses a new DBRelease version, scp the tar file over from lxplus.cern.ch and
put it in /c/DBRelease/ and "tar -xf" and move it as the way others are.
DBRelease tar files are stored in
/afs/cern.ch/atlas/www/GROUPS/DATABASE/pacman4/DBRelease/
----------------------------------------------5) Problems with release install
Check the postings in https://groups.cern.ch/group/hn-atlas-releaseKitProblem/default.aspx
as others might have similar problems.
Ask Peter or Zach.
If all fails, start a new thread in that forum.
-------------------------------------------------------------------.
pacman documentation : http://atlas.bu.edu/~youssef/pacman/
If you ran out of disk space during an install, manually download the last missing tarball with a command like:
Code Block |
---|
wget http://atlas-computing.web.cern.ch/atlas-computing/links/kitsDirectory/projects/kits/AtlasAnalysis_16_5_0_i686_slc5_gcc43_opt.tar.gz
|
6) When there is an announcement of new AtlasLogin or AtlasSettings
Go to the install area (/c/ in this example) and execute:
Code Block |
---|
pacman -update AtlasLogin |
...
pacman -update AtlasSettings |
They are supposed to be backward compatible, unless stated otherwise.
----------------------------------------------------------------------------
7) Updating pacman:
There are usually ATLAS announcements asking to install a new version.
New version of pacman can be downloaded from BU.:
Code Block |
---|
...
wget http://physics.bu.edu/pacman/sample_cache/tarballs/pacman-latest.tar.gz |
...
tar -xf pacman-latest.tar.gz |
Move the pacman package to /afs/slac/g/atlas/packages/pacman/, go into the new
pacman directory and set up.
Code Block |
---|
...
cd x.xx |
...
source setup.sh |
(Please note that any installs in /c/ or /d/ must stay with the pacman version
that was originally used. pacman does not get updated often, but when it does
it might be a good time to build a new install with it switching between
/c/ and /d/.)
8) Installing manually a DBrelease: check here for what's available
Code Block |
---|
pacman -allow trust-all-caches -get http://atlas.web.cern.ch/Atlas/GROUPS/DATABASE/pacman4/DBRelease:DBRelease-${DBRELEASE_VERSION |
9) Removing a release: (NEVER just use "rm -rf ..." - you'll confuse pacman!)
Code Block |
---|
pacman -remove AtlasProduction_16_0_2_3_i686_slc5_gcc43_opt pacman -remove AtlasProduction_16_0_2_i686_slc5_gcc43_opt |
--------------------------