<html>#2497: IllinoisGRMHD is incompatible with setting TmunuBase::stress_energy_at_RHS = "no"
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Gabriele Bozzola</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>development version</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 Roland Haas):</p>
<p>There was some discussion on this in the Einstein Toolkit call just now. The situation seems that one can enable Tmunu storage but disable Tmunu being actually set by setting <code>TmunuBase::stress_energy_storage = yes</code> and <code>TmunuBase::stress_energy_at_RHS = no</code> . <code>TmunuBase</code> relies on running in <code>MoL_PostStep</code>. Since <code>Tmunu</code> is a derived quantity like the primitives it may be most consistent with other codes to have <code>Tmunu</code> set at INITIAL at the same time say <code>HydroBase_Con2PrimInitial</code> is running by scheduling the <code>SetTmunu</code> group in there instead of only in <code>MoL_PostStep</code>. This would rely on checking on <code>ADMSbase_SetADMVars</code> and possible touch <code>HydroBase</code> as well in case setting Tmunu uses primitive variables.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2497/illinoisgrmhd-is-incompatible-with-setting'>https://bitbucket.org/einsteintoolkit/tickets/issues/2497/illinoisgrmhd-is-incompatible-with-setting</a></p>
</html>