<html>#2416: add ReadInterpolate thorn to Einstein Toolkit
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</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></td></tr>
<tr><td style='text-align:right'> Type:</td><td>proposal</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>I removed interpolation in time, so the testsuite does not test it.</p>
<p>The original code was (very) wrong (and cannot have ever worked).</p>
<p>I coded up a version that wold stand a chance of working in a branch "rhaas/timerinterp" (just pushed to GitHub):</p>
<p><a data-is-external-link="true" href="https://github.com/rhaas80/ReadInterpolate/tree/rhaas/timerinterp" rel="nofollow">https://github.com/rhaas80/ReadInterpolate/tree/rhaas/timerinterp</a></p>
<p>but that one will not work either right now due to the CarpetIOHDF5 checkpoint files (the only one with multiple timelevels which would make interpolation in time possible) lacking information what time the actual time levels actually correspond to. There is not enough information present in the files to deduce what time it is based on the cctk_time attribute that is stored, the delta_time attribute in global attributes and the refinement level information, at least not without making assumptions about time refinement factors. So in the end I<br />
shelved time interpolation. If someone needs it and is willing to spend some time working with me testing it the branch can go in as a feature update sometime after the release once it has been actually used in production.</p>
<p>The code can still read in multiple time levels but will only do interpolation in space, requiring that the time step is the same in the source and target simulation (which more or less limits its usefulness to going from a Cartesian to a Llama simulation or so).</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2416/add-readinterpolate-thorn-to-einstein'>https://bitbucket.org/einsteintoolkit/tickets/issues/2416/add-readinterpolate-thorn-to-einstein</a></p>
</html>