-
Notifications
You must be signed in to change notification settings - Fork 487
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
[bugfix] enable events while predicting into known future #1029
Conversation
resolves the issue of having NaN values in the events df, which led to problems
Codecov Report
@@ Coverage Diff @@
## main #1029 +/- ##
=======================================
Coverage 90.26% 90.26%
=======================================
Files 21 21
Lines 4737 4737
=======================================
Hits 4276 4276
Misses 461 461
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. |
Model Benchmark
|
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.
Great catch @judussoari
We should remove the option to not pass those variables (meaning remove the default None
values here to avoid such mistakes in the future).
added events config to _maybe_extend_df()
resolves the issue of having NaN values in the events df, which led to an Error. Instead, the extended version of events_df is filled with zeros now, just like in
make_future_dataframe()
Fixes #1027