- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -
- Information contained in the HLRS Wiki is not legally binding and HLRS is not responsible for any damages that might result from its use -

CRAY XE6 Environment: Difference between revisions

From HLRS Platforms
Jump to navigationJump to search
No edit summary
 
No edit summary
 
(4 intermediate revisions by 2 users not shown)
Line 1: Line 1:
HWW systems uses environment modules, a package for managing user environments. Software such as compilers, libraries, tools and some widely used application codes are available to users via modules. Thus, in order to use a particular version of a particular piece of software you must first load its module. On log-in to the system a default collection of modules are available.
HWW systems uses environment modules, a package for managing user environments. Software such as compilers, libraries, tools and some widely used application codes are available to users via modules. Thus, in order to use a particular version of a particular piece of software you must first load its module. On log-in to the system a default collection of modules are available.


* You can inspect which modules you have loaded currently by the command "module list".
* You can inspect which modules you have loaded currently by the command: <pre>module list</pre>
* In order to inspect which modules are available to use, you can issue the command "module avail".
* In order to inspect which modules are available to use, you can issue the command <pre>module avail</pre>
* If you want to swap one currently loaded module for another that is not, "module swap PrgEnv-pgi PrgEnv-gnu" for example swaps the currently loaded CRAY PGI Programming version PrgEnv-pgi for CRAY own programming version PrgEnv-cray.
* If you want to swap one currently loaded module for another that is not, <pre>module swap PrgEnv-pgi PrgEnv-gnu</pre> for example swaps the currently loaded CRAY PGI Programming version '''PrgEnv-pgi''' for CRAY own programming version '''PrgEnv-cray'''. This will switch several other modules to the corresponding choice.
If you want to load a module afresh (and there is no need to swap out a currently loaded module) use e.g. "module load castep".
 
For more details on using modules see the [[Module_command | Module commands]] or [https://fs.hlrs.de/projects/craydoc/docs/books/S-2396-50/html-S-2396-50/chapter-n4qtphjb-brbethke.html Using Modules].
For more details on using modules see [https://fs.hlrs.de/projects/craydoc/docs_merged/books/S-2396-601/html-S-2396-601/chapter-n4qtphjb-brbethke.html CRAY: Using Modules] or [[Module_command | Module commands]].

Latest revision as of 15:57, 28 November 2011

HWW systems uses environment modules, a package for managing user environments. Software such as compilers, libraries, tools and some widely used application codes are available to users via modules. Thus, in order to use a particular version of a particular piece of software you must first load its module. On log-in to the system a default collection of modules are available.

  • You can inspect which modules you have loaded currently by the command:
    module list
  • In order to inspect which modules are available to use, you can issue the command
    module avail
  • If you want to swap one currently loaded module for another that is not,
    module swap PrgEnv-pgi PrgEnv-gnu
    for example swaps the currently loaded CRAY PGI Programming version PrgEnv-pgi for CRAY own programming version PrgEnv-cray. This will switch several other modules to the corresponding choice.

For more details on using modules see CRAY: Using Modules or Module commands.