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

Delisting Event / Data Events #56

Closed
jaredbroad opened this issue Mar 13, 2015 · 2 comments
Closed

Delisting Event / Data Events #56

jaredbroad opened this issue Mar 13, 2015 · 2 comments
Labels

Comments

@jaredbroad
Copy link
Member

Create an "OnDelisting" event in the QCAlgorithm class which is called when a symbol is to be delisted.

This should be triggered in the Algorithm Manager(?) from a feed.DataEvents queue which has generic status events on the data. The data event will include the subscription-id, symbol and relevant event types.

Before the OnData event, the DataEvents queue would be cleared (synchronously processed) and passed into the algorithm event handlers.

This same mechanism could later be used for circuit breakers, and unexpected market closes.

For now this would only be supported in backtesting using the map_files. If the map files final date is today, pass through the delisting data event. For live trading we would need to organize a data source.

@bizcad
Copy link
Contributor

bizcad commented Apr 7, 2015

I was just thinking about this problem. It should be fired when the data feed breaks as well so that the algo could issue an OnLiquidate() and perhaps a quit, if the algo goes blind.

@jaredbroad
Copy link
Member Author

Completed in #e1938ba

gsalaz98-testdeploy added a commit to gsalaz98-testdeploy/Lean that referenced this issue Sep 11, 2020
…nerated-stubs

[Travis QuantConnect#56] Autogenerated Python Stubs
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants