-
Notifications
You must be signed in to change notification settings - Fork 4
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
Allowing time_utils.select_time_period
to work on arrays containing NaNs
#12
Allowing time_utils.select_time_period
to work on arrays containing NaNs
#12
Conversation
Codecov Report
@@ Coverage Diff @@
## master #12 +/- ##
==========================================
+ Coverage 16.52% 18.23% +1.70%
==========================================
Files 11 15 +4
Lines 599 894 +295
==========================================
+ Hits 99 163 +64
- Misses 500 731 +231
Continue to review full report at Codecov.
|
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.
Thanks for adding this functionality, @dougiesquire.
Before merging we just need to decide on a few general principles that apply to many/all functions we write:
- Google or Numpy style docstrings?
- Assumed dimension names or keyword argument defaults?
- Dual xarray Dataset/DataArray functionality (and thus whether to use
ds
orda
as a generic variable name)
Thanks for the review Damien. I've implemented what we discussed in person:
I'll go ahead and merge if you have no issues |
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.
Thanks, @dougiesquire. This looks great.
This PR extends
time_utils.select_time_period
to work on arrays containing NaNs.Note this builds off the branch requested for merge in #9, so best to merge that first
Closes #11