<html>#2413: Include "POWER" code to extrapolate waveforms to scri+ into ET
<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>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>task</td></tr>
<tr><td style='text-align:right'> Priority:</td><td>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td>EinsteinToolkit thorn</td></tr>
</table>
<p>Comment (by Gabriele Bozzola):</p>
<p>I would like to use POWER to validate kuibit.</p>
<p>I downloaded the code and use it (but haven’t compared against kuibit yet) and I have some suggestions for future improvements:</p>
<ul>
<li>It would be nice to be able to control explicitly the parameters via command-line, e.g., the ADMmass or the cutoff frequency. Depending on <code>TwoPunctures</code> limits the applicability of the tool.</li>
<li>The function <code>getFinalSpinFromQLM</code> assumes that scalars are output as one group per file</li>
<li>If one passes as folder <code>.</code>, then the output will be hidden files</li>
<li>It would be nice to be able use the code on arbitrary directory structures </li>
</ul>
<p>Other than that, thanks for the tool, I am looking forward to using it more carefully.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2413/include-power-code-to-extrapolate'>https://bitbucket.org/einsteintoolkit/tickets/issues/2413/include-power-code-to-extrapolate</a></p>
</html>