Search results

Jump to navigation Jump to search
  • ===Batch partitions (queues) defined on the Sapelo2=== ...es, amount of memory, GPU cards, etc). Please note, Slurm will not allow a job to be submitted if there are no resources matching your request. Please ref
    4 KB (631 words) - 10:32, 24 January 2024
  • ===How to list all user jobs in the queues=== The column entitled '''JOBID''' gives the job id of each job.
    10 KB (1,129 words) - 21:52, 5 September 2023
  • ===Using the Batch Queues=== Jobs of over ten (10) minutes duration must be submitted to the queues rather than run in the background or interactively on the login node pclust
    12 KB (2,087 words) - 12:28, 14 February 2013
  • for job scheduling and resource management on Sapelo2. Slurm replaced the Torque (P ...allocated to other jobs at the moment. Torque will queue the job, but the job would never run.
    13 KB (1,990 words) - 09:47, 28 October 2020
  • The login node for the teaching cluster should be used for text editing, and job submissions. '''No jobs should be run directly on the login node.''' ===Queues defined on the teaching cluster===
    27 KB (4,260 words) - 11:14, 18 January 2024
  • ...e job submission scripts. This might be seen as an inconvenience. Multiple queues and advanced scheduling mechanisms will be implemented on Sapelo2. ...elo or to copy and delete files from /lscratch on the compute nodes when a job crashes.
    6 KB (910 words) - 11:09, 4 January 2018
  • The login node for the Sapelo2 cluster should be used for text editing, and job submissions. '''No jobs should be run directly on the login node.''' ===Batch partitions (queues) defined on the Sapelo2===
    51 KB (7,941 words) - 08:37, 12 October 2023
  • ...rstand how to request computing resources and submit a computational batch job following the Sapelo2 cluster general workflow * Understand how to initiate an interactive job
    20 KB (2,866 words) - 09:40, 15 April 2024