Fix MultiBacktest mixed no-trade results#1366
Open
elpolini wants to merge 1 commit into
Open
Conversation
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
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.
Summary
Fixes #1344.
MultiBacktest._mp_task_run()currently returnsNonefor datasets whose strategy produced zero trades. When aMultiBacktestrun mixes datasets with trades and datasets with no trades,MultiBacktest.run()then receives a mixed list ofpd.SeriesandNone, which can either raiseTypeError: object of type 'NoneType' has no len()or produce nested/odd DataFrame values depending on ordering.Backtest.run()already returns a complete stats series for zero-trade strategies, so this change keeps those stats instead of replacing them withNone.Changes
_mp_task_run(), including zero-trade stats.# Trades == 0and do not produce nested Series values.Test plan