Utiliser des modules/en: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 101: Line 101:
The inconvenience of using a module hierarchy is that, since modules can have the same name, only the modules that are compatible with the "parent" modules are displayed by the <code>module avail</code> command. Loading a parent module is therefore a prerequisite to loading some modules. To get complete information, Lmod provides the <code>module spider</code> command. It scans the entire hierarchy and displays all the modules. By specifying a module and a particular version, it is then possible to see which paths in the hierarchy enable the desired module to be loaded.
The inconvenience of using a module hierarchy is that, since modules can have the same name, only the modules that are compatible with the "parent" modules are displayed by the <code>module avail</code> command. Loading a parent module is therefore a prerequisite to loading some modules. To get complete information, Lmod provides the <code>module spider</code> command. It scans the entire hierarchy and displays all the modules. By specifying a module and a particular version, it is then possible to see which paths in the hierarchy enable the desired module to be loaded.


<div class="mw-translate-fuzzy">
== Module collections ==
== Module collections ==
Module collections are an additional functionality provided by Lmod. See [[#Module collections (Lmod only)|this section]] for more details.
Module collections are an additional functionality provided by Lmod. See [[#Module collections (Lmod only)|this section]] for more details.
</div>


== Only one version loaded at a time ==
== Only one version loaded at a time ==
Bureaucrats, cc_docs_admin, cc_staff
2,232

edits

Navigation menu