This shows you the differences between two versions of the page.
— | linux:sfinx_modules [2015/07/02 08:47] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== Sfinx module files ====== | ||
+ | |||
+ | ===== Incomplete modules ===== | ||
+ | In some cases, loading the environment module is not sufficient to complete the setup for a [[sfinx_packages|package]]. This is currently true for these modules: | ||
+ | * iraf (but: environment setup is usually not needed to use the program, only when building your own tasks or running them from scripts outside the cl) | ||
+ | * miriad (but: environment setup is usually not needed to use the program, only if you want to use tasks from outside the miriad shell) | ||
+ | * newstar (dynamic list of aliases and some files are created when starting up) | ||
+ | * pydbsm (LOFAR setup) | ||
+ | * scisoft | ||
+ | * starlink | ||
+ | The proper way to set up these environments, | ||
+ | |||
+ | ===== Special case: MPI ===== | ||
+ | In case of MPI, there is a complication: | ||
+ | By default, '' | ||
+ | module switch mpi/ | ||
+ | module switch mpi/ | ||
+ | module switch mpi/ | ||
+ | module switch mpi/ | ||
+ | module switch mpi/ | ||
+ | The version without a reference to a python version in its name, sets the PYTHONPATH for the system default version of python (currently 2.7). For the sake of completeness, | ||