ru
Feedback
MQL5 Algo Trading

MQL5 Algo Trading

Открыть в Telegram

The best publications of the largest community of algotraders. Subscribe to stay up-to-date with modern technologies and trading programs development.

Больше

📈 Аналитический обзор Telegram-канала MQL5 Algo Trading

Канал MQL5 Algo Trading (@mql5dev) языкового сегмента Английский является активным участником. Сейчас сообщество объединяет 514 325 подписчиков, занимая 149 место в категории Технологии и приложения и 5 место в регионе Великобритания.

📊 Показатели аудитории и динамика

С момента создания невідомо проект демонстрирует стремительный рост, собрав аудиторию из 514 325 подписчиков.

Согласно последним данным от 28 июня, 2026, канал показывает стабильную активность. За последние 30 дней изменение числа участников составило 8 507, а за последние 24 часа — 138, при этом общий охват остаётся высоким.

  • Статус верификации: Не верифицирован
  • Уровень вовлечённости (ER): Средний показатель вовлечённости аудитории составляет 3.32%. В первые 24 часа после публикации контент обычно набирает 1.88% реакций от общего числа подписчиков.
  • Охват публикаций: В среднем каждый пост получает 17 087 просмотров. В течение первых суток публикация набирает 9 677 просмотров.
  • Реакции и взаимодействия: Аудитория активно поддерживает контент: среднее количество реакций на один пост — 38.
  • Тематические интересы: Контент сосредоточен на ключевых темах, таких как indicator, chart, mql5, candle, range.

📝 Описание и контентная политика

Автор описывает ресурс как площадку для выражения субъективного мнения:
The best publications of the largest community of algotraders. Subscribe to stay up-to-date with modern technologies and trading programs development.

Благодаря высокой частоте обновлений (последние данные получены 29 июня, 2026) канал поддерживает актуальность и высокий уровень охвата публикаций. Аналитика показывает, что аудитория активно взаимодействует с контентом, что делает его важной точкой влияния в категории Технологии и приложения.

514 325
Подписчики
+13824 часа
+2 0757 дней
+8 50730 день
Архив постов
A time-based exit routine can be built by storing configured hour and minute values, then checking the platform time on each
A time-based exit routine can be built by storing configured hour and minute values, then checking the platform time on each tick. When the current time matches the configured schedule, the logic can run only once per day to prevent repeated triggers. A separate date check should confirm that the current weekday is Friday before acting. If not Friday, the routine should exit without changes. When both conditions are met, filter open positions by symbol (currency pair) and evaluate profit per position. Close only positions with positive profit, leaving losing or zero-profit positions untouched. Use reliable order/position iteration, handle partial fills, validate trade permissions, and log close results and error codes for auditing. 👉 Read | Signals | @mql5dev

The article reframes “market physics” as modeling price with measurable components rather than intuitive narratives. Since pr
The article reframes “market physics” as modeling price with measurable components rather than intuitive narratives. Since price is discrete, derivatives are treated as average changes over a fixed step, and only statistical properties (expectation, variance) are considered realistically exploitable. A practical simplification is proposed: approximate the predictable component via market-player pressure, expressed as the imbalance between aggregated buy and sell volumes. To avoid unreliable, broker-specific tick streams, the model prefers bar data (O/H/L/C) for stability and speed. It then outlines four ways to extract patterns—hand-built formulas, order-flow simulation, general mathematical principles, and machine learning—highlighting a position-simulator EA that places stop/limit/market order grids per bar, updates incrementally, and trades on the evolvi... 👉 Read | Forum | @mql5dev

An Expert Advisor design combines three standard building blocks: ADX for trend strength confirmation, EMA for pullback timin
An Expert Advisor design combines three standard building blocks: ADX for trend strength confirmation, EMA for pullback timing, and ATR for volatility-scaled risk controls. Signal processing is restricted to closed bars on a selectable indicator timeframe and evaluated once per new bar. Entry requires ADX above a threshold and rising versus the prior bar, filtering out flat or weakening conditions. A pullback is identified when the price-to-EMA distance (normalized by ATR) transitions from at-or-above a configured ratio to below it on the next bar, indicating a completed approach-and-rejection sequence. Direction is taken from +DI and -DI on the prior bar, with optional buy-only or sell-only constraints. Stop loss is set as ATR multiplied by an SL factor, while take profit is derived via a fixed risk-reward ratio. Execution enforces one open position per sy... 👉 Read | Forum | @mql5dev

Retail volume bars report transaction count per period, but without price response they add little. High volume with limited
Retail volume bars report transaction count per period, but without price response they add little. High volume with limited price progress often signals absorption rather than trend strength, with aggressive flow being met by resting liquidity. Kyle’s Lambda measures liquidity density via a simple impact ratio: |ΔPrice|/Volume. The result approximates the cost to move price by one point, separating real participation from low-quality moves driven by thin liquidity. Low lambda during high volume indicates absorption and potential accumulation or distribution zones. High lambda spikes flag liquidity vacuums where small volume produces outsized gaps and unstable continuation. Implementation notes for MT4 include backward-index parsing to minimize CPU load in a single-threaded runtime, plus division guards for session opens, weekend gaps, and zero-v... 👉 Read | Calendar | @mql5dev

Part 2 moves from option emulation theory to a working MT5 EA that trades the underlying while tracking an emulated option’s
Part 2 moves from option emulation theory to a working MT5 EA that trades the underlying while tracking an emulated option’s delta. The EA converts “emulation levels” into real positions and continuously rebalances to keep the synthetic exposure aligned with the selected construction (Long/Short Call/Put), using daily expiration. The design introduces an option-construction base class built on MQL5’s CList, letting developers compose portfolios and compute total delta by iterating contained options. A range-setting method normalizes delta behavior per strike, making future multi-leg strategies straightforward to extend. On each tick, the EA updates the current level, adds or closes market positions when the level changes, and fully exits at level zero or at the forced expiration time. Practical details include lot-step normalization, magic-number encoding p... 👉 Read | NeuroBook | @mql5dev

AlternativeBarsViewer adds in-terminal inspection for the 10 alternative bar types from López de Prado, using the same CBarCo
AlternativeBarsViewer adds in-terminal inspection for the 10 alternative bar types from López de Prado, using the same CBarConstructor hierarchy as BarBuilderEA to keep outputs consistent across EA, indicator, and Python checks. Three data sources are supported: real ticks via CopyTicksRange with millisecond deduplication, synthetic ticks derived from chart OHLC, and replay from the EA’s per-type CSV with auto reload on file size changes. Tick and OHLC modes also show the current forming bar. Rendering uses DRAW_COLOR_CANDLES with buffers for OHLC plus a color index. Closed bars can be projected by time-slot alignment or packed sequentially by index. Colors separate bullish, bearish, and in-progress bars, and surface degenerate bars that close with minimal tick volume. A lightweight subwindow panel reports bar stats, degenerate counts, last times... 👉 Read | NeuroBook | @mql5dev

Adding timing, logging, or filtering directly into an RSI class turns one indicator into a shared container for unrelated con
Adding timing, logging, or filtering directly into an RSI class turns one indicator into a shared container for unrelated concerns. Each edit increases regression risk, expands the test matrix across EAs, and raises merge-conflict probability. These concerns belong to usage context, not to RSI computation. A decorator chain keeps the core indicator closed for modification. All components implement IIndicator with GetValue(shift) and GetName(). Decorators wrap an IIndicator pointer, delegate calls downward, then add behavior before or after the delegation. The EA holds only the outermost IIndicator*. Typical stack: CTimingDecorator → CLoggingDecorator → CThresholdFilterDecorator → CRSIIndicator. Order matters: side-effect decorators observe; filters transform values. Ownership is hierarchical: deleting the outermost decorator frees the entire chain safely. 👉 Read | AppStore | @mql5dev

DA-CG-LSTM targets dynamic multivariate time series where volatility and latent drivers degrade classical forecasting. The de
DA-CG-LSTM targets dynamic multivariate time series where volatility and latent drivers degrade classical forecasting. The design combines dual attention with a modified CG-LSTM to separate relevant signals from noise while retaining both long-range dependencies and short-term reactions. Feature attention reweights inputs per timestep, then temporal attention selects informative history windows. The CG-LSTM block adds control over memory updates using feature and time relevance, improving stability on long sequences and reducing stochastic artifacts. Implementation work in MQL5 consolidates existing components: a linear attention module reused from Hidformer and a previously implemented CG-LSTM block. Model design extends beyond point forecasts by integrating an encoder latent space with an Actor-Director-Critic RL stack, plus a probabilistic trend m... 👉 Read | Calendar | @mql5dev

This part extends an MQL5 replay/simulation stack by turning a SQLite helper class from “run scripts only” into a component t
This part extends an MQL5 replay/simulation stack by turning a SQLite helper class from “run scripts only” into a component that can execute SELECT queries and expose result sets to MQL5 code. It highlights a behavioral mismatch in MT5’s built-in SQLite (Build 3815): dropping tables with active foreign-key relationships can fail when the same script is executed again shortly after, while standalone SQLite may succeed. A practical workaround is deleting the database file and recreating it from embedded SQL resources. On the implementation side, the database is built from two embedded scripts: one for schema, one for seed data. Query support is added via DatabasePrepare for prepared statements, DatabaseFinalize to release prior statements, and a separate read step to consume results, avoiding redundant queries and improving performance for trading tools. 👉 Read | Forum | @mql5dev

