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

data / ib - fetch futures data #17

Merged
merged 15 commits into from
Jul 29, 2020
Merged

data / ib - fetch futures data #17

merged 15 commits into from
Jul 29, 2020

Conversation

westonplatter
Copy link
Owner

@westonplatter westonplatter commented Jul 28, 2020

Currently, the IB data fetcher class only pulls in stock data.

Let's add another method (keeping it somewhat uniform so we have a solid data fetcher interface for other data feeds) for futures data.

A couple things to keep in mind,

  • the calendar that calculates RTH will be different since we'll fetching data from a different exchange

  • not all US futures have the same RTH. Eg, /MES and /ZC and /M6E have different market hours. If possible, let's have the rth field account for this. This is not possible based on the current support from trading_calendars, see CME calendar - products have different open/close ranges quantopian/trading_calendars#139.

  • Is there any easy way to test this?

@westonplatter westonplatter merged commit 602fde5 into dev Jul 29, 2020
@westonplatter westonplatter deleted the issue-17/data-ib-futures branch July 29, 2020 07:21
@rsheftel
Copy link

I ran accros this randomly and just wanted to let you know that a fork I made of the great Quantopian prject has support for different market hours for futures: https://github.com/rsheftel/pandas_market_calendars

@westonplatter
Copy link
Owner Author

@rsheftel score. I was thinking I couldn't be the only one who might need something like https://pandas-market-calendars.readthedocs.io/en/latest/calendars.html. Thanks!

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

Successfully merging this pull request may close these issues.

2 participants