Page 1 of 2

Position sizing from ATR on M1 without turning it into indicator soup

Posted: Sat Sep 12, 2026 8:40 pm
by LondonScalper
Sizing note for scalpers who want volatility-aware risk without a Christmas-tree chart.

I use a short ATR only as a risk ruler, not as an entry signal. On M1 that means one number before the session, not a live oscillator I stare at.

Practical version
1. Take ATR(14) on M1 for the pair I’m trading that day (or a pre-saved average from the last few sessions).
2. Convert my stop distance into a multiple of that ATR (e.g. stop ≈ 0.8–1.2× ATR for my usual scalp structure).
3. Size so that if the stop is hit, cash risk is still my fixed R — not “whatever lots feel right.”

What I refuse: stacking ATR with three other filters until the chart decides for me. ATR here answers one question — how wide is normal noise so my stop isn’t inside it — then I go back to levels and tape.

Session caveat
London open ATR can be a different animal from mid-morning. If I size off a sleepy Asia print and then trade the open, I’m under-sized for the stop I need or over-sized for the stop I wrote. I refresh the ruler at the open, once.

If you size off fixed pips only, fair enough — just know a “10-pip stop” on GBPUSD at 08:05 is not the same risk unit as at 11:00. How do you keep sizing boring on purpose?

Re: Position sizing from ATR on M1 without turning it into indicator soup

Posted: Sun Sep 27, 2026 1:56 pm
by PropScalpDesk
Refreshing at the open once is the right instinct. What worked better for me than ATR(14) at 08:00 is a time-of-day ATR: the average one-minute range for the same 30-minute window over the previous five sessions. ATR(14) on M1 at 08:02 is still mostly measuring the last minutes of the pre-open, while the same-window average tells you what 08:00 to 08:30 normally looks like.

The sizing itself stays as you describe: lots = cash risk divided by (stop in pips times pip value). I round down, never up, because rounding up is where a fixed R quietly turns into 1.2R.

Re: Position sizing from ATR on M1 without turning it into indicator soup

Posted: Sun Sep 27, 2026 3:19 pm
by PTScalper
LondonScalper wrote: Sat Sep 12, 2026 8:40 pm Sizing note for scalpers who want volatility-aware risk without a Christmas-tree chart.

I use a short ATR only as a risk ruler, not as an entry signal. On M1 that means one number before the session, not a live oscillator I stare at.

Practical version
1. Take ATR(14) on M1 for the pair I’m trading that day (or a pre-saved average from the last few sessions).
2. Convert my stop distance into a multiple of that ATR (e.g. stop ≈ 0.8–1.2× ATR for my usual scalp structure).
3. Size so that if the stop is hit, cash risk is still my fixed R — not “whatever lots feel right.”

What I refuse: stacking ATR with three other filters until the chart decides for me. ATR here answers one question — how wide is normal noise so my stop isn’t inside it — then I go back to levels and tape.

Session caveat
London open ATR can be a different animal from mid-morning. If I size off a sleepy Asia print and then trade the open, I’m under-sized for the stop I need or over-sized for the stop I wrote. I refresh the ruler at the open, once.

If you size off fixed pips only, fair enough — just know a “10-pip stop” on GBPUSD at 08:05 is not the same risk unit as at 11:00. How do you keep sizing boring on purpose?
Hi LondonScalper,

Treating position sizing as an administrative baseline rather than a trading decision is exactly how you survive the M1 timeframe. When the chart is stripped of lagging indicators, the cognitive bandwidth freed up by removing the "Christmas-tree" can be entirely focused on raw price action, market microstructure, and liquidity sweeps.

Here is an expansion on how to operationalize that philosophy, keeping the execution sterile and the chart completely clean.

1. Automating the "Boring" Math

To keep sizing intentionally boring, the manual math must be eliminated. Staring at an ATR value and calculating lot sizes right as price sweeps a key level creates hesitation. Since the ATR is just a ruler, it can be entirely delegated to the background.

The Scripted Snapshot: Instead of plotting the ATR line, a lightweight MQL5 or C# cAlgo utility can be programmed to quietly snapshot the M1 ATR(14) at a specific timestamp (e.g., exactly at 08:00 for the London open) and freeze it in memory.

Visual Order Execution: You drop a visual line on the chart where your structural stop belongs. The script instantly reads that pip distance, compares it against the frozen ATR snapshot to confirm it sits outside the noise band, and calculates the exact lot size to risk precisely 1R. You never look at a number; you just read the structure and click execute.

