implemented a parameter for skipping errors during model training in the backtest process #10098
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.
Summary
In case of any data disruptions related to a coin, currently, a hard exception occurs, interrupting the backtesting and limiting the completion of backtesting for the FreqAI strategy with other coins. To bypass this, it was suggested to use an exception skipping parameter as a warning, during which the exception is ignored during backtesting, allowing the backtesting to continue. In a separate case (with another parameter), resolving this issue may involve additional data preprocessing, which is not included in this feature's development.
Solve the issue: #9671
Quick changelog
warn_exceptions_on_backtest_only
toconfig_examples/config_freqai.example.json
inconfig.freqai
freqtrade/freqai/freqai_interface.py
What's new?
We added an exception skipping parameter to handle data disruptions during backtesting, letting the FreqAI strategy proceed across coins even when exceptions occur, and there's potential for further data preprocessing to tackle such issues later on.