Python icon indicating copy to clipboard operation
Python copied to clipboard

[PYTEST WARNING] Machine learning forecasting

Open CaedenPH opened this issue 3 years ago • 3 comments

Feature description

@nandiya Please could you resolve this warning

machine_learning/forecasting/run.py::machine_learning.forecasting.run.sarimax_predictor
  /opt/hostedtoolcache/Python/3.10.7/x64/lib/python3.10/site-packages/statsmodels/tsa/statespace/sarimax.py:866: UserWarning: Too few observations to estimate starting parameters for ARMA and trend. All parameters except for variances will be set to zeros.
    warn('Too few observations to estimate starting parameters%s.'

machine_learning/forecasting/run.py::machine_learning.forecasting.run.sarimax_predictor
  /opt/hostedtoolcache/Python/3.10.7/x64/lib/python3.10/site-packages/statsmodels/tsa/statespace/sarimax.py:866: UserWarning: Too few observations to estimate starting parameters for seasonal ARMA. All parameters except for variances will be set to zeros.
    warn('Too few observations to estimate starting parameters%s.'

machine_learning/forecasting/run.py::machine_learning.forecasting.run.sarimax_predictor
  /opt/hostedtoolcache/Python/3.10.7/x64/lib/python3.10/site-packages/numpy/core/fromnumeric.py:3715: RuntimeWarning: Degrees of freedom <= 0 for slice
    return _methods._var(a, axis=axis, dtype=dtype, out=out, ddof=ddof,

machine_learning/forecasting/run.py::machine_learning.forecasting.run.sarimax_predictor
  /opt/hostedtoolcache/Python/3.10.7/x64/lib/python3.10/site-packages/numpy/core/_methods.py:223: RuntimeWarning: invalid value encountered in divide
    arrmean = um.true_divide(arrmean, div, out=arrmean, casting='unsafe',

machine_learning/forecasting/run.py::machine_learning.forecasting.run.sarimax_predictor
  /opt/hostedtoolcache/Python/3.10.7/x64/lib/python3.10/site-packages/numpy/core/_methods.py:257: RuntimeWarning: invalid value encountered in double_scalars
    ret = ret.dtype.type(ret / rcount)

origin: #7211

CaedenPH avatar Oct 16 '22 10:10 CaedenPH

@cclauss I think this issue should be reopened since the pytest warnings were never resolved

tianyizheng02 avatar Jan 02 '23 07:01 tianyizheng02

My sense is that these warnings were solved but new ones have come up.

cclauss avatar Jan 02 '23 08:01 cclauss

In the pytest logs from the most recent build here, it appears that the 5 warnings cited above are still present

tianyizheng02 avatar Jan 02 '23 10:01 tianyizheng02