MetaTrader 5 does not emit mouse events for chart apps by default to protect performance, so indicators and EAs must explicit
MetaTrader 5 does not emit mouse events for chart apps by default to protect performance, so indicators and EAs must explicitly enable only the required mouse resources and reliably disable them on shutdown. Failing to “turn off what was turned on” can leave a chart generating unnecessary events and degrade responsiveness. Mouse input is received through OnChartEvent, with separate handling for move and wheel actions. Mouse coordinates are reported only inside the chart’s client area, using chart-local coordinates, and values often need explicit type conversion before display or logic. The article also covers controlled capture of mouse buttons and related UI controls. Developers can temporarily block built-in chart behaviors (dragging, context menu, crosshair, keyboard scrolling/zoom, ENTER symbol input) to avoid conflicts, but must restore default... 👉 Read | Forum | @mql5dev

The SymbolInfo sample has been reworked from a single source file plus two headers into a three-file variant where each unit
The SymbolInfo sample has been reworked from a single source file plus two headers into a three-file variant where each unit now contains two functions and explicit call sites. Output rendering was also redesigned to improve readability and consistency. Nine output fields were added. Seven are standard symbol attributes, with two additional risk-related values: Margin Required (MT4 naming) and Standard Leverage. Margin Required is derived from the symbol’s Margin Calc Mode, while Standard Leverage is derived from Margin Required and may differ by volume depending on broker rules. All formulas and calculation steps follow the standard MQL5 documentation. 👉 Read | AppStore | @mql5dev

CoSO (Community of Scientists Optimization) is an optimization algorithm published in 2012 by A. Milani and V. Santucci. It m
CoSO (Community of Scientists Optimization) is an optimization algorithm published in 2012 by A. Milani and V. Santucci. It models a research community: agents publish to journals, compete for limited funds, form local groups, and keep diversity via funded outsiders. Population size can change during runtime. Each agent maintains position x, velocity v, personal best b, funds m, strategy s, and journal selection probabilities ρ. Velocity update combines inertia, cognitive pull to b, and a weighted social term from journal entries; position updates as x(t)=x(t-1)+v(t). Journals act as shared memory, storing the top-k solutions, updated only when a submission improves the worst entry. Funds are redistributed by rank roulette; inactive agents drop out when m reaches zero. Outsider share Ω adapts using fitness standard deviation, while successful agent... 👉 Read | Calendar | @mql5dev

Standard indicators capture level, range, and volatility, but miss trajectory shape. Two EURUSD windows can match mean close,
Standard indicators capture level, range, and volatility, but miss trajectory shape. Two EURUSD windows can match mean close, average range, and realized volatility while producing different phase-space paths: an elongated arc versus a closed loop. Topological Data Analysis focuses on invariants across scales and represents signal as birth-death pairs in a persistence diagram. The prerequisite step is converting a 1D series into a higher-dimensional point cloud, then defining a distance metric over that cloud. Takens time-delay embedding constructs vectors (x[i], x[i+tau], …) with user-controlled embDim and delay. The implementation uses CTDAPointCloud as a flat buffer for cache-friendly access. CTDADistance builds an NxN symmetric distance matrix under Euclidean, Manhattan, or Chebyshev norms, tracking max distance for later filtrations. 👉 Read | CodeBase | @mql5dev

Chart objects can now be edited after placement via a floating property ribbon. The update replaces fixed-at-creation styles
Chart objects can now be edited after placement via a floating property ribbon. The update replaces fixed-at-creation styles with descriptor-driven editing and a snapshot-based preview/rollback model. Four components back the system: per-tool property descriptors, engine get/set by string ID, widget renderers per property type, and a ribbon that binds widgets to the selected object and applies changes live. Descriptors define type, label, range, defaults, and visibility for ribbon vs settings. Composite types cover compact rows, per-level lists for Fibonacci/Gann, and action entries. Engine property access resolves object ID, dispatches by property ID, supports per-level arrays, and rejects non-applicable properties cleanly. Changes can be previewed immediately and reverted on cancel. 👉 Read | Forum | @mql5dev

Part 71’s weekend-gap marker is upgraded into a rule-based, automatable signal model for MT5. The indicator defines each gap
Part 71’s weekend-gap marker is upgraded into a rule-based, automatable signal model for MT5. The indicator defines each gap using Friday close and Monday open, filters by minimum tradable size, and only confirms entries on candle close (optionally requiring a price offset), keeping signals non-repainting. Bullish logic: after a gap-down, a bullish close back above the gap low triggers a buy. Bearish logic: after a gap-up, a bearish close back below the gap high triggers a sell. Take-profit targets the opposite gap boundary; stop-loss anchors to the current week’s swing extreme with an optional buffer. Implementation focuses on EA integration: six CopyBuffer-readable outputs (buy/sell arrows plus TP/SL for each), historical signal reconstruction, and a structured pipeline from gap detection to live updates and cleanup. 👉 Read | NeuroBook | @mql5dev

