-
Notifications
You must be signed in to change notification settings - Fork 880
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
Fix/nan in resample #1350
Fix/nan in resample #1350
Conversation
…el, closed, loffset and base
…the docstring accordingly and added an example
Codecov ReportBase: 93.88% // Head: 93.88% // No change to project coverage 👍
Additional details and impacted files@@ Coverage Diff @@
## master #1350 +/- ##
=======================================
Coverage 93.88% 93.88%
=======================================
Files 78 78
Lines 8508 8508
=======================================
Hits 7988 7988
Misses 520 520
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View 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.
Looks great :) just got a minor suggestion on link formatting.
to start the resampling and avoid nan at the first value of the resampled TimeSeries | ||
(https://docs.xarray.dev/en/stable/generated/xarray.DataArray.resample.html) | ||
|
||
Examples |
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 love this, thanks :)
rephrasing of the docstring using hyperlink Co-authored-by: Julien Herzen <julien@unit8.co>
Fixes #1237.
Summary
Added kwargs to
TimeSeries.resample
to be able to pass arguments to thexarray.resample
method and give the possibility to the user to shift the start of the resampling to avoid gettingnan
at the beginning of the resampledTimeSeries
.Other Information
Write an example in the docstring to cover the most likely usage, it might be too long...