<html>#2631: Meudon_BinNS fails if initial_dtshift or initial_dtlapse is set to an unexpected value
<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>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></td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>There’s also a bug in that setting <code>dtalp</code> requires computing spatial derivatives (via SummationByParts <code>Diff_Gv</code> aliased function) so that it can only be computed in the interior, but no SYNC or boundary condition is applied. The easiest fix to this (since boundary conditions applied to initial data are tricky) would likely be to compute <code>alp</code> on a grid larger than the Cactus grid so that <code>dx_alp</code> can be computed on the whole Cactus grid.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2631/meudon_binns-fails-if-initial_dtshift-or'>https://bitbucket.org/einsteintoolkit/tickets/issues/2631/meudon_binns-fails-if-initial_dtshift-or</a></p>
</html>