Add naked single-option strategies #7231
Merged
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.
Description
Add naked call and put single-option strategies in order to allow matching naked positions in the
OptionStrategyPositionGroupResolver
. This allows doing things like placing orders for an option strategy that would liquidate existing positions with only one leg ramianing. Previous to this change, a single leg option strategy was never matched and the orders could not be placed.For instance, take the situation where you want to roll out a front month contract for a back month one using a strategy (see the new
RollOutFrontMonthToBackMonthOptionUsingCalendarSpreadRegressionAlgorithm
algorithm):In this situation, after resolving the positions, the
OptionStrategyPositionGroupResolver
tries to match the resolved strategy (a single leg) with the existing definitions, which is why we needed the single-leg strategies.Note: this should be merged after rebasing #7230. That bug fix would revert the stats change in
OptionShortCallMarginCallEventsAlgorithm
.Related Issue
Closes #7184
Motivation and Context
Requires Documentation Change
How Has This Been Tested?
Unit tests.
Types of changes
Checklist:
bug-<issue#>-<description>
orfeature-<issue#>-<description>