-
Notifications
You must be signed in to change notification settings - Fork 0
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
92/Refactor pressure level modifications #94
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.
Looks logical to me.
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.
Changes look good to me. One small question but not really a necessary change
This one needs a final review before merging. @blimlim @marc-white would either of you mind going over the latest changes & conversation threads? |
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.
I think we're good to go at this point!
Argh, GitHub seems to need someone else to resolve the conversations before it'll let me merge... |
Resolves #92.
This PR covers a few tasks:
um2netcdf
module slightlyKnown gaps:
This work exposes a (possibly one off) case where
iris
funcs return a new cube. Moving the pressure level fixes intoprocess()
requires modifying the list of cubes being processed to patch the new cube in. This is noted in the code. The tests are also moderately loose, related to the complexity with testingiris
components.It's likely addressing this will have to be deferred until the code is restructured & tested, to allow workflow refactoring.
Otherwise, any comments welcome!