<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 Zach Etienne):</p>
<p>No it’s fully backportable for current Baikal* thorns, as it produces correct behavior in all cases Baikal* supports. (Currently Baikal* does not support symmetries, as was the nature of the problem with the other ticket.) We confirmed this patch fixes a bug in current Baikal*.</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>