You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As described in loader.py, benchmark returns are cut off 2 days before the current trading day. But if users run algorithms with a data source that includes the most recent trading days, it creates an error during the risk calculations at the end of the simulation, because the "extra" day will get nan for the benchmark return.
It's happening this weekend: zipline.data.load_from_yahoo() is returning data through 1/21, but the last benchmark return from loader.load_market_data is 1/20.
The text was updated successfully, but these errors were encountered:
As described in loader.py, benchmark returns are cut off 2 days before the current trading day. But if users run algorithms with a data source that includes the most recent trading days, it creates an error during the risk calculations at the end of the simulation, because the "extra" day will get
nan
for the benchmark return.It's happening this weekend:
zipline.data.load_from_yahoo()
is returning data through 1/21, but the last benchmark return fromloader.load_market_data
is 1/20.The text was updated successfully, but these errors were encountered: