-
Notifications
You must be signed in to change notification settings - Fork 912
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: datetime_attribute account for 0 or 1-indexing of the attributes #2242
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #2242 +/- ##
==========================================
+ Coverage 93.95% 93.97% +0.02%
==========================================
Files 135 135
Lines 13501 13499 -2
==========================================
+ Hits 12685 12686 +1
+ Misses 816 813 -3 ☔ View full report in Codecov by Sentry. |
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 @madtoinou thanks a lot 🚀
Had some minor suggestions. I think we should make the first "step" of each freq start at 0 for cyclic encodings (month=1 should result in sin(0), cos(0), similar to hour=0)
…all the generated encodings
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.
Another great PR, thanks @madtoinou 🚀
Fixes #2219.
Summary
datetime_attribute_timeseries()
was not taking into account the indexing of the attribute (1 for month, day or week for example), resulting in a shift of the "zeroed" columnsOther Information