CTYPTO/freqtrade
1
0
Fork 0
mirror of https://github.com/freqtrade/freqtrade.git synced 2025-12-03 10:33:08 +00:00
Code Issues Packages Projects Releases Wiki Activity

Deployed d064bd4 to develop in en with MkDocs 1.6.1 and mike 2.1.3

Browse Source
This commit is contained in:
github-actions[bot]
2025-08-14 13:21:18 +00:00
parent af8b76538f
commit 7b78d25d9a
6 changed files with 30 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
en/develop/advanced-backtesting/index.html
View File

@@ -1880,7 +1880,7 @@ back to a previous backtest output, you need to supply the <code>--export-filena
You can supply the same parameter to <code>backtest-analysis</code> with the name of the final backtest
output file. This allows you to keep historical versions of backtest results and re-analyse
them at a later date:</p>
<div class="highlight"><pre><span></span><code>freqtrade<span class="w"> </span>backtesting<span class="w"> </span>-c<span class="w"> </span>&lt;config.json&gt;<span class="w"> </span>--timeframe<span class="w"> </span>&lt;tf&gt;<span class="w"> </span>--strategy<span class="w"> </span>&lt;strategy_name&gt;<span class="w"> </span>--timerange<span class="o">=</span>&lt;timerange&gt;<span class="w"> </span>--export<span class="o">=</span>signals<span class="w"> </span>--export-filename<span class="o">=</span>/tmp/mystrat_backtest.json
<div class="highlight"><pre><span></span><code>freqtrade<span class="w"> </span>backtesting-analysis<span class="w"> </span>-c<span class="w"> </span>&lt;config.json&gt;<span class="w"> </span>--timeframe<span class="w"> </span>&lt;tf&gt;<span class="w"> </span>--strategy<span class="w"> </span>&lt;strategy_name&gt;<span class="w"> </span>--timerange<span class="o">=</span>&lt;timerange&gt;<span class="w"> </span>--export<span class="o">=</span>signals<span class="w"> </span>--export-filename<span class="o">=</span>user_data/backtest-results/backtest-result-2025-03-05_20-38-34.zip
</code></pre></div>
<p>You should see some output similar to below in the logs with the name of the timestamped
filename that was exported:</p>

14
en/develop/backtesting/index.html
View File

@@ -2079,7 +2079,7 @@ To learn how to get data for the pairs and exchange you're interested in, head o
[--timeframe-detail TIMEFRAME_DETAIL]
[--strategy-list STRATEGY_LIST [STRATEGY_LIST ...]]
[--export {none,trades,signals}]
[--export-filename PATH]
[--backtest-filename PATH]
[--breakdown {day,week,month,year} [{day,week,month,year} ...]]
[--cache {none,day,week,month}]
[--freqai-backtest-live-models] [--notes TEXT]
@@ -2126,10 +2126,9 @@ options:
becomes `backtest-data-SampleStrategy.json`
--export {none,trades,signals}
Export backtest results (default: trades).
--export-filename PATH, --backtest-filename PATH
Use this filename for backtest results.Requires
`--export` to be set as well. Example: `--export-filen
ame=user_data/backtest_results/backtest_today.json`
--backtest-filename PATH, --export-filename PATH
Use this filename for backtest results.Example:
`--backtest-filename=user_data/backtest_results/`
--breakdown {day,week,month,year} [{day,week,month,year} ...]
Show backtesting breakdown per [day, week, month,
year].
@@ -2229,9 +2228,10 @@ You can then use this data for backtesting as follows:</p>
</code></pre></div>
<p>Only use this if you're sure you'll not want to plot or analyze your results further.</p>
<hr />
<p>Exporting trades to file specifying a custom filename</p>
<div class="highlight"><pre><span></span><code>freqtrade<span class="w"> </span>backtesting<span class="w"> </span>--strategy<span class="w"> </span>backtesting<span class="w"> </span>--export<span class="w"> </span>trades<span class="w"> </span>--export-filename<span class="o">=</span>backtest_samplestrategy.json
<p>Exporting trades to file specifying a custom directory</p>
<div class="highlight"><pre><span></span><code>freqtrade<span class="w"> </span>backtesting<span class="w"> </span>--strategy<span class="w"> </span>backtesting<span class="w"> </span>--export<span class="w"> </span>trades<span class="w"> </span>--export-filename<span class="o">=</span>user_data/custom-backtest-results
</code></pre></div>
<hr />
<p>Please also read about the <a href="../strategy-customization/#strategy-startup-period">strategy startup period</a>.</p>
<hr />
<p>Supplying custom fee value</p>

9
en/develop/lookahead-analysis/index.html
View File

@@ -1827,7 +1827,7 @@ This is done by not looking at the strategy code itself, but at changed indicato
[--timeframe-detail TIMEFRAME_DETAIL]
[--strategy-list STRATEGY_LIST [STRATEGY_LIST ...]]
[--export {none,trades,signals}]
[--export-filename PATH]
[--backtest-filename PATH]
[--freqai-backtest-live-models]
[--minimum-trade-amount INT]
[--targeted-trade-amount INT]
@@ -1872,10 +1872,9 @@ options:
becomes `backtest-data-SampleStrategy.json`
--export {none,trades,signals}
Export backtest results (default: trades).
--export-filename PATH, --backtest-filename PATH
Use this filename for backtest results.Requires
`--export` to be set as well. Example: `--export-filen
ame=user_data/backtest_results/backtest_today.json`
--backtest-filename PATH, --export-filename PATH
Use this filename for backtest results.Example:
`--backtest-filename=user_data/backtest_results/`
--freqai-backtest-live-models
Run backtest with ready models.
--minimum-trade-amount INT

