<html>#2288: Lean's boundary condition setting for BSSN constraints only fills in a single ghostzone
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Zach Etienne</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>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>EinsteinToolkit thorn</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>Zach may be ignoring the level 1 warning. For this usage case, he can possibly do so (though I am not sure since the results of <code>CoordBase_GetBoundarySizesAndTypes</code> will differ on different MPI ranks since it returns the ghost size for patch boundaries that are not physical boundaries but instead inter-processor boundaries.<br />
<span class="ap-mention" data-atlassian-id="557058:56049c54-f8c2-4b6c-9b88-ab697c967495">@Erik Schnetter</span> <span class="ap-mention" data-atlassian-id="557058:8bc23f2a-45c0-477d-8ac4-a5a16c734278">@Zach Etienne</span> you may need to clarify the suggested code and observed behaviour.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2288/leans-boundary-condition-setting-for-bssn'>https://bitbucket.org/einsteintoolkit/tickets/issues/2288/leans-boundary-condition-setting-for-bssn</a></p>
</html>