forex-scalping.com

3. Practical Calculation Example: XAUUSD

Gold is the perfect example of why fixed pips fail, as its intraday volatility can shift drastically. Let's assume you are taking a long setup on the M15 chart.

Current M15 ATR: $2.50 (25 pips)

Entry Price: $2400.00

Risk Parameters: 1.5x ATR Stop Loss, 3.0x ATR Take Profit (1:2 RR)

The Math:

Calculate SL Distance: $2.50 × 1.5 = $3.75

Calculate TP Distance: $2.50 × 3.0 = $7.50

Set Hard Stop: $2400.00 - $3.75 = $2396.25

Set Hard Target: $2400.00 + $7.50 = $2407.50

If you took the exact same setup a week later during a quiet pre-market session and the M15 ATR was only $1.20, your stop would automatically tighten to $1.80, allowing you to capture a 1:2 RR on a much smaller market move.

4. The Critical Adjustment: Dynamic Position Sizing

Because your stop loss distance is now constantly changing, your lot size must dynamically adjust to keep your account risk constant. If you risk 1% of your equity per trade, a wider ATR stop requires a smaller lot size, and a tighter ATR stop allows a larger lot size.

Lot Size Formula: Risk Amount in USD / (Stop Loss in Points × Tick Value)

If you are risking $100:

High Volatility (37.5 pip SL): $100 / $37.50 per standard lot = 0.26 Lots

Low Volatility (18.0 pip SL): $100 / $18.00 per standard lot = 0.55 Lots

5. Algorithmic Implementation (MQL5 & cTrader)

If you are building this into an EA or automated script, the logic is straightforward:

In MQL5: Call iATR(_Symbol, PERIOD_CURRENT, 14) to grab the handle, copy the buffer, and multiply it by your input variable InpATRMultiplier. Normalize the final calculation using NormalizeDouble() to match the symbol's digits before passing it to OrderSend().

In cAlgo (C#): Call Indicators.AverageTrueRange(14, MovingAverageType.Simple) and multiply Result.LastValue by your multiplier.

Using ATR-based targets ensures you are never demanding more from the market than it is currently capable of giving, and your stops are never placed inside the immediate blast radius of normal price action.

Normalising by the pair's typical volatility helps if you trade several pairs. An ATR of 10 pips on EURUSD M5 might be high, while the same on GBPJPY might be low. Recording ATR as a ratio of its own average, like current ATR divided by the 20 day average, makes values comparable across pairs. Then a filter based on that ratio works for all of them instead of needing separate numbers for each. It also makes it easier to reuse the same thresholds when you add a new pair, since the ratio is already normalised.

Volatility at entry and volatility during the trade can differ. A trade entered in a quiet period might see volatility jump when news hits. Recording ATR at exit too, or the maximum ATR during the trade, shows whether trades that saw volatility change behaved differently. That's more effort, but for an EA it's easy to log. It can reveal that the trades that went wrong were mostly the ones where conditions changed after entry, which is a different problem from entering in the wrong conditions. Knowing that helps decide whether the fix is a filter at entry or a rule for managing trades when volatility jumps.

Recording ATR at exit as well as at entry is a useful addition. For EAs it is easy, as you say. For manual traders, a simpler version is to note whether a news event happened during the trade. That captures most of the cases where volatility changed after entry. If the trades that went wrong were mostly ones where news landed while the trade was open, the fix is a rule about holding through events, not a new entry filter.

Spread at entry is a related number to record alongside volatility. When volatility is low, spreads are often tight, and when it spikes, spreads widen. Recording both lets you see whether poor results in high volatility come from the market moving against you or from paying a wider spread at entry. If it's mainly the spread, waiting for spreads to settle before entering might be enough. If it's the market, a volatility filter might be needed. The two numbers together separate the causes. Both are easy for an EA to log automatically.

Do people adjust position size by volatility at entry? Some traders use ATR to set the stop distance and then size the position so the risk in money stays constant. That way, higher volatility means a wider stop and a smaller position, and lower volatility means a tighter stop and a bigger one. Recording ATR at entry makes it easy to check whether that sizing approach is being followed consistently. It also shows whether results differ between high and low volatility trades even with risk held constant. That check is quick once the column exists.

The point about quiet weeks not always meaning bad execution is one I needed years ago. I once blamed myself for a poor week and tightened my rules, when the real story was the ATR on M15 sitting about a third lower than usual. Targets of 12 pips just weren't getting reached.

What I do now is record ATR(14) on the entry timeframe and the ratio to its 20 day average. A trade taken at 0.6 of normal volatility is flagged differently from one at 1.5. After a couple of hundred trades I split them into thirds. My own result was that the low third averaged about -0.05R, the middle +0.20R, the high third +0.08R. So not the same shape for every system, but you can see where the sweet spot is.

The thing to watch is sample size. A third of 200 trades is only 66, so I treat it as a lead rather than proof, and I only change position size if it holds over the next batch.

Do you scale the stop by ATR as well, or keep fixed pips and just filter? And does your EA log the value at entry or at the signal bar?