<html>#2414: include con2prim framework by Siegel, Moesta et al. into ET
<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>on hold</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 Pedro Espino):</p>
<p>We have interfaced the implementation of con2prim with IllinoisGRMHD and EOS_Omni, including the evolution of the electron fraction. We’ve achieved a stable evolution of a TOV star and a BNS built using LORENE. We are currently diagnosing the convergence of the hydro solution using several initial data thorns, including RNS (already within the toolkit) and our own thorn which imports initial data generated using the Cook et al. code. Generation of reliable TOV initial data has been a problem, as we find inconsistencies between the ID generated by different thorns. A lot of time has gone into debugging RNS, and we now recognize that EOS tables with many entries are required. I plan on reporting the convergence rate of our hydro solution once these ID errors have been sorted out.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2414/include-con2prim-framework-by-siegel'>https://bitbucket.org/einsteintoolkit/tickets/issues/2414/include-con2prim-framework-by-siegel</a></p>
</html>