Skip to content
Snippets Groups Projects

Don't necessarily overwrite luminosity distance if redshift is supplied

All threads resolved!

For cosmology studies, it is conceivable that a user will generate their own precomputed dL -> z mapping and save both of these values in the injection parameters, along with source-frame masses. Currently, in this case the conversion function will ignore the dL supplied by the user and overwrite it such that it uses the Planck15 dL given the supplied redshift.

This fix works under the assumption that if the user has supplied both z and dL, they have confirmed that they are related by the intended cosmology a priori.

Merge request reports

Checking pipeline status.

Approved by

Merged by Gregory AshtonGregory Ashton 2 years ago (Oct 21, 2022 8:28am UTC)

Pipeline #469547 passed

Pipeline passed for 6780f567 on master

Test coverage 65.00% (0.00%) from 1 job

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • I'm happy for this to be added, as it should be an efficiency improvement when these calculations are not needed.

    The recommended use would be to use the built-in cosmology setter.

    If one is using a fixed different cosmology, this can be called once at the top of the script.

    If the cosmology is being sampled over, I would recommend wrapping this conversion function first, update the cosmology in the wrapper through the above function, and then call convert_to_lal_binary_black_hole....

    I guess there are other cases where people care about, for example, peculiar velocities that I haven't thought about, but I think that should be handleable with the above suggestion.

  • Colm Talbot
  • Jacob Golomb added 1 commit

    added 1 commit

    • d6334874 - Update bilby/gw/conversion.py

    Compare with previous version

  • Gregory Ashton changed milestone to %1.3.0

    changed milestone to %1.3.0

  • Colm Talbot resolved all threads

    resolved all threads

  • @jacob.golomb please can you update to the latest version of master? That should fix the CI.

  • Jacob Golomb added 1 commit

    added 1 commit

    Compare with previous version

  • Jacob Golomb added 19 commits

    added 19 commits

    Compare with previous version

  • Jacob Golomb added 1 commit

    added 1 commit

    Compare with previous version

  • Jacob Golomb added 1 commit

    added 1 commit

    Compare with previous version

  • Jacob Golomb added 1962 commits

    added 1962 commits

    Compare with previous version

  • Colm Talbot approved this merge request

    approved this merge request

  • Gregory Ashton approved this merge request

    approved this merge request

  • Colm Talbot resolved all threads

    resolved all threads

  • Gregory Ashton mentioned in commit 6780f567

    mentioned in commit 6780f567

  • Please register or sign in to reply
    Loading