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
This pull request is all my own work -- I have not plagiarized.
I know that pull requests will not be merged if they fail the automated tests.
This PR only changes one algorithm file. To ease review, please open separate PRs for separate algorithms.
All new Python files are placed inside an existing directory.
All filenames are in all lowercase characters with no spaces or dashes.
All functions and variable names follow Python naming conventions.
All function parameters and return values are annotated with Python type hints.
All functions have doctests that pass the automated testing.
All new algorithms include at least one URL that points to Wikipedia or another similar explanation.
If this pull request resolves one or more open issues then the description above includes the issue number(s) with a closing keyword: "Fixes #ISSUE-NUMBER".
Your PR doesn't actually fix #7305 because the Pytest warnings are still present in the build logs:
machine_learning/forecasting/run.py::machine_learning.forecasting.run.sarimax_predictor
/opt/hostedtoolcache/Python/3.11.4/x64/lib/python3.11/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.11.4/x64/lib/python3.11/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.11.4/x64/lib/python3.11/site-packages/numpy/core/fromnumeric.py:3747: 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.11.4/x64/lib/python3.11/site-packages/numpy/core/_methods.py:226: RuntimeWarning: invalid value encountered in divide
arrmean = um.true_divide(arrmean, div, out=arrmean,
machine_learning/forecasting/run.py::machine_learning.forecasting.run.sarimax_predictor
/opt/hostedtoolcache/Python/3.11.4/x64/lib/python3.11/site-packages/numpy/core/_methods.py:261: RuntimeWarning: invalid value encountered in scalar divide
ret = ret.dtype.type(ret / rcount)
However, your changes are still good, so we can merge this PR anyway after some minor tweaks
Sure, I'll update the code formatting.
Regarding the Pytest Warnings, I looked into the source of the error and it might be due to ARIMA deprecation.
Two approaches from mine would be to either transform the data passed to SARIMAX model for estimation or supress the warnings should be well enough.
Sure, I'll update the code formatting. Regarding the Pytest Warnings, I looked into the source of the error and it might be due to ARIMA deprecation. Two approaches from mine would be to either transform the data passed to SARIMAX model for estimation or supress the warnings should be well enough.
@p1utoze At first glance, it looks to me like some of the errors are caused by the small number of observations (which makes sense, the ARIMA models probably need way more observations to work well). Maybe reworking this file to use a different CSV file (one with much more data) might fix some if not all of the warnings.
Hey! I finally fixed the warnings. The numpy Runtime warning was due to the 0 in seasonal_order tuple and regarding the ARIMA models. Yes you are right, it needs more observations to work well and the User Warning are raised because of the sample test >>> sarimax_predictor([4,2,6,8], [3,1,2,4], [2]) used by doctests. Supressing it should be fine enough. Shall I create another PR then?
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…tion
Describe your change:
Fixes [#7305]
I have modified the run.py and it runs without any errors locally.
read_csvas it caused errors in Normalization.data_safety_checkerfunction.Checklist: