<html>#2670: Refinement prolongation: All points must have been received
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td></td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td>ET_2022_05</td></tr>
<tr><td style='text-align:right'> Version:</td><td>ET_2022_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>Carpet</td></tr>
</table>
<p>Comment (by Roland Haas):</p>
<p>These errors are usually caused by issues with the grid setup that develop over time in the simulation. The error is unfortunately only detectable deep inside of Carpet where the original cause is no longer obvious. With just the error message it is not really possible to help diagnose it. </p>
<p>To help with this, more information is needed:</p>
<ol>
<li>the <code>.out</code> and <code>.err</code> files produced by the simulation</li>
<li>the RunScript as found in output-NNNN/SIMFACTORY</li>
<li>the SubmitScript as found in output-NNNN/SIMFACTORY</li>
<li>if a public cluster, the name of the cluster used, otherwise the option list used</li>
</ol>
<p>With those it may be possible to provide meaningful advise. Otherwise shot in the dark suggestion would be: </p>
<ol>
<li>do not use too many MPI ranks (no more than 128 for a mid res BNS run), this avoids the domain parts assigned to each MPI rank becomming too small</li>
<li>check if your box locations have moved out of the grid (ie something went wrong with tracking)</li>
<li>check for NaNs in evolution variables</li>
</ol>
<p></p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2670/refinement-prolongation-all-points-must'>https://bitbucket.org/einsteintoolkit/tickets/issues/2670/refinement-prolongation-all-points-must</a></p>
</html>