ECEric Coulter

Eric Coulter

*This is an algorithmically generated author record based on publicly available information.

Current Organizations / Institutes

The organizations/institutes from the scholar's latest article


Eric Coulter has a total of 22 co-authors. Here are the top co-authors by number of shared publications:


Latest Publications

  • Open Access

    CEDAR - A Campus and HPC Connected Storage Solution for Collaborative Research

    by Deepa Phanish, Kenneth Suda, Ruben Lara, Dan Zhou, Eric Coulter, Fang Liu, Aaron Jezghani

  • Open Access

    Exploring Research Dataset-Sharing Strategies for Concurrent AI Workflows

    by Yongnuo Yang, Fang Liu, Michael D. Weiner, Aaron Jezghani, J. Eric Coulter, Ruben Lara, Ronald Rahaman, Kenneth J. Suda, Jeffrey Valdez, Dee Womack, et al.

    Artificial Intelligence (AI) and Machine Learning (ML) workflows are increasingly prevalent in High Performance Computing (HPC) centers, requiring additional support from campus research computing centers like Georgia Institute of Technology (GT) Partnership for an Advanced Computing Environment (PACE). AI datasets usually contain many small files and a large total size; it wastes storage space if every researcher downloads copies. Hence a shared dataset is desired. The challenge is how to share the AI dataset to support multiple concurrent AI workflows efficiently. HPC filesystem choices, low-level filesystem configuration, and AI pipeline data loader selection play essential roles. This paper demonstrates a systematic performance test to guide us in implementing a shared AI data service at PACE.


  • Open Access

    ICE 2.0: Restructuring and Growing an Instructional HPC Cluster

    by J. Eric Coulter, Michael D. Weiner, Aaron Jezghani, Matthew Guidry, Ruben Lara, Fang (Cherry) Liu, Allan Metts, Ronald Rahaman, Kenneth Suda, Peter Wan, et al.

    The Partnership for an Advanced Computing Environment (PACE) at Georgia Tech (GT) has been running two campus-wide cluster resources available for academic courses and workshops for five years. The initial design focused on creating a federated resource for a wide range of educational topics, based on a PACE and College of Computing (COC) partnership. Due to funding, this took the form of separate resources, one funded by PACE, and another by COC. These "Instructional Cluster Environments", PACE-ICE and COC-ICE, became very popular with instructors at GT but led to a high maintenance cost due to the split nature of the environments. With the transition to the Slurm scheduler, PACE collaborated with COC to merge the two clusters into one, ICE. This work details the strategies used to sensibly merge the two production systems, including the storage architecture, shared system policies, and scheduler priority configurations that honor funding complexities.


  • Open Access

    Campus Bridging in the Age of COVID-19

    by Eric Coulter, Richard Knepper, Resa Reynolds, Stephen Bird, Tabitha Kripa Samuel, Winona Snapp-Childs

  • Open Access

    Semi-Automatic Hybrid Software Deployment Workflow in a Research Computing Center

    by Fang Liu, Ronald Rahaman, Michael Weiner, Eric Coulter, Deepa Phanish, Jeffrey Valdez, Semir Sarajlic, Ruben Lara, Pam Buffington

    The software stack is an essential component in any High Performance Computing (HPC) cluster, and it is critical to optimize the usage of the underlying computing resources while simultaneously providing the best user experience. Georgia Institute of Technology (GT) Partnership for an Advanced Computing Environment (PACE) maintains a heterogeneous system with around 2000 compute nodes across five different clusters on two different schedulers (Torque and Slurm) and two different parallel filesystems (GPFS and Lustre). This diversity calls for multiple software stacks that pose a significant challenge to delivering software support efficiently. Hardware upgrades, filesystem changes, and scheduler replacements all lead to software stack changes ranging from updating the MPI libraries to rebuilding the whole stack. In the past five years, PACE has rebuilt the software stack four times due to these events. To reduce the build time, Spack, GitLab, and ReFrame tools were adopted. Spack, an automatic software building tool, allows us to set up more than half of the software stack quickly; GitLab provides git tags and issues to handle Dev-Test-Prod workflow coordination within the team; and ReFrame provides a systematic way to test the whole software stack automatically. By integrating these three tools alongside manual software installations, we have created a semi-automatic hybrid software deployment workflow that is presented in this paper. We share our experience to contribute to the body of work and useful tradition of HPC centers sharing their practices with the community.