<html>#499: Prolongation fails with vectorisation enabled
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Ian Hinder</td></tr>
<tr><td style='text-align:right'> Status:</td><td>closed</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>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Carpet</td></tr>
</table>
<p>Changes (by Roland Haas):</p>
<p><table>
<tr><td>status:</td><td>closed (was new)</td></tr>
</table></p>
<p>The development version of Carpet uses vectorisation to speed-up prolongation. This fails with various errors, including corruption of the malloc heap.</p>
<p>I am reducing the priority, and still hope to get to the bottom of this before the release.</p>
<p><strong>Keyword:</strong></p>
<p>Comment (by Roland Haas):</p>
<p>Datura and Damiana (the clusters mentioned here) no longer exists. However most clusters by now use VECTORIZE=yes by default and the issue is not seen there. The parameter use_random_restart_hill_climbing no longer exists, its function having (likely) been taken over by use_random_restart_hill_climbing which defaults to 0 since otherwise LoopControl remembers too many tries, becoming slow and using too much memory (the likely cause of the issue here).</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/499/prolongation-fails-with-vectorisation'>https://bitbucket.org/einsteintoolkit/tickets/issues/499/prolongation-fails-with-vectorisation</a></p>
</html>