0.Pegasus Supercomputer  The Pegasus cluster is the University of Miami's 000-node high-performance supercomputer, available to all University of Miami employees and students. Pegasus resources such as hardware (login and compute nodes) and system software are shared by all users.  We encourage new users to carefully read our documentation on Pegasus and available resources, especially users who may be unfamiliar with high-performance computing, Unix-based systems, or batch job scheduling. Understanding what your jobs do on the cluster helps keep Pegasus running smoothly for everyone.  Do not run resource-intensive jobs on the Pegasus login nodes. Submit your production jobs to LSF, and use the interactive queue (link) - not the login nodes - for resource-intensive command-line processes. You may compile and test jobs on login nodes. However, any jobs exceeding 00 minutes of run time or using excessive resources on the login nodes will be terminated and the CCS account responsible for those jobs may be suspended.  Reserve an appropriate amount of resources through LSF for your jobs. If you do not know the resources your jobs need, use the debug queue to benchmark your jobs. More on Pegasus Queues (link) and LSF Job Scripts (link) below. Jobs with insufficient resource allocations interfere with cluster performance and the CCS account responsible for those jobs may be suspended.  Stage data for running jobs exclusively in the /scratch file system, which is optimized for fast data access. Any files used as input for your jobs must first be transferred to /scratch. The /nethome file system is optimized for mass data storage and is therefore slower-access. Using /nethome while running jobs degrades the performance of the entire system and the CCS account responsible may be suspended.