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
hmm, it looks like this date was just chosen based on the data we commonly work with. Currently there is some work that modifies the trading calendar; however, it is not yet completed. This work is a more long term solution as it would allow the user to specify their start date. You can track this progress here: #556. As a temporary workaround, I think you might be able to patch out the start date from the module. For example:
fromzipline.utilsimporttradingcalendartradingcalendar.start=pd.Timestamp('1980-01-01') # set a new start date.
note: This is not supported behavior but it might solve the immediate problem that you have. This will likely break in future versions of zipline.
Another problem with this is that we do not mark all holidays before 1990, so the simulation might be incorrect.
get the following if i input data which is all prior than 1990
AssertionError: Period end falls before the first known trading day.
i did some narrow down and see it is hardcode
start = pd.Timestamp('1990-01-01', tz='UTC') in tradingcalendar
is there anyway I can see backtesting result prior to 1990? is there any workaround for the release 0.7
The text was updated successfully, but these errors were encountered: