Back to catalog / Crypto quant workflows
Break down backtest results by exit reason
Inspect historical behavior separately for ROI, stoploss, and custom exit tags.
Goal
Goal: Inspect historical behavior separately for ROI, stoploss, and custom exit tags.
Steps
- Run a fixed backtest with
--export signals. [analysis] - Group results with
freqtrade backtesting-analysis --analysis-groups 0 1 2 3 4 5. [analysis] - Compare trade count, net P&L, and exit tags per group; flag small samples. [analysis]
How to verify
Grouped summaries reconcile to total trades and individual records.
Troubleshooting
If fields are missing, check export options and result path.
Permissions
Prerequisites
- Python 3.11+, Freqtrade installed, a pinned strategy, and a local user-data directory.
Permissions
- Use public market data and local history; treat every trading decision as research and never connect a live account.
Limitations
Historical exit categories do not predict future signal performance.
Pinned upstream source
- Repository
- freqtrade/freqtrade
- File path
- docs/advanced-backtesting.md
- Pinned commit
82e4c9604c51523f7e05c5a297167cf2b13a2129- Source checked
- 2026-10-14 · Reviewed against the pinned upstream source
Repository metrics
These values describe the upstream repository, not popularity or likes for an individual skill or playbook.
- Stars
- Not collected
- Forks
- Not collected
- Observed at
- Not collected
No metrics snapshot is available yet.
License: GPLv3
Main topic
Build a reproducible crypto research workflow