In OCTOPUS, the environment variable settings of the compiler, library, and application environment are managed by Environment modules. By using the module command, it is possible to set the environment variables required for using the application in a unified manner.
The main usage is shown below.
| Command | Description |
|---|---|
| module avail | List of available development environments / apps |
| module list | List of loaded modules |
| module switch [file1] [file2] | Module replacement (file1 → file2) |
| module load [file] | load a module |
| module unload [file] | unload a module |
| module purge | Unload all loaded modules |
| module show [file] | Detailed display of modules |
*Note: If you want to use the module command in a csh shell script, you need to execute "source /etc/profile.d/modules.sh" in advance.
OCTOPUS provides a base environment that summarizes the environment variable settings required for each calculation environment. By loading the base environment first, you can easily arrange the environment variable settings.
The base environment prepared by this system is as follows.
| Type | Module Name | Contents |
|---|---|---|
| Compiler + MPI + Library | BaseCPU | Recommended environment for program development for general-purpose CPU nodes |
| BaseGCC | Development environment when using GCC | |
| Language environment + module | BasePy | Program development environment for Python |
| BaseR | Program development environment for R | |
| BaseJulia | Program development environment for Julia | |
| BaseJDK | Program development environment for Java | |
| Application | BaseApp | Base environment for ISV and OSS application users |