18
en/develop/plotting/index.html
View File

@@ -1815,7 +1815,7 @@ This is mostly for the performance problems even medium sized plots can cause, b
[--plot-limit INT] [--db-url PATH]
[--trade-source {DB,file}]
[--export {none,trades,signals}]
[--export-filename PATH]
[--backtest-filename PATH]
[--timerange TIMERANGE] [-i TIMEFRAME]
[--no-trades]
@@ -1843,10 +1843,9 @@ options:
(backtest file)) Default: file
--export {none,trades,signals}
Export backtest results (default: trades).
--export-filename PATH, --backtest-filename PATH
Use this filename for backtest results.Requires
`--export` to be set as well. Example: `--export-filen
ame=user_data/backtest_results/backtest_today.json`
--backtest-filename PATH, --export-filename PATH
Use this filename for backtest results.Example:
`--backtest-filename=user_data/backtest_results/`
--timerange TIMERANGE
Specify what timerange of data to use.
-i TIMEFRAME, --timeframe TIMEFRAME
@@ -2063,7 +2062,7 @@ This graph will also highlight the start (and end) of the Max drawdown period.</
[--freqaimodel NAME] [--freqaimodel-path PATH]
[-p PAIRS [PAIRS ...]] [--timerange TIMERANGE]
[--export {none,trades,signals}]
[--export-filename PATH] [--db-url PATH]
[--backtest-filename PATH] [--db-url PATH]
[--trade-source {DB,file}] [-i TIMEFRAME]
[--auto-open]
@@ -2076,10 +2075,9 @@ options:
Specify what timerange of data to use.
--export {none,trades,signals}
Export backtest results (default: trades).
--export-filename PATH, --backtest-filename PATH
Use this filename for backtest results.Requires
`--export` to be set as well. Example: `--export-filen
ame=user_data/backtest_results/backtest_today.json`
--backtest-filename PATH, --export-filename PATH
Use this filename for backtest results.Example:
`--backtest-filename=user_data/backtest_results/`
--db-url PATH Override trades database URL, this is useful in custom
deployments (default: `sqlite:///tradesv3.sqlite` for
Live Run mode, `sqlite:///tradesv3.dryrun.sqlite` for

2
en/develop/search/search_index.json
View File

File diff suppressed because one or more lines are too long

19
en/develop/utils/index.html
View File

@@ -2779,15 +2779,15 @@ Adding <code>--show-pair-list</code> outputs a sorted pair list you can easily c
</details>
<div class="highlight"><pre><span></span><code>usage: freqtrade backtesting-show [-h] [-v] [--no-color] [--logfile FILE] [-V]
[-c PATH] [-d PATH] [--userdir PATH]
[--export-filename PATH] [--show-pair-list]
[--backtest-filename PATH]
[--show-pair-list]
[--breakdown {day,week,month,year} [{day,week,month,year} ...]]
options:
-h, --help show this help message and exit
--export-filename PATH, --backtest-filename PATH
Use this filename for backtest results.Requires
`--export` to be set as well. Example: `--export-filen
ame=user_data/backtest_results/backtest_today.json`
--backtest-filename PATH, --export-filename PATH
Use this filename for backtest results.Example:
`--backtest-filename=user_data/backtest_results/`
--show-pair-list Show backtesting pairlist sorted by profit.
--breakdown {day,week,month,year} [{day,week,month,year} ...]
Show backtesting breakdown per [day, week, month,
@@ -2820,7 +2820,7 @@ Common arguments:
<div class="highlight"><pre><span></span><code>usage: freqtrade backtesting-analysis [-h] [-v] [--no-color] [--logfile FILE]
[-V] [-c PATH] [-d PATH]
[--userdir PATH]
[--export-filename PATH]
[--backtest-filename PATH]
[--analysis-groups {0,1,2,3,4,5} [{0,1,2,3,4,5} ...]]
[--enter-reason-list ENTER_REASON_LIST [ENTER_REASON_LIST ...]]
[--exit-reason-list EXIT_REASON_LIST [EXIT_REASON_LIST ...]]
@@ -2832,10 +2832,9 @@ Common arguments:
options:
-h, --help show this help message and exit
--export-filename PATH, --backtest-filename PATH
Use this filename for backtest results.Requires
`--export` to be set as well. Example: `--export-filen
ame=user_data/backtest_results/backtest_today.json`
--backtest-filename PATH, --export-filename PATH
Use this filename for backtest results.Example:
`--backtest-filename=user_data/backtest_results/`
--analysis-groups {0,1,2,3,4,5} [{0,1,2,3,4,5} ...]
grouping output - 0: simple wins/losses by enter tag,
1: by enter_tag, 2: by enter_tag and exit_tag, 3: by