Re: Position sizing from ATR on M1 without turning it into indicator soup

Posted: Sun Sep 27, 2026 3:20 pm
by PTScalper
2. Anchoring the Ruler to Market Structure

An ATR multiple alone shouldn't dictate the stop location—structure does. ATR simply acts as a filter for that structural decision.

The Noise Buffer: If you are trading a reversal off an M15 liquidity sweep, your hard stop goes just beyond the extreme of that sweep. The ATR's job is simply to answer: Is this structural stop wider than the current minute-by-minute breathing of the market?

The Invalidation Check: If your structural stop is 5 pips, but the current M1 ATR is printing 7 pips, you are placing a stop inside random noise. You are forced to either widen the stop (and automatically reduce lot size to maintain the fixed cash risk) or skip the setup entirely because the market is too erratic for your edge.

3. The Session Volatility Trap

Your caveat about the London open is critical. The transition from Asia to London isn't just a shift in directional volume; it is a fundamental change in order book density and spread dynamics.

Spread Vulnerability: A fixed 10-pip stop that is mathematically safe in a sleepy Asian session can be taken out by a momentary spread expansion at 08:05, even if the actual bid price barely moves.

The Volatility Reset: Refreshing the ATR ruler right as the bell rings recalibrates your sizing to the new liquidity reality. If London injects heavy volatility, the ATR expands, your required pip-distance naturally widens to avoid the chop, and your position size automatically shrinks to keep the cash risk identical.

Re: Position sizing from ATR on M1 without turning it into indicator soup

Posted: Sun Sep 27, 2026 3:20 pm
by PTScalper
4. The Psychological Edge of Fixed Risk

When sizing becomes a background algorithmic process, you eliminate the single biggest account killer: discretionary sizing based on conviction.

"Feeling" what lot size is right destroys the mathematical expectancy of a scalping edge. Boring sizing means a loss on a highly volatile GBPUSD open hits the exact same cash limit as a loss during a quiet mid-morning drift. It prevents the classic scalper's tilt where a trader takes a loss on a tight stop, then tries to make it back with double the lots on a wider stop, completely breaking the math of the system.

By demanding the ATR answer only one question—"how wide is normal noise?"—you strip away the noise of the indicator itself and get back to reading the tape.

Re: Position sizing from ATR on M1 without turning it into indicator soup

Posted: Sun Sep 27, 2026 3:21 pm
by PTScalper
To build this in cTrader using C# cAlgo, we need a Robot (cBot) rather than an Indicator. This allows us to handle chart interactions, calculate position sizing, and execute the trade, all while keeping the visual footprint strictly to a single draggable horizontal line and a lightweight UI panel.

Here is the architectural breakdown and the core C# logic to achieve this event-driven, visual sizing tool.

1. State and Parameter Initialization

We need to define our fixed risk, the target session time, and initialize the M1 ATR in the background. Because you only want the M1 ATR as a background reference, we instantiate the indicator using the M1 series, regardless of what timeframe the chart is currently displaying (e.g., your M15 or Daily structure chart).

Code: Select all

using cAlgo.API;
using cAlgo.API.Indicators;
using System;

[Robot(TimeZone = TimeZones.UTC, AccessRights = AccessRights.None)]
public class VisualRiskSizer : Robot
{
    [Parameter("Fixed Cash Risk ($)", DefaultValue = 100)]
    public double FixedRisk { get; set; }

    [Parameter("Snapshot Time (UTC)", DefaultValue = "08:00")]
    public string SnapshotTimeStr { get; set; }

    [Parameter("ATR Period", DefaultValue = 14)]
    public int AtrPeriod { get; set; }

    private AverageTrueRange _m1Atr;
    private double _frozenAtr = 0;
    private TimeSpan _snapshotTime;
    
    // UI Elements
    private ChartHorizontalLine _stopLossLine;
    private TextBlock _calcText;

    protected override void OnStart()
    {
        TimeSpan.TryParse(SnapshotTimeStr, out _snapshotTime);
        
        // Initialize ATR strictly on the M1 series, hidden from the chart
        var m1Series = MarketData.GetSeries(TimeFrame.Minute);
        _m1Atr = Indicators.AverageTrueRange(m1Series, AtrPeriod, MovingAverageType.Simple);

        InitializeUI(); // Sets up the draggable SL line and the on-chart text
    }
}

Re: Position sizing from ATR on M1 without turning it into indicator soup

Posted: Sun Sep 27, 2026 3:21 pm
by PTScalper
2. The Time-Locked Snapshot Mechanism

Instead of recalculating continuously, we listen to the OnBar event of the M1 timeframe. When the server time matches your session open, we snapshot the last closed bar's ATR and freeze it in state.

Code: Select all

protected override void OnBar()
{
    // Ensure we are checking the M1 time, even if the cBot is attached to an M15 chart
    var currentServerTime = Server.Time.TimeOfDay;

    if (currentServerTime.Hours == _snapshotTime.Hours && 
        currentServerTime.Minutes == _snapshotTime.Minutes)
    {
        // Snapshot the closed M1 bar's ATR
        _frozenAtr = _m1Atr.Result.Last(1); 
        
        Print($"London Open ATR Locked: {Math.Round(_frozenAtr / Symbol.PipSize, 1)} pips");
        UpdatePanel(); // Refresh UI to show the new noise baseline
    }
}

Re: Position sizing from ATR on M1 without turning it into indicator soup

Posted: Sun Sep 27, 2026 3:21 pm
by PTScalper
3. Chart Visuals and Drag Events

cTrader's API allows for interactive chart objects. We draw a horizontal line for the Stop Loss that you can physically drag to your structural invalidation point. We bind an event handler to this line so that every time you drop it, the math recalculates instantly.

Code: Select all

private void InitializeUI()
{
    // Draw an interactive line slightly below current price
    _stopLossLine = Chart.DrawHorizontalLine("SL_Line", Symbol.Bid - (10 * Symbol.PipSize), Color.Red);
    _stopLossLine.IsInteractive = true;

    // Subscribe to object modification to recalculate on drag
    Chart.ObjectsUpdated += OnChartObjectsUpdated;
    
    // (UI setup for _calcText omitted for brevity - standard cTrader Canvas approach)
}

private void OnChartObjectsUpdated(ChartObjectsUpdatedEventArgs args)
{
    if (args.ChartObjects.Contains(_stopLossLine))
    {
        CalculateSizing();
    }
}

Re: Position sizing from ATR on M1 without turning it into indicator soup

Posted: Sun Sep 27, 2026 3:22 pm
by PTScalper
4. Sizing Math & The "Noise" Check

When the line is moved, the cBot reads the distance between the current price and the line. It compares this distance to the _frozenAtr to warn you if your stop is inside market noise, and then calculates the exact normalized volume required to risk your fixed cash amount.

Code: Select all

private void CalculateSizing()
{
    if (_frozenAtr == 0) return; // Wait for snapshot

    double slPrice = _stopLossLine.Y;
    double currentPrice = slPrice < Symbol.Bid ? Symbol.Ask : Symbol.Bid; // Auto-detect Long/Short
    
    double slDistance = Math.Abs(currentPrice - slPrice);
    double slDistanceInPips = slDistance / Symbol.PipSize;
    double atrInPips = _frozenAtr / Symbol.PipSize;

    // 1. Noise Filter Check
    bool insideNoise = slDistance < _frozenAtr;
    string noiseWarning = insideNoise ? "WARNING: Stop inside M1 ATR noise." : "Stop is structurally safe.";

    // 2. Volume Calculation (Risk / (SL * TickValue))
    // Note: cTrader uses TickSize/TickValue for precise fiat conversion
    double exactVolume = FixedRisk / (slDistance / Symbol.TickSize * Symbol.TickValue);
    
    // Normalize to broker's allowed lot steps
    double normalizedVolume = Symbol.NormalizeVolumeInUnits(exactVolume, RoundingMode.Down);

    // 3. Update the visual text block on the chart
    _calcText.Text = $"ATR: {Math.Round(atrInPips, 1)} | " +
                     $"SL: {Math.Round(slDistanceInPips, 1)} pips | " +
                     $"Vol: {normalizedVolume}\n" +
                     $"{noiseWarning}";
}

Re: Position sizing from ATR on M1 without turning it into indicator soup

Posted: Sun Sep 27, 2026 3:22 pm
by PTScalper
Execution

To execute, you simply add a button click handler to your UI panel that calls ExecuteMarketOrder(), passing in the normalizedVolume and the physical slPrice from the line.

This architecture gives you exactly what you want: the chart remains entirely clean aside from a single red line and a text box. You drag the line below the liquidity sweep, look at the text to confirm it clears the frozen ATR, and click execute. No indicators plotted, no mental math, and precise 1R risk management.