[mdeacey] EMA% Channel + BB Range Strategy

24 thg 12, 2021

This strategy is based off the users selection of an EMA and percentage defined channel. The strategy longs when a red "reversal candle" (that exceeds the averages of 3 and 9 above the EMA 3) is found until such time that either the price goes outside the Bollinger Band or the green reversal candle is found. The same but opposite process for shorts. If the price begins trending and moves outside the channel all trades are exited to prevent loss.

For trending markets the sister strategy ("[mdeacey] EMA% Channel + Bollinger Band Trending Strategy") should instead be used.

The obvious fallback to this strategy is that:
- If the bands are too wide we don't have a good definition of trending vs ranging and the price can move up/down significantly and trend whilst remaining within the ranging channel. We try to mitigate this through use of a stoploss defined by ATR and a pretty tight channel. This is a tightrope exercise as making the percentage channels tighter misses earlier entries in optimal cases. Change the parameters to find an EMA and percentages to find the best R/R in your case.

Potential further iteration:
- It would be good to see if the R/R changes positively if we only allow shorts above the EMA and longs below it.

All options are configurable and code open source. Happy trading!

27 thg 12, 2021

Phát hành các Ghi chú

Update:
- Now only allowing shorts above the EMA and longs below it. R/R increased!

29 thg 12, 2021

Phát hành các Ghi chú

Strategy now includes the use of glaz's "RSI Candles" indicator (tradingview.com/script/RADlhsKE-RSI-Candles/). The basis for including this indicator into the strategy is to delay position entries if red/green RSI candles are found with the hope to remove entries that ride the bollinger band and end up getting stopped out - decreasing the total number of trades but increasing both profitability and rate of return. This update also closes trades when the opposite bollinger band is crossed on close as I noticed this causing a number of entries to be closed too early in their move.