-
Notifications
You must be signed in to change notification settings - Fork 321
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
Validators/permissive multiples #852
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
4a0e987
add a PermissiveMultiples validator
WilliamHPNielsen 339991e
Add a new validator for non-integer multiples + a test
WilliamHPNielsen b2a5364
Match call signatures
WilliamHPNielsen 739623d
Now actually match them :)
WilliamHPNielsen 004387c
Make Multiples and PermissiveMultiples numeric
WilliamHPNielsen 8087cc0
Merge branch 'master' into validators/PermissiveMultiples
WilliamHPNielsen 3543dcf
add the promised precision test
WilliamHPNielsen cffd096
add a __repr__ of PermissiveMultiples
WilliamHPNielsen 27da004
Merge branch 'validators/PermissiveMultiples' of github.com:QCoDeS/Qc…
WilliamHPNielsen ac6df3a
Merge branch 'master' into validators/PermissiveMultiples
WilliamHPNielsen 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 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 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
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.
Should this have a relative tolerance too?
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.
Mimicking
np.allclose
? I am a bit undecided. I think for most cases it will suffice to say "be precise to within 0.5 nV".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.
Yes as long as people are not using "strange" units its fine, we can always add later if needed