-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
Issues with running algorithms through latest close #2024
Comments
Hey @ChrisPappalardo thanks for opening this. Hmm...looks like this is a benchmark issue where we have missing data from the API endpoint we're hitting |
I thought that too. I verified that the SPY_benchmark.csv file in the container had data through 11/24. I noticed that the treasury_curves.csv file did not (latest was 11/21). I manually added rows for 11/22 and 11/24 to that file but I still get the same KeyError after re-running. |
Unless you have cached benchmark data here zipline/zipline/data/loader.py Line 213 in 5421ec0
when you try to load the benchmark data from the google API zipline/zipline/data/benchmarks.py Line 46 in cabe0b6
you get an error because it has been offline since Oct 1 pydata/pandas-datareader@08a700e |
Actually, the API still works, it's just that the URL has changed. I've managed to make the |
@alexukf Thanks for the reply. Your fix seems to work for the API issue, but doesn't fix the latest close issue. I believe it's due to the Fed H15 report being lagged a day (see here). |
Closing this as this should be fixed in the latest release of zipline. Feel free to update to 1.2.0 with either:
or
If you're still experiencing issues, please reopen this or open a new issue 🙂 |
The issue is still there as of Dec 2019. Cannot exactly recall. But someone metioned on a Google group that IEX no longer provides data for free, need to sign up with a cloud account. Is this the reason why this is failing again now? |
Two more issues for you guys:
Again, I'm doing all of this inside docker containers which I build and run with:
You can reproduce the issues as follows:
Where
test.py
is a do-nothing simple algorithm:When I run that code inside a zipline container I get:
The traceback in the first exception doesn't give any clues as to where this is happening in the algorithm or int the zipline code:
Am I missing something?
The text was updated successfully, but these errors were encountered: