<html>#864: Improve error reporting in Multipole
<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></td></tr>
<tr><td style='text-align:right'> Version:</td><td></td></tr>
<tr><td style='text-align:right'> Type:</td><td>enhancement</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>minor</td></tr>
<tr><td style='text-align:right'>Component:</td><td>EinsteinToolkit thorn</td></tr>
</table>
<p>Changes (by Roland Haas):</p>
<p><table>
<tr><td>status:</td><td>open (was new)</td></tr>
</table></p>
<p>When Multipole encounters an interpolation error, the error output from the interpolator consists of thousands of lines each listing the points that failed. This is too much information to process. It is also not clear that the error came from Multipole.</p>
<ol>
<li>This output should be limited;</li>
<li>The error should be prefixed with "Multipole" so the user knows which thorn was responsible for calling the interpolator (maybe the new CCTK_ScheduleQueryCurrentFunction from #817 could be used for this);</li>
<li>Multipole should contain a check in CCTK_PARAMCHECK that the extraction radii are not outside the Cactus base grid.</li>
</ol>
<p><strong>Keyword:</strong></p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/864/improve-error-reporting-in-multipole'>https://bitbucket.org/einsteintoolkit/tickets/issues/864/improve-error-reporting-in-multipole</a></p>
</html>