[Optimizer] allow multi exchange backtests and handle settings fallbacks #2246
+128
−60
Conversation
This file contains 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
This was referenced Feb 24, 2023
techfreaque
force-pushed
the
multi_exchange
branch
2 times, most recently
from
cd524a0
to
6fcf58d
Compare
techfreaque
force-pushed
the
multi_exchange
branch
from
6fcf58d
to
ac3e774
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
if the api receives a list of "exchange_ids" and/or a list of "data_files" it will optimize on multi exchanges.
Should behave the same way as before if "data_files" is a string and not a list and if no "exchange_ids" list is provided
requires:
Drakkar-Software/OctoBot-Trading#847
Drakkar-Software/OctoBot-Backtesting#172
Drakkar-Software/OctoBot-Tentacles#865