Allow rescaled priors from gracedb
This MR will automatically do the ROQ scaling for events from gracedb.
- There's a new template for online priors. This takes mass and distance bounds.
- The prior file is written to the output directory and then used from there.
- The distance marginalisation lookup table isn't currently working as expected...
- Low and high-mass events will be scaled.
- I extended the timeout time for the ping of Google. It was failing for my connection.
- I added the default distances to utils.
- Some cleanup of the gracedb module with improved help messages (pointing out the reliance on CIT infrastructure)
- Fix bugs with bilby version 0.5.2
Merge request reports
Activity
- Resolved by Gregory Ashton
Am I right to understand this deprecates the high mass prior as it will never be used by the gracedb script right? I'm okay with that, I just want to understand the changes.
Can you explain what you mean by the distance lookups are not working?
Once this is ready, could you (or someone else) check if with these changes a low-mass and high-mass gracedb event start sampling, e.g.
$ bilby_pipe_gracedb --gracedb G330564 --submit $ bilby_pipe_gracedb --gracedb G334993 --submit
or any other combination.
- Resolved by Gregory Ashton
Also it is failing the tests due to the
determine_prior_file_from_parameters
being removed and that it now assumes that/home/cbc/
etc exists.
added 1 commit
- 5b0f9b4e - fix path for distance marginalisation lookup table
added 13 commits
-
256a8914...e42d2b78 - 12 commits from branch
master
- dad7a6a9 - Merge branch 'master' into rescale-bns-prior
-
256a8914...e42d2b78 - 12 commits from branch
added 4 commits
-
dad7a6a9...98e26945 - 2 commits from branch
master
- bbc8d008 - Merge branch 'master' into rescale-bns-prior
- bb91c6dd - Fix test errors and simplify gracedb script
-
dad7a6a9...98e26945 - 2 commits from branch
changed milestone to %0.2.1
enabled an automatic merge when the pipeline for 258d1248 succeeds
mentioned in commit a112def5