You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
*What is the relationship between these lines in the config file:
cores_per_job: 2
processes: 2
memory_per_job: 48
max_jobs: 12
and the 128 in this command: srun --pty -p cpu -A mappnat --ntasks=1 --cpus-per-task=128 --exclusive -t 08:00:00 -u bash -i?
Should the cpus-per-task=128 in the srun command match the product of (MAX_JOBS defined in submit_c404-ba_hourly_workflow.sh) times ( max_jobs defined in the config file plus 1). Based on the example files in this repo, the product would be 10 * (12 + 1) = 130 which is higher than the cpus-per-task=128. Does cores_per_job (here 2) play any role in the cpus-per-task calculation?
Is 8 hours sufficient for the interactive job? What happens if the interactive job kicks me out at the 8 hours and the processing has not finished? Will it continue in the background or crash?
The text was updated successfully, but these errors were encountered:
*What is the relationship between these lines in the config file:
cores_per_job: 2
processes: 2
memory_per_job: 48
max_jobs: 12
and the 128 in this command: srun --pty -p cpu -A mappnat --ntasks=1 --cpus-per-task=128 --exclusive -t 08:00:00 -u bash -i?
Should the cpus-per-task=128 in the srun command match the product of (MAX_JOBS defined in submit_c404-ba_hourly_workflow.sh) times ( max_jobs defined in the config file plus 1). Based on the example files in this repo, the product would be 10 * (12 + 1) = 130 which is higher than the cpus-per-task=128. Does cores_per_job (here 2) play any role in the cpus-per-task calculation?
Is 8 hours sufficient for the interactive job? What happens if the interactive job kicks me out at the 8 hours and the processing has not finished? Will it continue in the background or crash?
The text was updated successfully, but these errors were encountered: