# Contrarian Signals
## Contrarian Signals — Trader's Guide (EN)
> **mrD Signals Premium** — How to use **Contrarian Signals** effectively and combine with **Trail Cloud** to maximize win-rate.
***
### 1. What are Contrarian Signals?
Contrarian Signals are designed to catch **strong trend reversals** rather than ride existing trends. The engine fires a `BUY` triangle (▲ green) or `SELL` triangle (▼ red) only when **multi-timeframe trend exhaustion** is confirmed by a **volatility expansion**.
In short: the system waits for **two simultaneous agreements**:
1. **Multiple timeframes saying "the old trend is reversing"** — not just the current chart, but the consensus across several higher and lower timeframes
2. **A volatility burst** — a sudden expansion in range signaling that real liquidity is stepping in, not just normal drift
These two filters (multi-timeframe agreement + volatility expansion) are what makes Contrarian signals **rare but strong**.
> Right mindset: Contrarian isn't "early entry". It's a reversal with evidence — you enter *after* the market has already turned, not by guessing the top/bottom barehanded.
#### Bar coloring — the regime filter
Beside the triangles, every bar is also painted using a composite "regime score" (EMA50 + EMA200 + RSI(14) + support/resistance):
* **Green bar** → bullish score AND price holds above support
* **Red bar** → bearish score AND price stays below resistance
* **Gray / neutral** → no strong regime → **stay out**
> The bar color is your **regime context**. The triangle is your **entry trigger**.
***
### 2. Fixed parameters (no profile selector)
> **Important**: Unlike Waves Trend Signals, Contrarian uses **fixed parameters** matching the original *MTF ATR Reversal Levels* (DeuceDavis / Blackflag FTS) reference indicator. The **Signals Swing** dropdown (Short-/Mid-/Long-Term) has **no effect** on Contrarian — only on Waves Trend.
| Parameter | Value | Notes |
| -------------------------------------- | ------------------------------ | ----------------- |
| **ATR Period** (Wilder MA) | **28** | Reference default |
| **ATR Factor** (trail width) | **3.0** | Reference default |
| **TR/ATR Threshold** (volatility gate) | **1.0** | Reference default |
| **Trail Type** | **modified** | Reference default |
| **Timeframes** | Chart TF + 15m + 30m + 1H + 1D | Reference default |
| **Bar EMA fast / slow** | 50 / 200 | — |
| **Bar Lookback H/L** | 80 | — |
| **Bar Score Threshold** | 0.5 | — |
This means Contrarian behaviour is **identical on every chart**, every asset, every market session — it's the original reference logic, period. The only thing you control is the **chart timeframe** you trade on.
**Recommended chart timeframe**: 5m – 4H. The 5 internal TFs are 15m / 30m / 1H / 1D + chart, so on charts above 1D the lower TFs lose meaning, and below 1m the cloud + signals will lag.
***
### 3. Why you MUST combine with Trail Cloud
> **Contrarian alone gives you the WHEN. Trail Cloud gives you the WHERE and the WHY.** Trading Contrarian signals naked is a trap.
#### What Trail Cloud is
Trail Cloud is a **dynamic trailing cloud** with two built-in anti-noise filters:
1. **Volatility margin** — price must break the trail line by an extra margin before the trend can flip
2. **Multi-bar confirmation** — the opposite direction must persist for several consecutive bars before the cloud actually changes color
Output: a colored cloud (lime = uptrend, red = downtrend) with **3 internal pullback bands** (named F1, F2, F3) that divide the distance between the trail line and the recent extreme into standard pullback zones — F1 is the shallow pullback band, F2 the standard pullback band, and F3 the deep pullback band.
#### Why pairing them works
| Trail Cloud says... | Contrarian BUY ▲ means... | Contrarian SELL ▼ means... |
| ----------------------------- | -------------------------------------------- | --------------------------------------------- |
| **Lime / uptrend** | Pullback into demand → **HIGH-quality long** | Counter-trend → **skip or scalp only** |
| **Red / downtrend** | Counter-trend → **skip or scalp only** | Pullback into supply → **HIGH-quality short** |
| **Just flipped (transition)** | Wait 3–5 bars for the cloud to settle | Wait 3–5 bars for the cloud to settle |
In other words: **Trail Cloud is the regime filter; Contrarian is the entry trigger inside that regime.** The **3 pullback bands** then give you exact pullback zones to enter, place stops, and scale out.
***
### 4. The recommended Setup
#### 4.1 Chart configuration
1. **Indicator overlay** → enable `Trail Cloud`
2. **Signals Detection** → select `Contrarian Signals`
3. **Signals Swing** → *(no effect on Contrarian — leave as is)*
4. (Optional) Enable `DCA Signals Detection` for additional confluence
5. **Chart timeframe** → choose 5m – 4H for best results
#### 4.2 Visual checklist before any trade
* [ ] Trail Cloud is **lime** (long) or **red** (short)
* [ ] The cloud has been the same color for **at least 5 bars** (avoid fresh flips)
* [ ] The Contrarian triangle prints in the **same direction as the cloud**
* [ ] The signal bar color matches the triangle (green bar + ▲ / red bar + ▼)
If all 4 boxes are checked → **A-grade signal**. If 3 of 4 → B-grade (smaller size). If ≤ 2 → **skip**.
***
### 5. Trading playbook (entry · stop · target)
#### 5.1 LONG playbook — `BUY ▲` inside a lime Trail Cloud
| Step | Action |
| -------------- | -------------------------------------------------------------------------------------------------------------- |
| **Entry** | Market on signal close, **or** limit at the Trail Cloud **F1 band** (shallow pullback) — whichever fills first |
| **Stop loss** | A few ticks **below the Trail Cloud line** (the lowest band). If broken → trend likely flipped, exit |
| **TP 1** (1/3) | At previous swing high or recent extreme used by Trail Cloud as reference |
| **TP 2** (1/3) | Trail with the **F2 band** (standard pullback) — exit if price closes below it |
| **TP 3** (1/3) | Hold and trail with the **Trail Cloud line itself** — exit only when the cloud flips red and confirms |
#### 5.2 SHORT playbook — `SELL ▼` inside a red Trail Cloud
| Step | Action |
| -------------- | -------------------------------------------------------------------------------------- |
| **Entry** | Market on signal close, **or** limit at the Trail Cloud **F1 band** (shallow pullback) |
| **Stop loss** | A few ticks **above the Trail Cloud line** |
| **TP 1** (1/3) | At previous swing low or recent low used by the cloud as reference |
| **TP 2** (1/3) | Trail with the **F2 band** (standard pullback) |
| **TP 3** (1/3) | Trail with the Trail Cloud line until it flips lime |
#### 5.3 Position sizing
* **A-grade signal** (all 4 checks) → 100% of normal size
* **B-grade** (3/4 checks) → 50% size
* **Counter-trend** (signal opposite to cloud) → **0% — do not take it**
***
### 6. Win-rate boosters (advanced)
#### 6.1 Filter by pullback-band confluence
The strongest setups happen when the **Contrarian triangle prints inside or just past an F1/F2 pullback band** of Trail Cloud. That means price just tagged a high-probability pullback zone *and* the multi-timeframe reversal logic agrees.
> Rule: take the trade only if the signal bar's wick or close is within the cloud-fill area (between Trail line and F2). Skip signals that fire deep outside the cloud — they're too late.
#### 6.2 Avoid the "fresh flip" trap
The very first signal after Trail Cloud changes color is often a whipsaw. Wait at least **5 bars after the flip** before taking the next Contrarian signal in the new direction.
#### 6.3 Multi-timeframe agreement
Open a higher timeframe chart (e.g. you trade 15m → check 1H). Take the signal **only if the higher-TF Trail Cloud is the same color**. This single rule typically removes the worst losing trades.
#### 6.4 Volume / event awareness
Contrarian signals during news spikes or low-liquidity sessions (Asia open for FX, weekends for crypto) are unreliable. The volatility threshold can fire on a news wick that doesn't follow through.
#### 6.5 Don't fight clusters of opposite signals
If the previous 1–2 Contrarian triangles in the **same direction** failed (price didn't reach TP1), the regime is unclear — wait for the Trail Cloud to flip, *then* take the next one.
#### 6.6 Adapt your timeframe, not the indicator
Since Contrarian uses fixed parameters, the only knob you have is your **chart timeframe**:
* Quiet, ranging market → drop down to a **lower chart TF** (e.g. 1H → 15m) to get more signals per session.
* High-volatility, trending market → step up to a **higher chart TF** (e.g. 15m → 1H) so the 5 internal TFs cover a wider window and filter noise.
***
### 7. Common mistakes to avoid
1. **Taking a triangle against the cloud color** — the #1 reason for losing trades. Always confirm cloud direction first.
2. **Ignoring bar color** — gray bars = no regime = skip.
3. **Stop loss too tight** — Contrarian signals fire after a strong move, so the very next bar can have a wide range. Place the stop **beyond the Trail Cloud line**, not at the signal candle low/high.
4. **Trying to "tune" Contrarian via Signals Swing** — the dropdown does nothing for Contrarian. Don't waste time switching it.
5. **Disabling Trail Cloud to "see signals better"** — you remove the single most important confirmation tool. Keep it on.
6. **Adding to a losing Contrarian trade** — these are reversal signals; if it didn't work in the first 3–5 bars, the reversal failed.
***
### 8. Quick reference card
```
╔══════════════════════════════════════════════════════════╗
║ CONTRARIAN + TRAIL CLOUD CHECKLIST ║
╠══════════════════════════════════════════════════════════╣
║ 1. Trail Cloud color = signal direction? [Y/N] ║
║ 2. Cloud held color ≥ 5 bars? [Y/N] ║
║ 3. Bar color matches triangle? [Y/N] ║
║ 4. Signal inside / near F1–F2 cloud band? [Y/N] ║
║ 5. Higher-TF cloud same color? [Y/N] ║
║ ║
║ 5/5 → A+ trade, 100% size ║
║ 4/5 → A trade, 100% size ║
║ 3/5 → B trade, 50% size ║
║ ≤2 → SKIP ║
╠══════════════════════════════════════════════════════════╣
║ ENTRY : market on signal OR limit at F1 band ║
║ STOP : just past Trail Cloud line ║
║ TP1 : previous swing / recent extreme (1/3) ║
║ TP2 : trail F2 band (1/3) ║
║ TP3 : trail Trail Cloud line (1/3) ║
╚══════════════════════════════════════════════════════════╝
```
***
### 9. FAQ
**Q. I see no signals at all.** A. Contrarian uses fixed strict parameters by design. On quiet markets it may print only a handful of signals per month. Try a **lower chart timeframe** (e.g. drop from 1H to 15m) to get more activity.
**Q. Signals are too noisy.** A. **Always require Trail Cloud confirmation** — if cloud color disagrees → skip. Also try a **higher chart timeframe** so the 5 internal TFs cover a wider window and filter intraday noise.
**Q. Does the Signals Swing dropdown affect Contrarian?** A. **No.** That dropdown only affects Waves Trend Signals. Contrarian uses fixed reference parameters regardless of what you pick there.
**Q. Can I use Contrarian on every market?** A. It works best on **liquid, trending instruments**: BTC/ETH, major FX pairs, large-cap indices, large-cap stocks. On thin penny stocks the volatility threshold misfires too often.
**Q. Should I use it on lower than 1m or higher than 1D?** A. The system uses multi-timeframe agreement up to the daily chart. Above 1D the lower TFs lose meaning. Below 1m the cloud + signals will lag. **5m to 4H** is the sweet spot.
**Q. Can I automate this?** A. Yes — use the existing alert blocks in the script and add a Trail-Cloud-color filter on your alert webhook side, e.g. only forward `BUY` alerts when the Trail Cloud is currently lime.
***
> **Final word**: Contrarian Signals are *high-probability when filtered, high-loss when not*. Trail Cloud is not optional — it is the **filter that turns this from a coin-flip into an edge**. Always trade them together.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.mrd-indicators.com/feature/tradingview-indicators/mrd-signals-premium-eng/contrarian-signals.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.