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 the CEA Saclay (i.e., external). No claim of completeness whatsoever, and a lot of these things might be obvious for most of you. ..
CVS : getting the latest ScienceTools
Look at the ScienceTools scripts online: CVS repository
...
Follow the steps in Using the GLAST SLAC cvs Repository, then
--> write a mail to Thomas Glanzman to to get CVS access for your account.
...
Get the CVS status:
| Code Block |
|---|
cvs status |
Get the CVS update:
| Code Block |
|---|
cvs up |
...
SCons: Building the ScienceTools
SCons version SCons 1.3 required (SCons) I didn't have the newest version, so I needed to have it installed and issue:
module add sconsHow to use SCons: SCons for Fermi/LAT: An Overview, Making Builds with SCons
...
I put some example output at the end of this pageOrder of packages:
The order of packages to install might be important! For example, to install skymaps, astro needs to be installed first. Follow the path astro -> skymaps -> python -> data
Remark (python code):
python code, let's say the script foo.py example in
...
So do not change the code in the python package directly
Remark (dependencies):
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:
| Jira | ||||
|---|---|---|---|---|
|
...
Environment
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:
| Code Block |
|---|
PATH
ST_INST
INST_DIR
LD_LIBRARY_PATH
TCL_LIBRARY
DYLD_LIBRARY_PATH
PYTHONPATH
## e.g.
export PATH=$MY_ScienceTools:${PATH}:.
|
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:
...