Radon to switch to hierarchical modules
January 25, 2017
Update: January 25, 2017 11:26am
Radon has been converted to hierarchical modules.
Old style module load commands should still continue to function until the end of the Spring semester, however you will be given a warning message and a suggestion on how to correct your scripts. Once you believe you have made all the necessary changes you may turn off the old-name translation by:
$ touch ~/.hierarchy
Then, by logging out and back in, the automatic translation will be disabled. This will allow you to be sure that your scripts are correctly updated before the translation is turned off system wide at the end of the semester. We will send further details and timing on turning off translations in the coming weeks.
On January 25th, 2017 the Radon cluster's software stack will be converted to an hierarchical configuration. This new software has been in use on Halstead since it was brought online. This change will help prevent errors and configuration problems due to version mismatches or conflicting software, and will allow for ITaP to provide a more robust software stack.
This change may require you to make small modifications to your job scripts. The module command will attempt to automatically translate these for you to help ease into the transition but an automatic translation may not always be possible, and this functionality will only be offered for a limited time.
To further aid in this transition, a Radon node has been converted to the new configuration for you to log in and explore the new configuration. In addition, a small tool has been developed that will scan your shell startup scripts and specified job scripts to identify potential changes that may need to be made.
From a Radon front-end machine, type the command:
$ ssh radon-modules
Once on the test node, you can use "module spider" and "module avail" to explore the new hierarchical configuration. Once on this test node you can run the module checker script.
To check shell start up scripts:
To check a job script(s):
$ modulecheck myjobscript.sub
The tool will attempt to also scan any other scripts that the specified scripts source or include. If the tool is unable to find a sourced file, it will warn you that it was unable to check that file.
The output of this command will give you a summary of the files it found, whether it found any issues and will offer suggestions on how to update your scripts. Please do not try to run your jobs on this test node.
Additional information and explanations about the module hierarchy can be found in the user guide.