<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>Yes, I will remove NPScalars_SF from the PR on the manifest. About the REPO_BRANCH, is it possible for us to use a separate branch from master for our proposal for the next release?</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>