<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>Hi all, after discussing with the other authors and maintainers of Canuda/Scalar, we decided to merge TwoPunctures_BBHSF from the branch <code>proposal_ET_2023_05</code> into <code>master</code>. So any updates or bug fixes for the new thorn will happen on <code>master</code>, and <code>proposal_ET_2023_05</code> would not be maintained.</p>
<p><span class="ap-mention" data-atlassian-id="557058:59e031ba-9bb5-4298-a472-7b99d0ae6f22">@Roland Haas</span> could we update the manifest thornlist to use the master branch for Scalar? Should we make another pull request for the change, or can the release team just make the changes?</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>