Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
pandoc:introduction-to-vsc:04_module_environment:01_modules [2018/01/12 11:19] – Pandoc Auto-commit pandocpandoc:introduction-to-vsc:04_module_environment:01_modules [2024/10/24 10:28] (current) – external edit 127.0.0.1
Line 2: Line 2:
  
   * Article written by Markus Stöhr (VSC Team) <html><br></html>(last update 2017-10-09 by ms).   * Article written by Markus Stöhr (VSC Team) <html><br></html>(last update 2017-10-09 by ms).
 +
  
  
Line 8: Line 9:
   - Find a suitable **location and directory structure** for serveral versions of the same library/code   - Find a suitable **location and directory structure** for serveral versions of the same library/code
   - Manage the **user environment** to be able to access the correct version automatically   - Manage the **user environment** to be able to access the correct version automatically
-  - Manage different software stacks, e.g. use different compiler(-version) or different library versions to build another library (--> 1.)+  - Manage different software stacks, e.g. use different compiler(-version) or different library versions to build another library (> 1.)
  
  
Line 88: Line 89:
 ===== Environment Modules ===== ===== Environment Modules =====
  
-  * **environment**: global variables available to current and all sub-shells ('env''set)+  * **environment**: global variables available to current and all sub-shells (envset’ )
   * http://modules.sourceforge.net/   * http://modules.sourceforge.net/
   * **module**: all modifications (set and prepend to variables) in the user environment necessary for using a piece of software   * **module**: all modifications (set and prepend to variables) in the user environment necessary for using a piece of software
Line 270: Line 271:
   * create own module environment as described on previous slide, create a directory within your training sub-folder   * create own module environment as described on previous slide, create a directory within your training sub-folder
   * check again, how the module is loaded.   * check again, how the module is loaded.
 +
  
 ===== Simple example ===== ===== Simple example =====
Line 305: Line 307:
  
  
-If needed add e.g. include directory explicitly:+If needed add e.g. include directory explicitly:
  
 <code> <code>
Line 323: Line 325:
   * mpicc   * mpicc
   * mpiicc   * mpiicc
 +
  
  • pandoc/introduction-to-vsc/04_module_environment/01_modules.1515755997.txt.gz
  • Last modified: 2024/10/24 10:21
  • (external edit)