<html>#2629: MoL_PseudoEvolution vs ANALYSIS
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Gabriele Bozzola</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></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></td></tr>
</table>
<p>Changes (by Gabriele Bozzola):</p>
<p>Consider a thorn like <code>NPScalars</code> in the canuda arrangement.</p>
<p><code>NPScalars</code> computes the Newman-Penrose grid functions in the <code>CCTK_ANALYSIS</code> bin. The operation requires taking derivative. Similarly, <code>LeanBSSNMoL</code> computes the constraints in the same bin (this will likely be a regression I introduced in commit <a href="https://bitbucket.org/einsteintoolkit/tickets/commits/80b6b1b" rel="nofollow" class="ap-connect-link">80b6b1b</a>).</p>
<p>My understanding is now that <code>CCTK_ANALYSIS</code> is not the right place where to do this because of interpolation/prolongation/notsurewhat.</p>
<p>Is the fix to simply replace <code>CCTK_ANALYSIS</code> with <code>MoL_PseudoEvolution</code>?</p>
<p>I would like to make sure that this is the case considering also parameters like <code>compute_every</code>. Since these are expensive diagnostics, it is best to compute them only when they are output. Do I get the correct constraints/scalars if I compute and output them only when all the refinement levels are synced?</p>
<p></p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2629/mol_pseudoevolution-vs-analysis'>https://bitbucket.org/einsteintoolkit/tickets/issues/2629/mol_pseudoevolution-vs-analysis</a></p>
</html>