Setting up CMT on Unix

AT SLAC (linux)

Modify your .cshrc to include, in a section that always gets executed,  the lines

setenv GLASTROOT /afs/slac.stanford.edu/g/glast
source ${GLASTROOT}/ground/scripts/group.cshrc

Note that the above lines define the group default version of CMT. This is currently the v1r8p1 version of CMT that is obsolete, but frozen. To use a more current version it is suggested that you add the following line BEFORE the above lines in your .cshrc file (the group.cshrc script will use the CMTVERSION environment variable, if defined,  to set the CMT version) :

setenv CMTVERSION v1r9p20010927

You can set up your own path in two ways:

1. Define CMTPATH, either interactively, or in your .cshrc

2. clear CMTPATH, and put a line CMTPATH=... into a file .cmtrc in your HOME folder.   Currently the releases are put into the release area at /nfs/slac/g/glast/ground/releases.

On your own machine

CMT must be set up once per session. The simplest way to accomplish this is to add the following three lines to your .cshrc (or the equivalent to your shell's start-up file, e.g. .bashrc if you're running the bash shell, etc.):

The first line sets up the CMT environment variable CMTCONFIG.  You will need to replace ${BASE_OF_CMT} with whatever the path is to your installation of CMT.

The second line sets up some other CMT environment variables.  Again replace ${BASE_OF_CMT}.

The third line specifies to CMT where to look for your packages.  In this case CMT learns that the packages will be installed in /u/gl/tlindner/MyPackages.  It is possible to specify more than one place where packages will be kept, by using the following format

Conceivably you might also want to reissue the "setenv CMTPATH ..." command during a session if, for example, you want to switch between an environment using only released packages and one which will preferentially pick up your development packages.

Author: T. Lindner.
 Last Modified (by Toby Burnett): 12/02/2002 11:40