<html>#2432: backport Baikal boundary handling fix to release branch
<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>open</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td></td></tr>
<tr><td style='text-align:right'> Version:</td><td>ET_2020_05</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>Please see <a data-is-external-link="true" href="https://bitbucket.org/einsteintoolkit/tickets/issues/2288/#comment-58230880" rel="nofollow">https://bitbucket.org/einsteintoolkit/tickets/issues/2288/#comment-58230880</a> for an explanation for why the currently observed behaviour does not show bug-freeness. As far as I can tell the current code depends on the fact that Carpet puts a non-zero poison value in cctk_bbox. If it was not doing so then the code would not run. The only reason that it does not fail is an accident.</p>
<p>Note that there is a difference between no error being observed with a single test run and the code being bug-free (the latter means that it is expected to work in all cases). I am not claiming that you are not seeing that things seem to work, I am claiming that they work only be accident and there is not guarantee they will continue to do so.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2432/backport-baikal-boundary-handling-fix-to'>https://bitbucket.org/einsteintoolkit/tickets/issues/2432/backport-baikal-boundary-handling-fix-to</a></p>
</html>