<html>#2745: Inclusion of GRHayL library and associated MHD thorns
<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>new</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>Sorry, I was actually working on that right now. Also, there’s been some internal pressure to make sure this gets in this release, but I am not sure how feasible it is to actually get them all ready. However, I at the very least would like to see if I can get <code>GRHayLib</code>, <code>GRHayLID</code>, and <code>GRHayLHD</code> in.</p>
<p>I did push changes that should make the Balsara1 test work. We had switched the thorn from using its own copies of HydroBase to directly using HydroBase variables, which led to the issues you saw in regards to <code>rho</code> and <code>P</code>.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2745/inclusion-of-grhayl-library-and-associated'>https://bitbucket.org/einsteintoolkit/tickets/issues/2745/inclusion-of-grhayl-library-and-associated</a></p>
</html>