<html>#178: New command that runs non-interactively
<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>resolved</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>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>Changes (by Roland Haas):</p>
<p><table>
<tr><td>status:</td><td>resolved (was new)</td></tr>
</table></p>
<p>SimFactory should offer a command that is halfway in between "submit" and run". This command should start a simulation immediately, but should run it in the background while redirecting stdout and stderr to the usual locations in the simulation's output directory.</p>
<p>Technically, this command would be on the same level as "submit", while "run" would reside at a lower level. For example, "run" would expect an active simulation (and would not activate a simulation), while this new command would activate the simulation.</p>
<p><strong>Keyword:</strong></p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/178/new-command-that-runs-non-interactively'>https://bitbucket.org/einsteintoolkit/tickets/issues/178/new-command-that-runs-non-interactively</a></p>
</html>