<html>#2030: Multi-block boundaries leave uninitialized boundary points
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Erik Schnetter</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>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>EinsteinToolkit thorn</td></tr>
</table>

<p>Changes (by Roland Haas):</p>
<p><table>
<tr><td>assignee:</td><td>Erik Schnetter (was )</td></tr>
<tr><td>responsible:</td><td>[] (was )</td></tr>
</table></p>
<p>Applying multi-block boundaries can leave uninitialized boundary points. This happens when multi-block boundaries are used in combination with another boundary condition that looks at the interior of the grid, such as e.g. a symmetry condition or radiative / extrapolating boundaries.</p>
<p>There is another bug currently in McLachlan that applies its "scalar" boundary conditions to too few grid points (it uses "BoundaryNoSync" instead of "Boundary"), which means there are uninitialized boundary points for <code>initial_boundary_condition = "scalar"</code> as well in multi-block systems.</p>
<p><strong>Keyword:</strong></p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2030/multi-block-boundaries-leave-uninitialized'>https://bitbucket.org/einsteintoolkit/tickets/issues/2030/multi-block-boundaries-leave-uninitialized</a></p>
</html>