The Daily Bulletin

The recommended way to set up your Cheyenne user environment–or in some cases, environments–is to load the desired modules after logging in or to create customized environments as described here.

Some users recently reported problems that resulted from loading environment modules with their personalized start files (.bashrc, .cshrc, .kshrc, .tcshrc, .login, .profile, and so on) instead of the recommended procedures.

As advised in our Personalizing start files documentation, Cheyenne users should not set environment modules in their start files by using commands such as:

  • module load nco

  • module load netcdf

Please contact the CISL Consulting Services Group if you have questions.

Batch jobs running on the Cheyenne systems sometimes fail when they create large stdout or stderr files that overflow the spool directory on the first compute node used. Failures from this condition are more likely with MPI jobs. To avoid the problem, CISL recommends redirecting job output to a file as described in this newly updated documentation regarding job scripts.