<html>#2697: Include BBH+scalar field initial data code from Canuda in ET
<table style='border-spacing: 1ex 0pt; '>
<tr><td style='text-align:right'> Reporter:</td><td>Cheng-Hsin Cheng</td></tr>
<tr><td style='text-align:right'> Status:</td><td>new</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>major</td></tr>
<tr><td style='text-align:right'>Component:</td><td></td></tr>
</table>
<p>Comment (by Cheng-Hsin Cheng):</p>
<p><span class="ap-mention" data-atlassian-id="557058:088051f9-5b94-4b5e-bfbe-71137030b9c1">@Samuel Cupp</span> <span class="ap-mention" data-atlassian-id="557058:f7fd5133-6eee-4385-a5e5-3e03342a0b24">@Peter Diener</span> Apologies for the lack of updates on NPScalars_SF. But Helvi and Giuseppe and I were only discussing today about withdrawing it from inclusion into the next ETK release, and instead to update the original NPScalars thorn in the future to support other matter terms including scalar fields. From what I understand, Miguel thinks this would be a better decision for the code too. So we would like to retract NPScalars_SF from the next release, and Peter is off the hook from reviewing it.</p>
<p>Dropping NPScalars_SF will affect the parameter files in TwoPunctures_BBHSF which are using it, so we will also update the parameter files there to use the original NPScalars.</p>
<p>--<br/>
Ticket URL: <a href='https://bitbucket.org/einsteintoolkit/tickets/issues/2697/include-bbh-scalar-field-initial-data-code'>https://bitbucket.org/einsteintoolkit/tickets/issues/2697/include-bbh-scalar-field-initial-data-code</a></p>
</html>