Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

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

...

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)

...

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
serverSLAC National Accelerator Laboratory
keySTGEN-160

...

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:

...