...
Data from jobs run on Beartooth during testing: historical information about JOBS will be lost once Beartooth goes live - DATA resulting from the jobs will remain in /project, /home, and/or /gscratch.
LMOD issue: ARCC has found an issue where the user’s local module cache does not differentiate which cluster you are using, which can result in versions of a module installed on Beartooth being shown while using on Teton, and vice-versa. A work around is to add “--ignore-cache” to the module spider command. This forces LMOD to only navigate the module tree for the cluster you’re using.
For example: module --ignore-cache spider <module name>
Citing Beartooth
For information on citing Beartooth, please reference the citing section in Documentation and Help.