Resolve "GW-specific result object"

Closes #251 (closed)

changed milestone to %0.3.5

assigned to @gregory.ashton

added 1 commit

• 8bd8ac4a - Add GW-specific result object

Compare with previous version

@charlie.hoy this may be of interest to you. The idea is that the result object produced will have properties for all the things that you'll want to access. For example, to get the waveform_approximant it will be as simple as

result.waveform_approximant

Under the hood, everything is stored in the meta_data attribute. The CBCResult just knows how to unpack it. By doing it this way, we can change how the meta data is stored in future versions while maintaining backward compatibility.

added 1 commit

• 07ff25b9 - Fix pymc3 issues

Compare with previous version

added 1 commit

• 5d6fe92c - Add missing result file

Compare with previous version

unmarked as a Work In Progress

approved this merge request

approved this merge request

unapproved this merge request

@gregory.ashton you should add something to the changelog for this before we merge.

resolved all discussions

approved this merge request

merged

mentioned in commit 6dd4a238