Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Protective Collar to Option Strategies #8025

Open
wants to merge 17 commits into
base: master
Choose a base branch
from

Conversation

LouisSzeto
Copy link
Collaborator

@LouisSzeto LouisSzeto commented May 15, 2024

Description

Add support Protective Collar, Conversion and Reverse Conversion to abstraction option combo orders in OptionStrategies class.
(source of margin requirement: https://www.interactivebrokers.com.hk/en/trading/margin-options.php)

Margin (might have very slight difference due to non-perfect underlying price -> other strategy minorly involved [<$5]):

  • Protective Collar:
collar
  • Conversion:
collar
  • Reversal:
reversal

Related Issue

closes #6919
closes #8035
closes #8036

Motivation and Context

missing feature

Requires Documentation Change

Amendment to https://www.quantconnect.com/docs/v2/writing-algorithms/trading-and-orders/option-strategies/protective-collar
Add new page for Conversion and Reverse Conversion

How Has This Been Tested?

  • added unit test
  • added regression test

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • Refactor (non-breaking change which improves implementation)
  • Performance (non-breaking change which improves performance. Please add associated performance test and results)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Non-functional change (xml comments/documentation/etc)

Checklist:

  • My code follows the code style of this project.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.
  • My branch follows the naming convention bug-<issue#>-<description> or feature-<issue#>-<description>

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant