some tasks failed. see the tasks screen for more info.

Sets a limit on the total run time of the job allocation. If not, the default setting of 500MB will be assigned per CPU. Note: It’s highly recommended to specify -mem-per-cpu.

This is the minimum memory required per allocated CPU. Hence, the controller will grant allocation of 4 nodes, one for each of the 4 tasks. However, by using the -cpus-per-task=3 options, the controller knows that each task requires 3 processors on the same node. If the HPC cluster is comprised of quad-processors nodes and simply ask for 12 processors, the controller might give only 3 nodes. For instance, consider an application that has 4 tasks, each requiring 3 processors. Without this option, the controller will just try to allocate one processor per task. The default is 1 task per node, but note that the -cpus-per-task option will change this default.Īdvises the Slurm controller that ensuing job steps will require ncpus number of processors per task. This option advises the Slurm controller that job steps run within the allocation will launch a maximum of number tasks and offer sufficient resources. If not specified, the default partition is normal. Requests a specific partition for the resource allocation ( gpu, interactive, normal). If not specified, the default filename is slurm-jobID.out. Instructs Slurm to connect the batch script’s standard output directly to the filename. The default is the name of the batch script, or just sbatch if the script is read on sbatch’s standard input. The specified name will appear along with the job id number when querying running jobs on the system.

Some tasks failed. see the tasks screen for more info.