ExecuteMarginCall can liquidate the same deficit across several groups in one batch

Abierto
  • ¿Algo no está bien?
#10,107 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

priority:P1
Description

DefaultMarginCallModel.ExecuteMarginCall can submit multiple liquidations for the same margin deficit within its first execution batch, even when the first pending order would already cover the whole deficit. This is separate from generating duplicate orders for the same group on later scans (#10008).

GetMarginCallOrders sizes every position group's request from the same current portfolio deficit. ExecuteMarginCall submits a group and calls SecurityTransactionManager.WaitForOrder, but ignores its false return when the wait times out. If the order is still open, holdings and MarginRemaining are unchanged, so execution continues to the next group and submits another order covering the same deficit.

In backtesting, MarketOrderFillTimeout is zero, and market orders on daily subscriptions can remain open until the next bar. Thus multiple distinct groups can all be liquidated for the same deficit during a single margin call, even without any subsequent scans.

Reproduction and observed result

Reproduced locally with a temporary NUnit test in MarginCallModelTests, using the existing portfolio/security helpers and FakeOrderProcessor:

  1. Create two distinct USD equity positions, SPY and AAPL, each holding 100 shares at a current price of $100 and leverage 2. Use zero fees and set cash to -$14,000.
  2. Use DefaultMarginCallModel with its default margin buffer and set portfolio.Transactions.MarketOrderFillTimeout = TimeSpan.Zero.
  3. Verify portfolio value is $6,000, maintenance margin is $10,000, and the deficit is $4,000.
  4. Call GetMarginCallOrders, then call ExecuteMarginCall exactly once, leaving submitted orders open.

Observed:

  • Generation returns one request for each group, each selling 81 shares.
  • A single execution submits both requests, returning two tickets.
  • Each sale releases $4,050 of margin at current prices; combined projected relief is $8,100 against a $4,000 deficit.
  • An assertion expecting only one submitted liquidation fails: Expected: 1, But was: 2.

The reproduction fails identically on master (da4d8e4a4) and on 6dd4b06d1; this is a pre-existing execution/sizing problem, not a regression introduced by the pending-ticket guard.

Tested end to end with daily SPY and minute AAPL as well: AAPL's liquidation can fill while a further SPY liquidation is already being submitted from the same unchanged deficit snapshot.

What a fix must achieve

Avoid committing the entire deficit more than once when multiple position groups are processed in one margin call. Continue to allow additional liquidation when pending orders cannot cover the deficit, preserve combo-order grouping, and handle cancellation/rejection without leaving the portfolio indefinitely under-margined.

One possible approach is to account for pending reductions when deciding whether and how much to liquidate from the next group, rather than assuming a timed-out wait means the first liquidation has completed.

Lenguaje dominante
C#
Estrellas
22.5k
Forks
5.4k
Merge medio
22 h 6 min
PR fusionados (30 d)
81

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de QuantConnect/Lean

Todos los issues de QuantConnect/Lean

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.