-
Notifications
You must be signed in to change notification settings - Fork 44
Fixed --skip-nonexistent option #1093
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
Conversation
|
@jvegasbsc Would you have time to review this? |
valeriupredoi
left a comment
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.
very nice, thanks a lot @schlunma 🍺
| def concatenate(cubes): | ||
| """Concatenate all cubes after fixing metadata.""" | ||
| if not cubes: | ||
| return cubes |
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.
thank you! I meant to plug this in since January 😆
|
this is good, @jvegasbsc have a look too pls mate but it's good to go by me 👍 |
remi-kazeroni
left a comment
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.
Works fine for me! This PR solves the issues I had with the --skip-nonexistent option. Thanks a lot for your work @schlunma 👍
|
oops I merged 😁 @jvegasbsc holler back if you encounter any issues, mate, but this is working well and I am rather happy to see it in the sooner than later 👍 |
This PR fixes a bug that was introduced in #917 that prevented the usage of the
--skip-nonexistentoption. I also add a tiny test for it.Note that I also adapted the preprocessors
concatenateandsavewhich gave ugly error messages when an empty cube was passed. This should never happen during a regular ESMValTool run, but could happen when these functions are used as part of theesmvalcoreAPI.Closes #1040, closes #988.
Link to documentation:
Before you get started
Checklist
It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.
To help with the number pull requests: