<html>#2482: Inconsistency in Simfactory submission scripts
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Steven R. Brandt</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>SimFactory</td></tr>
</table>
<p>Comment (by Steven R. Brandt):</p>
<p>Sorry, my last response didn’t come out right. What I think happens is this: </p>
<p>If we set -N 2 -n 6 --ntasks-per-node=4 then slurm sets SLURM_TASKS_PER_NODE=4(x2) and SLURM_NTASKS=6 and it’s up to the application to make sense of it. </p>
<p>mpich runs 8 procs, 4 on each of 2 nodes (the number of nodes in SLURM_NODELIST). Of course, one is free to give explicit parameters to mpi to change these values. </p>
<p>What I think we want simfactory to do is let mpich (or openmpi) interpret the environment variables how they want. That means --ntasks-per-node should be @NUM_PROCS@ I believe.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2482/inconsistency-in-simfactory-submission'>https://bitbucket.org/einsteintoolkit/tickets/issues/2482/inconsistency-in-simfactory-submission</a></p>
</html>