Resolve "Default to using the LALCBCWaveformGenerator"

Closes #244 (closed) defaulting to the LALCBCWaveformGenerator which provides enhanced checking of the waveform

changed milestone to %1.0.7

added Improvement label

requested review from @colm.talbot

assigned to @gregory.ashton

It looks like the new waveform generator is thoroughly broken. The enum we are using isn't swig wrapped, we should probably have noticed that. This will need a fix in Bilby.

mentioned in merge request bilby!1140 (merged)

added 19 commits

• 17f95025...0afc3617 - 18 commits from branch master
• f15e278c - Merge remote-tracking branch 'origin/master' into 244-default-to-using-the-lalcbcwaveformgenerator

Compare with previous version

This is failing due to a bug with pesummary and the latest seaborn release. I submitted a fix in pesummary!705 (merged).

mentioned in merge request !459 (merged)

added 6 commits

• f15e278c...a7515aac - 4 commits from branch master
• 4977156c - Merge branch 'master' into 244-default-to-using-the-lalcbcwaveformgenerator
• 262bebd4 - Merge branch '244-default-to-using-the-lalcbcwaveformgenerator' of...

Compare with previous version

added 3 commits

• 262bebd4...7600db53 - 2 commits from branch master
• f549dab7 - Merge branch 'master' into 244-default-to-using-the-lalcbcwaveformgenerator

Compare with previous version

@colm.talbot are you happy with this switch over?

resolved all threads

approved this merge request

merged

mentioned in commit 7a5c433c