<html>#931: CartGrid3D's dependency on Boundary
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Jian Tao</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>Cactus_4.0.0</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>Cactus</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>I don’t think there is anything actually to do here. CartGrid3D scheduling its ApplyBCs routine in Boundary’s group becomes a no-op of thorn Boundary is not running (as intended). It does not introduce a dependency, between the two (at least for “old” uses of CartGrid3D that did not use Boundary before that thorn came into existence). The aliased function <code>Boundary_SelectedGVs</code> from thorn Boundary is used in only those scheduled functions which only run if <code>Boundary</code> is on. Similarly <code>SymmetryRegister</code> and <code>SymmetryRegisterGrid</code> are in group <code>SymmetryRegister</code> scheduled by SymBase (which also provides those functions).</p>
<p>So, I do not actually see any dependency and would content that the thorn is fine as is. </p>
<p></p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/931/cartgrid3ds-dependency-on-boundary'>https://bitbucket.org/einsteintoolkit/tickets/issues/931/cartgrid3ds-dependency-on-boundary</a></p>
</html>