<html>#2534: Evolution of grid arrays with Mol no longer works
<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></td></tr>
<tr><td style='text-align:right'> Version:</td><td>development version</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>Somewhat unrelated: instead of the current workaround for arrays of</p>
<blockquote>
<p>The kludge was to check to see that if the "correct" component is being updated, and if not, re-write the old values of the grid array).</p>
</blockquote>
<p>wouldn’t it be possible ot make this work by scheduling the RHS function as <code>GLOBAL</code> ? That way it would only execute once per iteration and not once per iteration per refinement level. MoL would still update the state vector for the array but b/c it initializes the RHS to zero before the <code>CalcRHS</code> schedule group the fact that the RHS routine does not run would leave the RHS unchanged (ie 0) and thus effectively no update would be done.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2534/evolution-of-grid-arrays-with-mol-no'>https://bitbucket.org/einsteintoolkit/tickets/issues/2534/evolution-of-grid-arrays-with-mol-no</a></p>
</html>