-
Notifications
You must be signed in to change notification settings - Fork 5
feat(resampling): support setting custom dates for the start and end of extrapolation #58
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
feat(resampling): support setting custom dates for the start and end of extrapolation #58
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.
lgtm, tested and working - just one comment about release notes
Let's go ahead here ? |
…tion with hourly (or shorter) time steps
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.
Overall lgtm
Weirdly, opening a resampling recipe now always dirties the save, which didn't seem to be the case before
Also, maybe we should have a quick sentence explaining what we do in _can_customize_resampling_dates
for anyone in a +-13 tz ?
… favoring UTC+13 (NZDT) over UTC-11 (American Samoa), also add a warning about that behavior in the recipe logs
Logged internally as this is common to all plugins with a date input
We now favour UTC+13 and only have unexpected behaviour in UTC-11 (American Samoa). Code is well commented and a warning is added in the logs in that case. |
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.
LGTM! nice work on the timestamp stuff
think we need to merge the changelog but otherwise all clear
Default is still to use the first and last known timestamps:
Custom dates can be set for either:
dss-plugin-timeseries-preparation-2.1.0.zip