Skip to content

Computing Environment


Login node

The default shell for Launch is bash. Its environment is defined in the startup file, .bash_profile. It is read and executed when you login and resides in your home directory.

The use of the login nodes is for small-to-medium code development and processing. The most important processing limits here are:

  • CPU time - ONE HOUR for interactive processes on the login nodes.
  • Cores for Concurrent Use - EIGHT CORES cumulative across all Launch login nodes.

ANYONE found violating these limits WILL have their processes killed WITHOUT WARNING. Repeated violation of these limits WILL result in account suspension.

More information about the hardware of each of the login nodes can be found on the Hardware Summary page.

File Space

Immediately upon logging in to Launch, the following message about the status of your disk space use greets you (format may vary):

Your current disk quotas are:
Disk       Disk Usage      Limit    File Usage      Limit
/home           2.49G        10G           113      10000
/scratch        1.25G         1T            40      250000
Type 'showquota' to view these quotas again.

Note: It is important to pay attention to this information, as it shows how much space has been used in each directory. Hitting a quota limit can cause problems for the user and should be avoided. More information on the specific file systems including limitations and information about expansions can be found on the File Systems page.


The Modules system organizes the multitude of packages we have installed on our clusters so that they can be easily maintained and used. Any software you would like to use on Launch should use the Modules system. NO modules are loaded by default.

The main command necessary for using software on Launch is the load command. To load a module, use the following command:

[username@launch ~]$ module load [packageName]

The specification of packageName in the load command is case sensitive and it should include a specific version. To find the full name of the module you want to load, use the following command:

[username@launch ~]$ module spider [packageName]

To see a list of available modules, please use the mla wrapper script:

[username@launch ~]$ mla

Note: Launch uses a hierarchical module system. That means before you can load a package that has a Toolchain dependency, you will need to load the Toolchain it was built with first.

More information on the Modules system can be found on the Modules System page.

Back to top