fix: go for forecast method instead of predict in ets

aimclub / FEDOT

Automated modeling and machine learning framework FEDOT

https://fedot.readthedocs.io

BSD 3-Clause "New" or "Revised" License

619 stars 84 forks source link

fix: go for forecast method instead of predict in ets #1299

Closed Lopa10ko closed 2 weeks ago

Lopa10ko commented 3 weeks ago

This is a 🐛 bug fix. Related to api_ts_forecasting_example integration test failure.

[x] Change predict logic by calling forecasting method instead of a predict one in ExpSmoothingImplementation (27315b2)
[x] Make sure that this resolves the issue with that kind of pipelines by running saved troubled pipelines locally
[x] Remove obsolete custom message logging level (da4fc93)

related to #1297, but not closing it since there are various types of troubled pipelines closes #1300

docu-mentor[bot] commented 3 weeks ago

👋 Hi, I'm @docu-mentor, an LLM-powered GitHub app powered by Anyscale Endpoints that gives you actionable feedback on your writing.

Simply create a new comment in this PR that says:

@docu-mentor run

and I will start my analysis. I only look at what you changed in this PR. If you only want me to look at specific files or folders, you can specify them like this:

@docu-mentor run doc/ README.md

In this example, I'll have a look at all files contained in the "doc/" folder and the file "README.md". All good? Let's get started!

Lopa10ko commented 3 weeks ago

ap_ts_forecasting_example_predict_vs_forecast

github-actions[bot] commented 3 weeks ago

All PEP8 errors has been fixed, thanks :heart:

Comment last updated at

Lopa10ko commented 2 weeks ago

На проблему с ets хорошо бы тест добавить. Хотя бы для какого-то конкретного пайлпайна.

e43412e