This article turns the NLMS-based SAMA from a textbook update rule into a production-grade MQL5 indicator designed to behave
This article turns the NLMS-based SAMA from a textbook update rule into a production-grade MQL5 indicator designed to behave predictably in live charts. The implementation avoids common pitfalls: it never trains on the still-forming candle, seeds weights to a neutral 1/N prior to prevent startup instability, and enforces a warm-up phase to reduce session-to-session re-render differences. Robustness is handled explicitly: NLMS energy normalization is protected with an epsilon floor, extreme one-bar shocks are capped via ATR-based error clamping, and weight leakage adds controlled forgetting. An optional constraint normalizes weights to sum to 1.0, keeping outputs on the price scale. Tuning is practical: inputs support PRICE/DIFF/RET training, an Efficiency-Ratio adaptive learning rate, and guidance to keep μ ≤ 1.0 for stable tracking. Limitations are ... 👉 Read | Docs | @mql5dev

High-volatility trading exposes a gap in accessibility: no standard hands-free, low-latency input path for MQL5 tools that wo
High-volatility trading exposes a gap in accessibility: no standard hands-free, low-latency input path for MQL5 tools that works under motor impairments and market stress. Mouse, keyboard macros, hotkeys, and voice pipelines add delay or fail in noisy environments. A gesture-controlled system is presented using a webcam with MediaPipe Hands and OpenCV in Python, sending gesture codes to MetaTrader via MQL5 Global Variables. An EA polls every 10 ms and executes via CTrade, using a busy-flag and neutral reset to avoid repeated orders. Benchmarks on an i7-1165G7 laptop (30 FPS, 640×480, confidence 0.7) show mean end-to-end latency and accuracy over 100 runs: Buy (index) 68 ms, 97.2%; Sell (thumbs-up) 72 ms, 96.8%; Close-all (fist) 85 ms, 95.4%. 95th percentile stays within 110 ms. 👉 Read | CodeBase | @mql5dev

AFML-style microstructure features are ported from Python to MetaTrader 5 as a single include file, CMicrostructureFeatures.m
AFML-style microstructure features are ported from Python to MetaTrader 5 as a single include file, CMicrostructureFeatures.mqh, so EAs can compute seven bar-level signals directly from OHLCV without external dependencies. It implements Roll spread/impact, Corwin–Schultz spread and intraday volatility, plus Kyle, Amihud, and Hasbrouck lambdas. A key constraint is MT5 “tick volume”: it counts price updates, not trades. Lambda estimators therefore use a bar-close tick rule and tick volume as approximations, making them best for regime ranking rather than broker-comparable impact levels. Roll and Corwin–Schultz remain volume-free and robust. The design emphasizes single-pass running sums (no temp arrays), strict new-bar execution to avoid look-ahead, and clean accessors for EA/ONNX pipelines. A companion MicrostructureViewer indicator plots all features wi... 👉 Read | VPS | @mql5dev

An Expert Advisor is available as a research implementation of the Inside Bar continuation hypothesis. The setup requires a t
An Expert Advisor is available as a research implementation of the Inside Bar continuation hypothesis. The setup requires a two-candle pattern: a Main Bar and a Signal Bar fully contained within the Main Bar range. On a bullish Main Bar close, a Buy Stop is placed above the Main Bar high; on a bearish close, a Sell Stop is placed below the Main Bar low. Risk controls use Stop Loss as a fraction of Main Bar range and Take Profit via a configurable Risk/Reward ratio, with TP optional. Position sizing supports fixed lots or percent risk from the starting balance captured at EA launch. Filters include an optional ATR condition requiring Main Bar size to exceed a multiple of recent volatility, plus constraints on Main Bar body and maximum Inside Bar size. Logic runs on new bars only, with one open position and one pending order per symbol, and automatic pending ... 👉 Read | Calendar | @mql5dev

Multivariate market series now routinely exceed what ARIMA/SARIMA can handle under non-stationarity, regime shifts, and micro
Multivariate market series now routinely exceed what ARIMA/SARIMA can handle under non-stationarity, regime shifts, and microstructure noise. RNNs improve sequence handling, while LSTM/GRU extend context but remain sensitive to feature quality and may miss decisive short-term spikes. Attention improves long-range dependency capture by reweighting relevant features and time steps, yet can still underreact to fast shocks. DA-CG-LSTM addresses this with dual-stage attention plus a Conversion-Gated LSTM that modifies input/forget gate activations to reduce saturation and improve responsiveness. Implementation notes in MQL5/OpenCL: split CG-LSTM into (1) linear pre-activation generation and (2) a kernel applying custom activations and state updates. Use float4 loads for bandwidth efficiency. Backprop recomputes required intermediates from pre-activations to avoid extr... 👉 Read | AppStore | @mql5dev