Zipline's one key feature is the ability to store the backtest result.
Later, the result could be feed into pyfolio for analysis.
Currently zipline-live does not provide such capability due to it's execution model:
start at BOD, exit at EOD. Due to the daily start the perf tracker object always tracks one
day.
To address this shortcoming the perf_tracker object needs to be persisted and updated
at every start.
Zipline's one key feature is the ability to store the backtest result. Later, the result could be feed into pyfolio for analysis.
Currently zipline-live does not provide such capability due to it's execution model: start at BOD, exit at EOD. Due to the daily start the perf tracker object always tracks one day.
To address this shortcoming the perf_tracker object needs to be persisted and updated at every start.