<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 Steven R. Brandt):</p>
<p>I chose the term “total threads” because that’s what all of the documentation uses. You have stated previously that you think you don’t want to support the terminology in the documentation. There is a PR (the `fixsub` branch of simfactory) which implements <code>--total-threads</code>. It also introduces <code>--nodes</code> and <code>--node-procs</code> which (I think) is the functionality you are suggesting with <code>--ranks</code> or <code>--mpi-ranks</code>. It also introduces <code>--test</code> to see whether the simfactory options you provide do what you think they do.</p>
<p>I would be perfectly happy to name all these options something different, but I would like to see this PR accepted in some form, as both <code>--procs</code> and <code>--cores</code> are not the things that they are named after. I have frequently been confused by the behavior of these parameters. </p>
<p>An alternative to the <code>--total-threads</code> would be to simply get rid of the smt stuff, which was the source of much confusion for me.</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>