<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 Roland Haas):</p>
<p>As a suggestion: there is a Cactus parameter </p>
<div class="codehilite"><pre><span></span><code>Cactus::schedule_sort_mode = "descending"
</code></pre></div>
<p>also "non", the default, or "ascending".</p>
<p>Which can be used to willfully change the ordering of scheduled functions without any explicit <code>AFTER</code> or <code>BEFORE</code> relation. A correctly written <code>schedule.ccl</code> should be unaffected. While one that relies on accidental order would fail.</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>