<html>#2929: GRHayLET/IllinoisGRMHD convert_IllinoisGRMHD_to_HydroBase schedule compatibility with VolumeIntegrals_*
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Maxwell Rizzo</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td>ET_2026_05</td></tr>
<tr><td style='text-align:right'> Version:</td><td>ET_2025_05</td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</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 Leonardo Rosa Werneck):</p>
<p>In this case, the issue is not with <code>VolumeIntegrals</code>, but with <code>IllinoisGRMHD</code>. <code>VolumeIntegrals</code> expects <code>HydroBase</code> variables, and when using <code>IllinoisGRMHD</code>, those variables are only set correctly if one explicitly calls the routine that converts from <code>IllinoisGRMHD</code>'s native variables to <code>HydroBase</code>.</p>
<p>This is therefore not a diagnostic issue, but rather a consequence of <code>IllinoisGRMHD</code>'s choice of gridfunctions. For that reason, I think it is reasonable to expect <code>IllinoisGRMHD</code> to handle this conversion, rather than placing that responsibility on the diagnostic thorn.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2929/grhaylet-illinoisgrmhd'>https://bitbucket.org/einsteintoolkit/tickets/issues/2929/grhaylet-illinoisgrmhd</a></p>
</html>