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
Compatibility issue with statsmodels 0.18.0 #897
Comments
you mean 0.13.0, right? The update on Friday that also broke We just verified that indeed reverting to 0.12.1 seems to resolve the issue (temporarily). The fix in |
For your information, this has been changed too: Maybe something like this:
|
Should just make sure |
Hi ! Are there any updates? |
i see this bug today. Though I turn statemodel to 0.12.1, but does't work? Help,pls. |
On 0.11 everything works fine. |
I am really looking forward to this update ! Are there any changes happened? |
@SirJohnFranklin, thanks for the short demo of the new interface. |
Remove unnecessary pin on statsmodels following tsfresh new release including this fix: blue-yonder/tsfresh#897 http://b/215027867
* Upgrade base image to m88. Remove unnecessary pin on statsmodels following tsfresh new release including this fix: blue-yonder/tsfresh#897 http://b/215027867 * pin setuptools to 59.5.0 in torch build
The problem:
Since v0.18.0, statsmodels stops supporting
unbiased
and usesadjusted
(statsmodels/statsmodels@3d6c388#diff-771ed9ae3d316dec0997427f2182d015dbfdaf6935335428bbf177ce1968bc72), and use ofstatsmodels.tsa.stattools.acf
intsfresh.feature_extraction.ceature_calculators
now causesTypeError
. We need to useadjusted
instead ofunbiased
in calls foracf
in statsmodels later than v0.14.0.The text was updated successfully, but these errors were encountered: