A session-based pair roster: what to allow in Asia vs London

[FTtrader]

Here is the C# cBot implementation designed to run headlessly, monitoring the M15 timeframe and pushing alerts to a mobile terminal when liquidity conditions become optimal.

Code: Select all

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

namespace cAlgo.Robots
{
    [Robot(TimeZone = TimeZones.UTC, AccessRights = AccessRights.None)]
    public class SvrHeadlessScreener : Robot
    {
        [Parameter("ATR Period", DefaultValue = 14, MinValue = 1)]
        public int AtrPeriod { get; set; }

        [Parameter("Minimum SVR Threshold", DefaultValue = 15.0)]
        public double SvrThreshold { get; set; }

        private AverageTrueRange _atr;

        protected override void OnStart()
        {
            // Initialize ATR on the M15 execution timeframe
            _atr = Indicators.AverageTrueRange(MarketData.GetBars(TimeFrame.Minute15), AtrPeriod, MovingAverageType.Simple);
        }

        protected override void OnBar()
        {
            // Retrieve the last closed bar's ATR
            double currentAtr = _atr.Result.Last(1);
            
            // Normalize raw price values to standard pips
            double spreadInPips = Symbol.Spread / Symbol.PipSize;
            double atrInPips = currentAtr / Symbol.PipSize;

            // Prevent division by zero during zero-spread ticks on raw pricing accounts
            if (spreadInPips <= 0) return;

            double svr = Math.Round(atrInPips / spreadInPips, 2);

            if (svr >= SvrThreshold)
            {
                string alertMessage = $"[SVR ALIVE] {Symbol.Name} | SVR: {svr} | Spread: {spreadInPips:F1} pips | M15 ATR: {atrInPips:F1} pips";
                
                // Push notification to the mobile app
                Notifications.SendPushNotification(alertMessage);
                Print(alertMessage);
            }
        }
    }
}

[FTtrader]

Deploying this script on a VPS against a raw spread feed creates a completely passive filtering system. The bot handles the quantitative gating, ensuring that a push notification only fires when the asset has the momentum to clear transaction costs rapidly. Once the alert hits your phone, you can manually open the chart to check if the current price action aligns with your pre-marked H4 and D1 support or resistance zones before executing the M15 scalp.

[FXS Prop Desk]

FTtrader, a headless screener on a VPS pushing alerts to the phone fits the session roster idea neatly, because the roster becomes code rather than a list someone has to remember. A small addition would be to log every alert that fires outside the allowed pairs for the session, without sending it. After a few weeks that log answers the obvious question: are the excluded pairs actually worse at those hours, or just excluded by habit?