From b805e4e1501e9a52b22768b749cd59e918ab1ba5 Mon Sep 17 00:00:00 2001 From: Matthias Date: Sun, 20 Oct 2019 10:34:04 +0200 Subject: [PATCH] Try list extension --- docs/backtesting.md | 5 +++-- mkdocs.yml | 1 + 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/backtesting.md b/docs/backtesting.md index 7bfc2dab5..6db573224 100644 --- a/docs/backtesting.md +++ b/docs/backtesting.md @@ -199,8 +199,9 @@ Since backtesting lacks some detailed information about what happens within a ca - Low happens before high for stoploss, protecting capital first. - ROI sells are compared to high - but the ROI value is used (e.g. ROI = 2%, high=5% - so the sell will be at 2%) - Stoploss sells happen exactly at stoploss price, even if low was lower -- Trailing stoploss: High happens first - adjusting stoploss -- Trailing stoploss: Low uses the adjusted stoploss (so sells with large high-low difference are backtested correctly) +- Trailing stoploss + - High happens first - adjusting stoploss + - Low uses the adjusted stoploss (so sells with large high-low difference are backtested correctly) - Sell-reason does not explain if a trade was positive or negative, just what triggered the sell (this can look odd if negative ROI values are used) Taking these assumptions, backtesting tries to mirror real trading as closely as possible. However, backtesting will **never** replace running a strategy in dry-run mode. diff --git a/mkdocs.yml b/mkdocs.yml index 197df7dc8..863731873 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -52,3 +52,4 @@ markdown_extensions: - pymdownx.tasklist: custom_checkbox: true - pymdownx.tilde + - mdx_truly_sane_lists