Bureaucrats, cc_docs_admin, cc_staff
2,232
edits
Utiliser des modules/en: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 92: | Line 92: | ||
The main differences between the environment available to you on the new Compute Canada servers and the servers you have used in the past are as follows. | The main differences between the environment available to you on the new Compute Canada servers and the servers you have used in the past are as follows. | ||
== Module hierarchy == | == Module hierarchy == | ||
Most systems use a flat module structure: All modules are at the same level. This becomes problematic when many combinations of versions of different modules are available on a system. For example, if you need to use the [[FFTW]] library and the module <code>fftw</code> is available in several versions, including a version compiled with GCC 4.8 and Open MPI 1.6, you might see modules named <code>openmpi/1.6_gcc4.8</code> and <code>fftw/3.3_gcc4.8_openmpi1.6</code>. This is neither elegant nor practical. To solve this problem we use a hierarchy of modules. Rather than using the command | Most systems use a flat module structure: All modules are at the same level. This becomes problematic when many combinations of versions of different modules are available on a system. For example, if you need to use the [[FFTW]] library and the module <code>fftw</code> is available in several versions, including a version compiled with GCC 4.8 and Open MPI 1.6, you might see modules named <code>openmpi/1.6_gcc4.8</code> and <code>fftw/3.3_gcc4.8_openmpi1.6</code>. This is neither elegant nor practical. To solve this problem we use a hierarchy of modules. Rather than using the command | ||
| Line 98: | Line 97: | ||
you instead use | you instead use | ||
{{Command|module load gcc/4.8 openmpi/1.6 fftw/3.3}} | {{Command|module load gcc/4.8 openmpi/1.6 fftw/3.3}} | ||
This is made possible by using a module hierarchy. The <code>fftw/3.3</code> module that is loaded will not be the same one that would be loaded if you had previously loaded the Intel compilers instead of GCC. | This is made possible by using a module hierarchy. The <code>fftw/3.3</code> module that is loaded will not be the same one that would be loaded if you had previously loaded the Intel compilers instead of GCC. | ||
<div class="mw-translate-fuzzy"> | <div class="mw-translate-fuzzy"> | ||