<html>#2950: CarpetX/ADMBaseX: Missing ADMBase features (Conditional storage, evolution parameters)
<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></td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>bug</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>CarpetX</td></tr>
</table>
<p>Very similar to <a href="https://bitbucket.org/einsteintoolkit/tickets/issues/2948/hydrobasex-missing-hydrobase-features-aphi" rel="nofollow" title="HydroBaseX: Missing HydroBase features (Aphi GF, conditional storage, split init)" class="ap-connect-link">#2948</a>, but smaller in scope. Mostly consistency and future proofing in mind. All changes are following the previous Carpet ADMBase conventions.</p>
<ol>
<li>Missing conditional storage on the extra fields (shift, dtlapse, dtshift).</li>
<li>Missng <code>*_evolution_method</code> parameters specifying which thorn evolves which fields.</li>
<li>ADMBaseX defaults to an initial dtlapse/dtshift of <code>zero</code> instead of <code>none</code> (previously in Carpet ADMBase). With conditional storage it probably makes sense to return to the <code>none</code> default to only enable the extra fields if the user needs them. Changing this default here may break some test parameter files.</li>
</ol>
<p>Addressed by CarpetX <a data-is-external-link="true" href="https://github.com/EinsteinToolkit/CarpetX/pull/386" rel="nofollow">PR #386</a></p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2950/carpetx-admbasex-missing-admbase-features'>https://bitbucket.org/einsteintoolkit/tickets/issues/2950/carpetx-admbasex-missing-admbase-features</a></p>
</html>