QuantConnect / QuantConnect/Lean

Supports Multiple Continous Contracts for a Future

Open
#7,062 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature
Dominant language
C#
Stars
21.7k
Forks
5.3k
Avg merge
2d 22h
Merged PRs (30d)
34

Description

Expected Behavior

Supports multiple continous contracts for a future, e.g. \ES1, \ES2.

Actual Behavior

Lean only support one continous contract per future.

Potential Solution

N/A

Reproducing the Problem

Add two Future objects:

 _continuousContract0 = AddFuture(Futures.Indices.SP500EMini, contractDepthOffset: 0);
 _continuousContract1 = AddFuture(Futures.Indices.SP500EMini, contractDepthOffset: 1);

Observe that the second one is not updated (prices are zero) and Mapped is always null.

Checklist
  • I have completely filled out this template
  • I have confirmed that this issue exists on the current master branch
  • I have confirmed that this is not a duplicate issue by searching issues
  • I have provided detailed steps to reproduce the issue

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the AddFuture calls in the reproduction and trace how two SP500EMini Future objects with contractDepthOffset values 0 and 1 are registered and updated. Reproduce the issue, then verify that both objects receive nonzero prices and that the second object's Mapped value is populated.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
fintech-quant
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.