<html>#2483: Simfactory job parameters are not consistent
<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>I suspect that <code>--total-threads</code> will still require smt information since <code>--total-threads = --procs * --num-threads</code> so there is no extra information available. The smt stuff is really used for the queuing system since those sometimes need to know whether the code uses smt or not (since they want a ppn like value and that differs between smt and non-smt).</p>
<p>I am not trying to suggest nodes and nodes procs, no. I am suggesting to use the names items used by <code>mpirun</code> which is “number of MPI ranks” and OS threads (<code>OMP_NUM_THREADS</code>). smt will still be required (same reason as for <code>--total-threads</code>). Ie re-use names and nomenclature that people who are using a cluster are already familiar with.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2483/simfactory-job-parameters-are-not'>https://bitbucket.org/einsteintoolkit/tickets/issues/2483/simfactory-job-parameters-are-not</a></p>
</html>