<html>#2630: WaveMoL example computes energy from unsynchronized grid variables
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Roland Haas</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>The WaveMoL example in CactusExamples computes the wave energy as <code>E = phi_t**2 + phi_i*phi_i</code> over the whole grid. However it does so on <code>MoL_PostStep</code> and ends up doing so before it applies boundary conditions and <code>SYNC</code> to the evolved variables (<code>phi</code>, <code>phi_t</code> and <code>phi_i</code>).</p>
<p>Pull request <a data-is-external-link="true" href="https://bitbucket.org/cactuscode/cactusexamples/pull-requests/3/wavemol-compute-energy-only-after-field-is" rel="nofollow">https://bitbucket.org/cactuscode/cactusexamples/pull-requests/3/wavemol-compute-energy-only-after-field-is</a> addresses this.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2630/wavemol-example-computes-energy-from'>https://bitbucket.org/einsteintoolkit/tickets/issues/2630/wavemol-example-computes-energy-from</a></p>
</html>