|
|
<!-- DOCTOC SKIP -->
|
|
|
|
|
|
The `module` command is installed on the cluster. It allows you to use specific versions of libraries, that are not present in the packaging system. This is done by modifying your environment variables, like `LD_LIBRARY_PATH` or `PATH`.
|
|
|
The `module` command is installed on the cluster. It allows you to use specific versions of libraries that are not present in the packaging system. This is done by modifying your environment variables, like `LD_LIBRARY_PATH` or `PATH`.
|
|
|
|
|
|
|
|
|
#### Usage
|
... | ... | @@ -34,5 +34,4 @@ When using module, there are two kinds of modules available: |
|
|
* Single modules: Modules that load environment for a specific library
|
|
|
* Profile modules: Meta-modules that load other modules
|
|
|
|
|
|
When using the modules, you really need to pay attention to the modules you load, specifically due to the dependencies that exist between modules (e.g. petsc is compiled for a specific version of OpenMPI, thus will not work with other MPI versions). For this reason, we will only provide support for Profile modules.
|
|
|
In case you encounter problems, please ask the persons in charge, indicated when you log on atlas. |
|
|
\ No newline at end of file |
|
|
When using the modules, you really need to pay attention to the modules you load, specifically due to the dependencies that exist between modules (e.g. petsc is compiled for a specific version of OpenMPI, thus will not work with other MPI versions). For this reason, we will only provide support for Profile modules. |
|
|
\ No newline at end of file |