<html>#2601: Add four more parameters for carpet
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Liwei Ji</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>development version</td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Carpet</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>Thank you. I think with those things should be good to go. With the addition of adding this parfile as a test case to Carpet. Shiftout is ok since without the shiftout the first boundary point is exactly on the boundary (eg at -1.0) and there are not <code>boundary_size</code> points <em>outside</em> of the nominal domain (but <code>boundary_size - 1</code>). This is actually intentional since it helps with convergence to have the boundary point stay fixed.</p>
<p>Weren’t there plans at one point for SphericalNR to support / use mesh refinement on top of the spherical coordinates? In that case one would have to update this code it would seem.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2601/add-four-more-parameters-for-carpet'>https://bitbucket.org/einsteintoolkit/tickets/issues/2601/add-four-more-parameters-for-carpet</a></p>
</html>