<html>#2499: New machine thornyflat at WVU
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Erik Schnetter</td></tr>
<tr><td style='text-align:right'> Status:</td><td>open</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td>development version</td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>SimFactory</td></tr>
</table>
<p>Comment (by Erik Schnetter):</p>
<p>The first job you submitted requested 128 cores, which is not a multiple of 40 cores, the number of cores per node. The queuing system does not seem to support this. I recommend using 160 cores instead of 128 cores.</p>
<p>Your second job seems to be waiting the queue just fine. If you want it to start earlier, then you could try asking for a shorter run time. Usually, jobs asking for a longer time take a longer time to start. Start by asking for one hour to see whether it works, then maybe for 24 hours. You could also inquire with the system administrators whether the job’s parameter are fine.</p>
<p>-erik</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2499/new-machine-thornyflat-at-wvu'>https://bitbucket.org/einsteintoolkit/tickets/issues/2499/new-machine-thornyflat-at-wvu</a></p>
</html>