<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 Roland Haas):</p>
<p>I will have to write proper documentation still., which will document these,</p>
<p>I am be quite reluctant to add new options to the command line since it can easily become a mess. For more complex use cases, using it as a Python module and calling the POWER or Nakano routines directly is the preferred way of using it.</p>
<p>The thinking is that “module options” will be things that would be identical between simulations while function arguments are things that change from one simulation to the next.</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>