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
Copy file name to clipboardexpand all lines: docs/backtesting.md
+14
Original file line number
Diff line number
Diff line change
@@ -435,6 +435,20 @@ To save time, by default backtest will reuse a cached result from within the las
435
435
To further analyze your backtest results, freqtrade will export the trades to file by default.
436
436
You can then load the trades to perform further analysis as shown in the [data analysis](strategy_analysis_example.md#load-backtest-results-to-pandas-dataframe) backtesting section.
437
437
438
+
### Backtest output file
439
+
440
+
The output file freqtrade produces is a zip file containing the following files:
441
+
442
+
- The backtest report in json format
443
+
- the market change data in feather format
444
+
- a copy of the strategy file
445
+
- a copy of the strategy parameters (if a parameter file was used)
446
+
- a sanitized copy of the config file
447
+
448
+
This will ensure results are reproducible - under the assumption that the same data is available.
449
+
450
+
Only the strategy file and the config file are included in the zip file, eventual dependencies are not included.
451
+
438
452
## Assumptions made by backtesting
439
453
440
454
Since backtesting lacks some detailed information about what happens within a candle, it needs to take a few assumptions:
0 commit comments