<html>#2373: kasner example from ET paper cannot be reproduced
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</td></tr>
<tr><td style='text-align:right'> Status:</td><td>resolved</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>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 far as I can tell the parfile in the examples repo, which matches the parfile in the paper repo, never worked as advertised. Certainly not with the Curie release (the release version at the time the paper was prepared) and given that Maxwell (the release just after the paper was published) fails with NaN I cannot say if it possibly ever worked with Maxwell.</p>
<p>My own guess would be that when the data for the paper was produced, a modified version of McLachlan was used that had gauge evolution disabled. No version of McLachlan of any release has <code>lapse_evolution_method</code> appear anywhere other than in <code>param.ccl</code> so no version could have respected it being set to <code>static</code>. Since ML_BSSN e.g, has its own <code>ML_lapse</code> group, even having <code>ADMBase</code> reset <code>alp</code> to 1 after each step would not avoid the metric blowing up since <code>alp</code> is no used for input by ML_BSSN.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2373/kasner-example-from-et-paper-cannot-be'>https://bitbucket.org/einsteintoolkit/tickets/issues/2373/kasner-example-from-et-paper-cannot-be</a></p>
</html>