Once you have an account and the necessary software, you can log in and run jobs on the Cheyenne supercomputer.
Logging in also gives users access to these resources, depending on their allocations:
To run data analysis and visualization jobs on the Casper system's nodes, follow the procedures described here. There is no need to transfer output files from Cheyenne for this since Cheyenne and Casper mount the same GLADE file systems.
Don’t run sudo on NCAR systemsIf you need help with tasks that you think require sudo privileges, or if you aren’t sure, please contact HPC User Support before trying to run sudo yourself. The command fails when unauthorized users run it and sends a security alert to system administrators. |
Logging in on an NCAR system
EnvironmentThe Cheyenne HPC system uses a Linux operating system and supports widely used shells on its login and compute nodes. Users also have several compiler choices. Operating systemSUSE Linux. SchedulerAltair PBS Pro. See this detailed documentation about using PBS Pro and running jobs. ShellsThe default login shell for new Cheyenne users is bash. You can change the default after logging in to the Systems Accounting Manager (SAM). It may take several hours for a change you make to take effect. You can confirm which shell is set as your default by entering echo $SHELL on your Cheyenne command line. Environment modulesThe Cheyenne module utility enables users to easily load and unload compilers and compatible software packages as needed, and to create multiple customized environments for various tasks. Here are some of the most commonly used commands. (See the Environment modules page for more details.) module av - Show which modules are available for use with the current compiler. module help - List switches, subcommands, and arguments for the module utility. Specify a modulefile by name for help with an individual module.
module list - List the modules that are loaded. module load - Load the default version of a software package, or load a specified version.
module spider - List all modules that exist on the system. module swap - Unload one module and load a different one. Example:
module unload - Unload the specified software package.
CompilingCheyenne users have access to Intel, PGI, and GNU compilers. The Intel compiler module is loaded by default. After loading the compiler module that you want to use, identify and run the appropriate compilation wrapper command from the table below. (If your script already includes one of the following generic MPI commands, there is no need to change it: mpif90, mpif77, ftn; mpicc, cc; mpiCC and CC.) Also consider using the compiler's diagnostic flags to identify potential problems.
DebuggingCISL provides the ARM Forge tools, DDT and MAP, for debugging, profiling, and optimizing code in the Cheyenne environment. Performance Reports is another ARM tool for Cheyenne users. It summarizes the performance of HPC application runs. See Running DDT, MAP and PR jobs. Cheyenne queuesMost of the Cheyenne batch queues are for exclusive use, and jobs are charged for all 36 cores on each node that is used. Jobs in the shared use "share" queue are charged only for the cores used. The "regular" queue, which has a 12-hour wall-clock limit, meets most users' needs for running batch jobs. See the table on this page for information about other queues. Submitting jobsSchedule your jobs to run on Cheyenne by submitting them through the PBS Pro workload management system. (To run jobs on the Casper cluster, see this documentation.) To submit a Cheyenne batch job, use the qsub command followed by the name of your batch script file.
See this page for job script examples. To start an interactive job, use the qsub command with the necessary options but no script file.
More detailed PBS Pro documentation |