= Group Setup =

The most important thing to know is your main computer group. id shows the main group after gid. If your main group is atlas the standard atlas setup will be done automatically when you log intot an atlas computer. Otherwise you have to source the following file:

=== Using bash ===
{{{
source /afs/desy.de/group/atlas/etc/login.sh
export PATH=/afs/desy.de/group/atlas/bin:$PATH 
export LD_LIBRARY_PATH=/afs/desy.de/group/atlas/lib:$LD_LIBRARY_PATH
}}}

=== Using (t)csh ===
{{{
source /afs/desy.de/group/atlas/etc/login.csh
setenv PATH /afs/desy.de/group/atlas/bin:${PATH}
setenv LD_LIBRARY_PATH ${LD_LIBRARY_PATH}:/afs/desy.de/group/atlas/lib:
}}}

This will setup the batch system.

= KITS at Hamburg =

The following list of releases is installed:
 * 11'er series: 11.0.5 
 * 12'er series: 12.0.3, 12.0.6 (12.0.6.1, 12.0.6.2, 12.0.6.3, 12.0.6.4, 12.0.6.5), 12.0.7 (12.0.7.1), 12.0.8 
 * 13'er series: 13.0.40 (13.0.40.4, 13.0.40.5)
 * 14'er series: 14.2.20 (14.2.20.1 - 14.2.20.3), 14.2.25 (14.2.25.1 - 14.2.25.11), 14.4.0, 14.5.2
 * 15'er series: 15.0.0, 15.2.0
use `atlas_list_software.py` to list the current installed AtlasOffline and AtlasProduction versions. <<BR>><<BR>>

Setup: <<BR>>

Use the command `atlas_create_requirements.py` to get a curent requirements file for the installed kits.

CMT for setting up the requirement file is installed in each kit. For example use the following to setup CMT from the releasse 15.2.0 kit area: 
 * zsh/bash: {{{source /afs/desy.de/group/atlas/software/15.2.0/CMT/v1r20p20090520/mgr/setup.sh}}}
 * tcsh: {{{source /afs/desy.de/group/atlas/software/15.2.0/CMT/v1r20p20090520/mgr/setup.csh}}}
 
= EventView Group Area at Hamburg =

Installed: 
 * 11'er series: 11.0.5 (16) 
 * 12'er series: 12.0.6 (2,3,4,5,6,7,8), 12.0.7 (0,1) 
 * 13'er series: 13.0.40 (1) 

Setup: 
 * For the stable version of the !EventView group area you need the following line in your requirements file: <<BR>>{{{macro ATLAS_GROUP_AREA "${DAKIT}/EVGroupArea"}}}<<BR>>To activate the group area add groupArea to the -tag arguments in the athena setup step. 
 * For a numbered version of the !EventView group area you need the following line in your requirements file: <<BR>>{{{macro ATLAS_GROUP_AREA "${DAKIT}/EVGroupArea/EVTags-12.0.6.8"}}}<<BR>>To activate the group area add groupArea,oneGroup to the -tag arguments in the athena setup step. 

= CERN token =

If you want to work on package using cmt or svn you need a kerberos token for CERN. You can get it with one of the following commands: 
{{{
kinit username@CERN.CH 
}}}

= DDM =

Usually you need a valid grid proxy (grid-proxy-init or voms-proxy-init --voms atlas). In order to get a GRID UI (User Interface) use {{{ini glite}}}. The following tools are installed at DESY:

 * [[https://twiki.cern.ch/twiki/bin/view/Atlas/UsingDQ2|dq2 client]]
 * [[https://twiki.cern.ch/twiki/bin/view/Atlas/UsingDQ2#2_DQ2_end_user_tools|dq2 user tools]]
 * [[https://twiki.cern.ch/twiki/bin/view/Atlas/DistributedAnalysisUsingGanga|ganga]]
&nbsp;
 * {{{ini dq2}}} will setup the DQ2 client and user tools. Install directory is /afs/desy.de/group/atlas/software/dq2. 
 * {{{ini ganga}}} will setup a default ganga version. Install directory is /afs/desy.de/project/ganga. 

= Useful Commands =

 * `get_tag full_package_name release`: list all tags for package (or only for given release)