-
Notifications
You must be signed in to change notification settings - Fork 10
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
Pipeline requires explicit arguments for QuantileDeltaMappingCorrection #211
Conversation
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.
This looks good. Whats up with that one test? Random failure? Maybe just rerun failed tests?
Can you add another PR with the "extend and smooth" feature?
Can you also add no_trend kwarg to the base DataHandler object? |
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.
Could we add an integration test in the forward pass testing suite?
@castelao The mac tests might pass after you rebase on main (aka remove the netCDF4 dep) |
1d43216
to
aac6a8f
Compare
@castelao looks good but can you add the |
aac6a8f
to
4383803
Compare
@bnb32 , is this still a request? |
Shall we merge this one? Is it missing anything? |
All good! |
As requested by @grantbuster, to qdm_bc() can pass along a 'no_trend' option to QDM correction.
Bug introduced on f0840f2
It's possible to infer the resulting offset from the theory, so we don't need to save the full matrix of outputs.
Validate two aspects: - We should be able to run a forward pass in a unbiased data. - The bias trend should be observed in the predicted output.
clean: Unused variables style: unused variable
1cfaf51
to
aea7b34
Compare
Pipeline requires explicit arguments for QuantileDeltaMappingCorrection
@grantbuster raised the point that the pipeline system requires explicit argument to orchestrate the inputs.