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/RegressionEnsemble.extreme_lags when models use only covariates lags #1942
Conversation
Codecov ReportPatch coverage:
❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more. Additional details and impacted files@@ Coverage Diff @@
## master #1942 +/- ##
==========================================
- Coverage 93.87% 93.87% -0.01%
==========================================
Files 132 132
Lines 12675 12663 -12
==========================================
- Hits 11899 11887 -12
Misses 776 776
☔ 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.
Thanks for this @madtoinou. I added the two comments we discussed.
Let me know when I can re-review.
…also when none of the forecasting models use target lags
…/darts into fix/reg_ens_extreme_lags
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 @madtoinou 🥳
Fixes #1867.
Summary
When forecasting models don't use target lags,
RegressionEnsembleModel.extreme_lags
directly returnsEnsembleModel.extreme_lags
instead of subtractingregression_train_n_points
tomin_target_lags
(which isNone
).