#2697: Include BBH+scalar field initial data code from Canuda in ET

Reporter: Cheng-Hsin Cheng Status: new Milestone: Version: Type: enhancement Priority: major Component:

Comment (by Roland Haas):

Right now the code for TwoPunctures_BBHSH in the ET manifest thornlist is from branch `proposal_ET_2023_05` in Canuda. While ok in principle it is a bit strange to not have this eg in either development (since it saw changes) or master (which for Canuda seems to be the “trusted” branch). If included in the ET the code is expected to be “good' and what the authors use themselves.

Eg for sure for the eventual release the changes must be in an `ET_2023_05` branch which normally should be a child of the trusted branch (`master` in this case).

Since the ET manifests `master` branch is not the “trusted good” but the “bleeding edge” branch (for the ET), one should be able to pick up bug fixes on ET released thorns in it without changing branches. With `proposal_ET_2023_05` does seems unlikely since I would expect bug fixes to show up either in `development` or `master`of Scalar, wouldn't they?

-- Ticket URL: https://bitbucket.org/einsteintoolkit/tickets/issues/2697/include-bbh-scalar...