<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>Comment (by Gabriele Bozzola):</p>
<p>Upon further reflection, and reading more carefully the previous message, my impression is that there’s no easy way to implement a <code>compute_every</code> function. I originally implemented the function following <code>WeylScal4</code>, which simply takes the modulo of the current iteration and the <code>compute_every</code> parameter. But, if I understand what is going on, this is not the correct thing to do, as I can see in my test runs (unless <code>compute_every</code> is 1). </p>
<p>So, should <code>compute_every</code> be removed from the <code>canuda</code> codes and <code>WeylScal4</code> ? (Or at least, forced to be 1 for backwards compatibility)</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>