<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 Roland Haas):</p>
<p>right. TwoPunctures just generates some ID at very low resolution. The <code>Meudon_Bin_Foo</code> thorns do not have tests. <code>FLRWSolver</code> uses a special “no data file needed” setup for its test. CarpetIOHDF5 has some recover tests (and ID reader) in carpet/CarpetIOHDF5/test/input_initial_data.par and some data files for that (15k data). Same with einsteininitialdata/ReadInterpolate/test/synthetic.par (1MB data). 80MB is definitely too large. Ideally the files would <1MB (they don’t need to be physically sane, so very few modes and few should be sufficient).</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>