You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Next »

This page gives some tips for using  FRED with the Beam test software releases, but also with any other GLAST software release.

The page is devided in 3 sections.

  • Setting the environment variables to use a specific software package
  • Useful macro to select  the events you want to display with FRED
  • Setting FRED GLAST panel to visualize the desired data

 

The scripts and macros use paths which are from the machines at SLAC. In order to work on other cluster of computers one needs to replace the pathnames. 

1 -  Setting the environment variables to use a specific software package

The software to analyze GLAST data is pretty complex. It involves several (similar) release packages (BeamtestRelease,  EngineeringModel,  GlastRelease and  ScienceTools) and many different
release versions. In order to add more complexity to the issue, different release packages run with different root versions, and different programs might be running with different shell flavours. That implies that one needs to be careful when changing software package; the chances of  working with a not properly set package (i.e. wrong libraries) are not negligible.

In this section you can find a set of very simple scripts and a even more simple root macro that help setting the environment variables in rather easy and systematic way.

The 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/$

Unknown macro: {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:

source .SetSoftRelease BeamtestRelease v3r0907p2

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

_source $

Unknown macro: {HOME}

/.SetSoftRelease BeamtestRelease_ v3r0907p2

 

# options commonly used so far by me (2005/07):
# EngineeringModel v6r070329p17
# BeamtestRelease v2r0903p0
# BeamtestRelease v3r0907p2

The different release package and versions can be set
via the script $

/.SetSoftRelease

An example follows:

source $

Unknown macro: {HOME}

/.SetSoftRelease BeamtestRelease v2r0903p0

      

setenv MAINPATH4BUILDS "/nfs/farm/g/glast/u09/builds/$

 

"
setenv SOFTRELEASETYPE $1
setenv SOFTRELEASEVERSION $2
setenv CMTPATH
 

 

 

 

 

2 -  Useful macro to select  the events you want to display with FRED

 

 

 

3 -  FRED GLAST panel to visualize the desired data

 

 

(EngineeringModel, BeamTest)

 

# EngineeringModel v6r070329p17
# BeamtestRelease v2r0903p0

  • No labels