<html>#2747: Inclusion of sgrid importer in Einstein Toolkit
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Samuel Cupp</td></tr>
<tr><td style='text-align:right'> Status:</td><td>open</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td>ET_2023_11</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>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>EinsteinToolkit thorn</td></tr>
</table>
<p>Comment (by Samuel Cupp):</p>
<p>This test is trying to use <code>NSTracker</code>, which I don't think is part of the Einstein Toolkit. My guess is that its one of the unrunnable tests mentioned at the top. Can you just get rid of that thorn? </p>
<p>Also, the parfile says its going to run to a final time of <code>2500</code>, which (unless this runs very quickly) is incorrect for a test. This isn’t going to run long, if at all, and it should be a minimal code test, not a physics test. So the grid doesn’t have to be well resolved. You can almost certainly move the outer boundary closer, and maybe remove some refinement levels. I’d say the iterations should probably be less than 10, especially if you’re doing full GRMHD.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2747/inclusion-of-sgrid-importer-in-einstein'>https://bitbucket.org/einsteintoolkit/tickets/issues/2747/inclusion-of-sgrid-importer-in-einstein</a></p>
</html>