You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I read that after 2.0 exog was being replaced with X as argument call when fitting, updating, or predicting. But because of **fit_args these functions still take exog as argument without having an impact then.
This can be very confusing or a dangerous source of mistakes for users who updated a pre 2.0 version to 2.0 and upwards because it produces wrong or unexpected predictions.
To Reproduce
General behavior, independent of specific configurations or code.
Describe the bug
I read that after 2.0
exog
was being replaced withX
as argument call when fitting, updating, or predicting. But because of**fit_args
these functions still takeexog
as argument without having an impact then.This can be very confusing or a dangerous source of mistakes for users who updated a pre 2.0 version to 2.0 and upwards because it produces wrong or unexpected predictions.
To Reproduce
General behavior, independent of specific configurations or code.
Versions
Expected Behavior
It should throw an error when still using
exog
.Actual Behavior
Is processes exogenous data passed to these functions as
exog
but these exogenous data have no impact on the model.Additional Context
No response
The text was updated successfully, but these errors were encountered: