In the following, I compiled some useful information / links / problems that I encountered during my try to install the ScienceTools myself on a machine at CEA Saclay (i.e., external). No claim of completeness whatsoever, and a lot of these things might be obvious for most.
CVS : getting the latest ScienceTools
Look at the ScienceTools scripts online: CVS repository
Setting up CVS:
Follow the steps in Using the GLAST SLAC cvs Repository, then
--> write a mail to Thomas Glanzman to get CVS access for your account.
--> you will have to logout and login for the change to take effect.
--> you should have (if you have an external account):
Check the available versions of ScienceTools: New Release Manager web interface
How to get the ScienceTools (here, version LATEST-1-4167):
Get the CVS status:
Get the CVS update:
SCons: Building the ScienceTools
SCons version SCons 1.3 required (SCons)
Environment variable $GLAST_EXT:
“The environment variable GLAST_EXT should be suitably defined. (...)
Note: The --with-GLAST-EXT option must always be supplied; others are optional under most circumstances.”
This is the variable defining the directory of external programs (e.g. python).
I pointed the GLAST_EXT variable to the ScienceTools RELEASE, which is not the place where I want to install the latest ScienceTools version.
How to build the ScienceTools:
(assuming you want to build a package called 'astro')
I put some example output at the end of this page
Remark (python code):
python code, let's say the script foo.py example in
will be copied to
when you build the respective package (here: pointlike. For the example output, see end of this page)
So do not change the code in the python package directly
SCons should handle dependencies correctly. However, at the moment there seems to be an issue when compiling the skymaps before astro package. Follow this thread:
Obviously, in order to use your brand new installation of the ScienceTools, you would need to adjust your environment.
You might consider changing the following environmental variables:
E.g., one could create a second bashrc script that sets the environment so that you can chose between the 'standard' installation and your own one.
Example output of building with SCons: