<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 Roland Haas):</p>
<p>Responding to <a data-is-external-link="true" href="https://bitbucket.org/einsteintoolkit/tickets/issues/2482/inconsistency-in-simfactory-submission#comment-59534195" rel="nofollow">https://bitbucket.org/einsteintoolkit/tickets/issues/2482/inconsistency-in-simfactory-submission#comment-59534195</a>: I picked an hybrid job that uses OpenMP and MPI because for a pure MPI job the number of threads/cores is the same as the number of MPI ranks so there would be no difference in the <code>--ntasks-per-node</code> value no matter whether it counted the MPI ranks or the threads.</p>
<p>For the hybrid job shown though there are 4 MPI ranks per node (2 nodes, 8 ranks total) but <code>--ntasks-per-node</code> is set to <code>24</code> and not <code>4</code> which would be <code>@NODE_PROCS@</code>. </p>
<p>Hence me statement that not all SLRUM clusters use SLURM’s <code>--ntasks-per-node</code> variable (or by induction “tasks”) in the same way and thus one must expect inconsistencies between SLURM using submit and run scripts on different SLURM using clusters. These inconsistencies are induced by the clusters being different.</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>