Updated 2020-08-28

ECE Software on testflight-coda

As a reminder the login node is: login-testflight-coda.pace.gatech.edu

With the move to Coda, the ECE software stack and user environment will undergo two changes 1. The ECE software stack will be hosted in the PACE Community software repository 2. The default user shell will be changed to bash from the current tcsh

Accessing the ECE Software Stack

The ECE software is now supported under a community environment called PACE Community, which comprises PACE user-built software. PACE is not responsible for the content, quality and any other issue related to use of the software; ECE group who installs the software will carry out software maintenance and support. Compilers and MPI libraries are provided by PACE.

As an end-user, all you will need to do is:

  • Load the pace-community module with module load pace-community
  • See available software with module avail
  • Load ECE software with module load <software>

There are also methods to allow modules to persist (for both login and jobs). Here's a workflow example:

module restore pace        # start with the default PACE meta-module
module load pace-community # expose more software 
module load cst            # load ECE component
module save                # saves to 'default' module collection

Then at login, the software that you need will be available.

Want to start fresh? Then do

rm ~/.lmod.d/default         

For more details, please read about Lmod's (the modules system used on PACE's Coda resources) user collections.

Default Shell Switching to Bash

To preserve current ECE user workflow, the switch to Bash will occur after users have been moved into Coda. Any work being conducted on compute resources in Rich (accessed via the login-s or login7-d headnodes) will continue as normal. testflight-coda will be an opportunity for ECE users to adapt to the new environment and shell change later this year. Here are some key points: - While using testflight-coda, users will still login to a tcsh shell as usual - All jobs must run with a Bash script for consistency with the software build environment - The additional option -S /usr/bin/bash must be included at job submission to run in the appropriate shell


You can alias the qsub command in your ~/.bashrc file to automatically set the shell for every job submission! Simply run the command echo "alias qsub='qsub -S /usr/bin/bash' >> ~/.bashrc" && source ~/.bashrc once, and it will remain effective every time you log in to testflight-coda.

Finally, when users are migrated to Coda completely, the default shell for all ECE users will be changed to Bash. The work done on testflight-coda will allow users the opportunity to seamlessly transition to the new shell. Because the default shell for ECE users will be Bash in Coda, the above tip to specify the run-time shell will no longer be required for job submission.