Page History

...

1.1 - Scripts to set some environment variables 

Wiki MarkupThe script \[\] (\[\] [script .SetSoftRelease([].SetSoftRelease_bash] for bash or sh shell) sets the environement variables CMTCONFIG (to "rh9_gcc32opt"), GLAST_EXT (to "/afs/slac/g/glast/ground/GLAST_EXT/$CMTCONFIG") and the variable CMTPATH. The first 2 point to the directory where all the software packages hang, therefore they DO NOT need to be replaced. On the other hand, the variable CMTPATH points to the specific software package to be used, and consequently it needs to be modified every time you want to change software package or release. Because of that, the script has 2 arguments:

1. Software package; _BeamtestRelease, EngineeringModel... _
2. Release version: v3r0907p2, v6r070329p17 ...

An example of how to use it follows:unmigrated-wiki-markup

_source_ [].SetSoftRelease]\_\[\]\_ _BeamtestRelease_ _v3r0907p2_  BeamtestRelease v3r0907p2

I have this script in my home directory, which allows me to call it from everywhere in the following way:

source $HOME/[].SetSoftRelease BeamtestRelease v3r0907p2

 
It is important to note that different software packages might be using different root versions. That is the case (at August 2006) for the BeamtestRelease and the EngineeringModel, which uses root 5 and root 4 respectively. That implies that the root version (and related environment variables) have to be also modified when switching between these two software packages.

...

• The above mentioined scripts use the script .SetSoftRelease, and they all assume that this script is located in the $HOME directory. Therefore, if you want to place.SetSoftRelease in any other place, you have to change the scripts accordingly...
• I do have csh and sh scripts because, even though I particularly use csh, FRED wants to use bash (see section 3), and therefore I need both. I do not know whether this applies to you... but that might be useful.

...