|
From: Angel de V. <ang...@ia...> - 2024-09-07 11:44:02
|
Hello, Thanks Paul and Xavier for your comments. But I think the current options provided by "module" are not sufficient for what I wanted to achieve. The idea is to give our users (some of which are very new to "modules") a very easy and clear view of all the packages we provide at our institution. We already have a webpage describing them, organized by categories, and I wanted to be able to somehow replicate the same structure with the command "module avail". In case the mail broke all the lines, here you can see properly the output structure after my changes: https://pastecode.io/s/955wj58p > There currently are 3 ways to achieve hierarchical organization: > * using specific modulepaths and enabling/disabling them on demand > * playing with module visibility: hide modules that are not useful by > default, show them if one specific module is loaded > * module variants: 1 modulefile many variations of it I knew these (and have used all except the variants, I'll give it a go), but for very new users to "modules" I wanted to try something that does not hide or disables anything by default, or that the user has to issue some command to show some extra modules, etc. because they are going to get confused (I know it is easy, but trust me, I know our users :-)). I think they will prefer (though not sure yet) if all modules are shown, but with a nice structure so they can find the relevant one quickly. > As Paul suggest, there is also the approach to limit the view to the > default (or latest) module version. Yes, we use this one as well, but we have many different packages, not many versions of each, so this cuts very little in our output (plus only makes it shorter, not structured)./ > Based on your explanation and example, it may be interesting to add a > "group" feature to specifically sort modules of a given modulepath. > Group could be defined in .modulerc files with a new command > (module-group for instance). One may decide to view all the modules > sorted by group or not, thanks to the "avail_output" configuration > option. Yes, a "group" feature where you specify a hierarchy to be shown would be ideal. My changes were attempting something similar, in which I give for each modulepath a label and an indentation, so that I can create "module avail" output in a more organized and personalized way. Cheers, -- Ángel de Vicente Research Software Engineer (Supercomputing and BigData) Tel.: +34 922-605-747 --------------------------------------------------------------------------------------------- AVISO LEGAL: Este mensaje puede contener información confidencial y/o privilegiada. Si usted no es el destinatario final del mismo o lo ha recibido por error, por favor notifíquelo al remitente inmediatamente. Cualquier uso no autorizadas del contenido de este mensaje está estrictamente prohibida. Más información en: https://www.iac.es/es/responsabilidad-legal DISCLAIMER: This message may contain confidential and / or privileged information. If you are not the final recipient or have received it in error, please notify the sender immediately. Any unauthorized use of the content of this message is strictly prohibited. More information: https://www.iac.es/en/disclaimer |
