-
Notifications
You must be signed in to change notification settings - Fork 39
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
Added warning and automatic fix for no bounds #166
Conversation
… into dev_bounds_warning
Can you please fix the merge conflict? |
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.
Code looks good to me, but I did not test
… into dev_bounds_warning
Done! |
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.
Code looks fine to me, but I did not try running it. @mattiarighi Could you please test?
I would suggest @nperezzanon to test it, since she reported the issue in #151. |
@nperezzanon can you please test this so it can be merged? |
@mattiarighi Can you have a look at this please? Or maybe @axel-lauer can test, because this is a feature he requested? |
@axel-lauer any use case for testing this? |
Just got aware of this via @jhardenberg's mention in #470. Every time this is actually used it masks a serious data error. What's more, |
I agree with you that this can lead to errors, but:
This is the kind of issue in which the trade-off strictness - usability we are discussing every time shows off in all its glory |
Regarding usability vs compliance, the case doesn't seem so clear. I absolutely think this can be fixed, so high usability from a user point of view, but imho really only on a case by case basis. |
Maybe we can revisit this after #374 is merged, because then we could only apply the guess bounds when using reduced cmor check strictness? |
As discussed in #151