<html>#380: The number of timelevels for the AHFinder mask needs to be set to something intelligent.
<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>open</td></tr>
<tr><td style='text-align:right'>Milestone:</td><td>ET_2020_04</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>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>Other</td></tr>
</table>
<p>Changes (by Roland Haas):</p>
<p><table>
<tr><td>assignee:</td><td>Roland Haas (was )</td></tr>
<tr><td>responsible:</td><td>[] (was )</td></tr>
<tr><td>milestone:</td><td>ET_2020_04 (was )</td></tr>
</table></p>
<p>The number of timelevels for AHFinderdirect::ahmask has to be set to something intelligent. Setting it to some fixed number doesn't work, because the number of timelevels for a given time-integrator might be different and Carpet chokes in that situation. At the moment it's set to how-many timelevels ADMBase::metric has, but that's also not good because that might be 1, while ahmask should have more. We cannot couple AHFinderDirect to any evolution thorn or Carpet as well. We might have to introduce a new parameter, but I would like to avoid this if somehow possible (which is why I coupled it to the metric in the first place, hoping this would be ok, which is apparently not really the case).</p>
<p><strong>Keyword:</strong></p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/380/the-number-of-timelevels-for-the-ahfinder'>https://bitbucket.org/einsteintoolkit/tickets/issues/380/the-number-of-timelevels-for-the-ahfinder</a></p>
</html>