-
Notifications
You must be signed in to change notification settings - Fork 139
MAINT: tweaks to prior constraints #1096
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
mj-will
wants to merge
6
commits into
bilby-dev:main
Choose a base branch
from
mj-will:improve-prior-constraints
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
cef9ebc
ENH: raise an error if constraint key is missing from samples
mj-will a9b8fdd
MAINT: remove unreachable if statement
mj-will d65404e
TST: add tests for evaluate constraints
mj-will 717f8e5
TST: add test for prior normalization
mj-will b4de671
ENH: add `strict` option to `evaluate_constraints`
mj-will a7e2493
TST: add tests for `strict` in `evaluate_constraints`
mj-will File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why has this been removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My understanding was that this was a hacky check for if there aren't any constraints. Prior to #1028,
evaluate_constraintswould return1.0if there weren't any constraints, so this would skip the rest of this function.After the changes 1028, that only happens if the
sampling_chunk=1is, so it's not clear to me this actually serves it's intended purpose.Looking at this again, I think the lines above this may be redundant as well and this whole thing could be replaced with a
has_constraints(or similar) property.