Skip to content
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

Validate timeseries data using explicit value and rtol #866

Closed

Conversation

danielhuppmann
Copy link
Member

Please confirm that this PR has done the following:

  • Tests Added
  • Documentation Added
  • Name of contributors Added to AUTHORS.rst
  • Description in RELEASE_NOTES.md Added

Description of PR

This PR adds keyword arguments to validate() to use value and rtol directly instead of upper_bound and lower_bound, in response to the discussion in IAMconsortium/common-definitions#104. However, now that I've implemented this, I'm wondering whether it wouldn't make more sense to keep the pyam method lean and do the translation from value and rtol as part of a nomenclature.DataValidator class...

Any thoughts @phackstock?

Copy link

codecov bot commented Jul 20, 2024

Codecov Report

Attention: Patch coverage is 92.59259% with 2 lines in your changes missing coverage. Please review.

Project coverage is 94.9%. Comparing base (ddbb88e) to head (5789802).
Report is 31 commits behind head on main.

Files Patch % Lines
pyam/validation.py 91.6% 2 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##            main    #866     +/-   ##
=======================================
- Coverage   95.0%   94.9%   -0.1%     
=======================================
  Files         64      63      -1     
  Lines       6134    6164     +30     
=======================================
+ Hits        5828    5855     +27     
- Misses       306     309      +3     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@danielhuppmann
Copy link
Member Author

After some thoughts, I concluded that implementing this feature in nomenclature makes more sense.
Closing in favor of IAMconsortium/nomenclature#370.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant