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
Trying to run fcst.make_future_dataframe and getting valuerror. ValueError: starts must be integers or timestamps, got '<class 'pandas._libs.tslibs.timestamps.Timestamp'>'.
I discovered this while trying to run fcst.predict and getting the same error there.
I can't share the train code, but the ds field is a datetime64[ns, US/Eastern], whereas in the tutorials I see that it's just `datetime64[ns]'.
Could that be the issue?
Btw, I tried to go to the Slack to ask this question (to avoid opening issue), but not able to login with my Google account.
Issue Severity
Medium: It is a significant difficulty but I can work around it.
The text was updated successfully, but these errors were encountered:
Hey @matsuobasho, thanks for raising this. This should be fixed by Nixtla/utilsforecast#84, which is part of the 0.1.10 release, can you try upgrading to that version (pip install -U utilsforecast)?
Thanks for the response @jmoralez . That worked! Is this a recent change? If not, might want to update which version of utilsforecast is installed, since I had just run pip install mlforecast to install about a month ago.
What happened + What you expected to happen
Trying to run
fcst.make_future_dataframe
and getting valuerror.ValueError:
startsmust be integers or timestamps, got '<class 'pandas._libs.tslibs.timestamps.Timestamp'>'.
Versions / Dependencies
pandas 2.2.2
mlforecast 0.12.1
Reproduction script
I discovered this while trying to run
fcst.predict
and getting the same error there.I can't share the
train
code, but theds
field is adatetime64[ns, US/Eastern]
, whereas in the tutorials I see that it's just `datetime64[ns]'.Could that be the issue?
Btw, I tried to go to the Slack to ask this question (to avoid opening issue), but not able to login with my Google account.
Issue Severity
Medium: It is a significant difficulty but I can work around it.
The text was updated successfully, but these errors were encountered: