ch
Feedback

不要被骗子欺骗!Telemetrio 会找到并标记这些频道 👉 如果想查看标记,请订阅

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) 英语 语言赛道中的 是活跃参与者。目前社区聚集了 582 642 名订阅者,在 技术与应用 类别中位列第 143,并在 英国 地区排名第 5 位。

📊 受众指标与增长动态

自 невідомо 创建以来,项目保持高速增长,吸引了 582 642 名订阅者。

根据 17 十一月, 2026 的最新数据,频道保持稳定运转。过去 30 天订阅人数变化为 10 285,过去 24 小时变化为 674,整体触达仍然可观。

  • 认证状态: 未认证
  • 互动率 (ER): 平均受众互动率为 1.87%。内容发布后 24 小时内通常能获得 1.29% 的反应,占订阅者总量。
  • 帖子覆盖: 每篇帖子平均可获得 10 871 次浏览,首日通常累积 7 486 次浏览。
  • 互动与反馈: 受众积极参与,单帖平均反应数为 39。
  • 主题关注点: 内容集中在 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.”

凭借高频更新(最新数据采集于 18 十一月, 2026),频道始终保持新鲜度与高覆盖。分析显示受众积极互动,使其成为 技术与应用 类别中的关键影响点。

582 642
订阅者
+67424 小时
+2 4167 天
+10 28530 天
帖子存档
Perceptron training can fail on raw-value datasets when feature magnitude shifts outside expected ranges. With gradient-based
Perceptron training can fail on raw-value datasets when feature magnitude shifts outside expected ranges. With gradient-based updates and small random initialization, large scales can inflate early error and prevent convergence, even when distribution shape is unchanged. Rescaling to a bounded interval (for example, 0..1) keeps gradients numerically stable and can reduce training bias caused by disproportionate feature ranges. This becomes critical as input dimensionality grows. Two scale types are typically applied: arithmetic (linear mapping) and logarithmic (nonlinear, nonnegative domains). A practical implementation is to scan min/max in the training array, compute a scale factor, and transform values before training, without changing model code. 👉 Read | NeuroBook | @mql5dev
18 11月, 00:09

Проблема стандартных ZigZag и фракталов на M5 заключается в шуме и жестких порогах: либо появляется избыток волн, либо пропус
Проблема стандартных ZigZag и фракталов на M5 заключается в шуме и жестких порогах: либо появляется избыток волн, либо пропускаются развороты из-за фильтра по размеру. Индикатор формирует структуру по логике ручной разметки. Разворот фиксируется по старшему таймфрейму: используется H1‑фрактал из трех свечей, а точка ставится на ту M5‑свечу внутри часа, где был фактический максимум или минимум. Волна не может пройти мимо экстремума: если между точками цена ушла дальше, конец волны переносится на новый экстремум. Последняя точка сопровождает цену до подтверждения встречным фракталом. Если H1‑фрактала нет, но откат не меньше 0,5 ATR(H1), добавляется недостающая пара точек. Порогов в пунктах нет, подход одинаков для валют, металлов и индексов. Сплошные линии показывают подтвержденные волны без перерисовки. HH/HL означают рост, LH/LL — снижение. Справа ри... 👉 Read | NeuroBook | @mql5dev
18 11月, 00:00

A Wolfe Wave indicator can be used to flag potential trend reversals and is typically applied on H4 or daily charts. Signal f
A Wolfe Wave indicator can be used to flag potential trend reversals and is typically applied on H4 or daily charts. Signal frequency depends on pattern sizing controls, including the candle-count threshold used to qualify bars as swings. Higher values produce larger formations and fewer detections. Wave filtering can be tightened with a minimum ATR wave size. A value of 0 disables filtering, while 1 requires each leg to be at least 1 ATR. ATR period defines the lookback for the ATR calculation and is only relevant when the minimum ATR filter is enabled. Historical depth is controlled via the “candles from history to analyze” setting. Rule toggles commonly include bullish-only, bearish-only, or both. Clean Pattern (Bulkowski) rejects formations with intermediate peaks/troughs outside the structure. Time symmetry requires similar wave durations, with... 👉 Read | Signals | @mql5dev
17 11月, 22:09

Reference levels remain a common tool for breakout and rejection logic, especially around the prior day, prior week, and the
Reference levels remain a common tool for breakout and rejection logic, especially around the prior day, prior week, and the current session open. A lightweight indicator can standardize these levels across any chart timeframe using fixed daily and weekly data. The plot set includes PDH/PDL (previous day high/low), PWH/PWL (previous week high/low), and today’s open. Each level is drawn as a line with a compact label showing the name and exact price, positioned just to the right of the latest candle. Levels are sourced from the symbol’s D1 and W1 bars, meaning the “day” follows the broker server session. Values refresh only when a new D1 bar starts and rely on completed days and weeks, preventing intra-day repainting. If D1/W1 history is not yet available, rendering is deferred until data arrives, and all objects are cleared on removal. Key inputs co... 👉 Read | AppStore | @mql5dev
17 11月, 20:09

Trading sessions are rendered as rectangles from the configured start to end time, spanning the highest high and lowest low p
Trading sessions are rendered as rectangles from the configured start to end time, spanning the highest high and lowest low printed within that window. Labels are optional and can show the session name, with the high above the box and the low below it. New York labels are placed inside the box due to overlap with London. Hours are defined in broker server time, not local time or GMT. Defaults target a GMT+2/GMT+3 server with US daylight saving: Tokyo 02–11, London 10–19, New York 15–24. For other brokers, read Market Watch server time and offset accordingly. Sessions can cross midnight by setting an end hour lower than the start hour. Boxes are drawn only on M1–H1. H4 and higher are skipped due to bar alignment issues. Weekends and holidays are ignored in the “Days to show” count. Past boxes never repaint, and all objects are removed when the indicat... 👉 Read | AppStore | @mql5dev
17 11月, 18:09

A compact chart-corner text block provides three live lines: bar close countdown, current spread in points (ask minus bid), a
A compact chart-corner text block provides three live lines: bar close countdown, current spread in points (ask minus bid), and time remaining to server 00:00 rollover. The bar countdown shifts color during the final 10% of the candle. The rollover line appends “(x3)” on triple-swap days for the symbol. Updates run on a 1-second timer, so values keep moving between ticks and on low-liquidity instruments. If no tick arrives for over 5 minutes, the bar line switches to showing the last tick timestamp instead of a countdown. Timing notes: MT5 relies on the terminal’s server clock estimate. MT4 derives server time from the last tick and advances it using the local clock, so values may be off until the first fresh tick after loading. Rollover is typically at server midnight, but broker schedules vary. The indicator draws text labels only and cleans them up... 👉 Read | NeuroBook | @mql5dev
17 11月, 16:09

Spread and Swap Monitor surfaces symbol trading costs directly on the chart, targeting spread spikes on XAUUSD, oil, and majo
Spread and Swap Monitor surfaces symbol trading costs directly on the chart, targeting spread spikes on XAUUSD, oil, and major FX pairs around news, rollover, and low-liquidity sessions, plus overnight swap impact. A separate window plots per-bar spread as a histogram in points with a configurable moving average (50 bars default). Wide-spread bars are flagged when exceeding a multiple of the average (2x default) or an optional fixed-point threshold. Spread sourcing supports Auto, bar-history only, or tick-history only. Auto uses broker per-bar spread when available, otherwise rebuilds the widest bid/ask spread per bar from tick data (last 500 bars default). The current bar tracks the widest live spread seen so far. An on-chart panel shows live spread in points and price, average spread, today’s tightest/widest live spread since load, swap long/short w... 👉 Read | Calendar | @mql5dev
17 11月, 14:09

ATR Risk Planner standardizes pre-trade planning around ATR-based volatility. Stop distance is calculated as ATR multiplied b
ATR Risk Planner standardizes pre-trade planning around ATR-based volatility. Stop distance is calculated as ATR multiplied by a configurable factor, with targets shown as R multiples (1R, 2R, 3R). Position sizing uses broker tick size and tick value for loss, enabling consistent sizing across FX, metals, energy, and indices without manual pip-value calculations. The panel reports ATR in price and points on the current or selected timeframe, spread in points and as a percentage of the stop with a warning threshold, and risk as percent of balance, percent of equity, or a fixed currency amount. Lot size is rounded down to the broker volume step and the resulting SL loss is displayed; if minimum volume exceeds allowed risk, it is flagged. Buy and sell plans are computed separately (ask vs bid) and optional chart lines mark entry, stop, and up to three target... 👉 Read | Calendar | @mql5dev
17 11月, 12:09

Session Ranges + ADR Panel consolidates key intraday context: session highs/lows for Asia, London, and New York, current-day
Session Ranges + ADR Panel consolidates key intraday context: session highs/lows for Asia, London, and New York, current-day movement versus Average Daily Range, remaining time on the active candle, and live spread. Session boxes include high, low, and range labels, with overlap visibility and a distinct London/New York overlap color. High/low calculations are sourced from a lower timeframe (default M5) for precision on M1–H1 charts, with optional hiding above a chosen timeframe. Sessions can cross midnight, and completed session boxes remain fixed with no repainting; only the active session expands as new extremes print. The ADR panel tracks the last N completed days, today’s range, % of ADR with 70%/100% thresholds, and ADR remaining. Updates run every second, even without ticks. Units support pips, points, or raw price with auto pip sizing and optional... 👉 Read | VPS | @mql5dev
17 11月, 08:07

Trading sessions are rendered as rectangles from configured start to end hours, spanning the highest high and lowest low prin
Trading sessions are rendered as rectangles from configured start to end hours, spanning the highest high and lowest low printed within each session. Labels can be enabled to show the session name plus its high above the box and low below it; New York labels sit inside the box due to overlap with London. Sessions in progress expand as new highs or lows are formed. Hours are defined in broker server time (whole hours), not local time or GMT. Defaults target common GMT+2/GMT+3 servers with US DST: Tokyo 02–11, London 10–19, New York 15–24 (server time). Sessions may cross midnight by setting an end hour lower than the start. Rendering is limited to M1–H1; H4+ is skipped. Non-trading days are ignored, historical boxes do not repaint, and all chart objects are removed on indicator unload. Optional fill draws behind candles; otherwise outlines are used. 👉 Read | VPS | @mql5dev
17 11月, 02:02

Time-based OHLC appeared as a storage and reporting compromise when trades were sparse. As activity grew, bars and candlestic
Time-based OHLC appeared as a storage and reporting compromise when trades were sparse. As activity grew, bars and candlesticks added High/Low while keeping data volume manageable, scaling cleanly across timeframes. In signal processing, Nyquist-Shannon shows that undersampling a periodic signal destroys frequency and amplitude information. Similar loss can occur when market data is sampled by clock time instead of event intensity. Exchange pricing is discrete by tick and lot, but price is not driven by time. It reacts to trades, order book updates, and participant repricing. Fixed time bars therefore bundle a variable number of market events, making volatility and pattern statistics non-stationary across instruments and across years with different microstructure and algo participation. 👉 Read | Signals | @mql5dev
16 11月, 02:00

G7 Account Inspector Pro is an on-chart account diagnostics and risk auditing dashboard for MetaTrader 5. It targets prop fir
G7 Account Inspector Pro is an on-chart account diagnostics and risk auditing dashboard for MetaTrader 5. It targets prop firm evaluation workflows, EA-driven trading, and discretionary portfolio monitoring with real-time performance and exposure metrics. The interface toggles between a compact HUD and a full multi-column panel. It also calculates an account health score (0–100) based on core factors such as profit factor, max drawdown, win rate, and return-to-risk, with letter-grade output. Behavioral metrics cover execution mix (EA vs manual via magic number), grid-style exposure, scalping turnover, lot sizing variance, and overnight/weekend holding. A compliance auditor tracks daily and total drawdown against configurable limits, with CSV export for historical reviews. Key inputs include initial panel state, chart anchoring and offsets, daily/tot... 👉 Read | AppStore | @mql5dev
16 11月, 00:00

This article tackles a common MT5 usability problem: users delete a chart object created by an indicator, and earlier impleme
This article tackles a common MT5 usability problem: users delete a chart object created by an indicator, and earlier implementations removed the entire program. The proposed approach keeps the indicator running and automatically recreates the missing object. It starts with a minimal fix: listen for object-deletion events and rebuild the object. Testing reveals subtle issues: repeated pointer initialization can leak memory, and OnDeinit can accidentally trigger recreation via queued events. The corrected version guards pointer reuse and disables event handling during shutdown. A more practical refinement stores key object state (position and size) inside the object-managing class. When deletion is detected, the indicator restores the object using saved properties, balancing effort against fidelity. 👉 Read | Calendar | @mql5dev
15 11月, 08:00

G7 FVG OB Confluence AutoTrader is an MT5 algorithmic trading utility built around strict OB/FVG overlap validation. Trade si
G7 FVG OB Confluence AutoTrader is an MT5 algorithmic trading utility built around strict OB/FVG overlap validation. Trade signals are only considered when an institutional Order Block and an unmitigated 3-bar Fair Value Gap coincide at the same price structure, with configurable overlap tolerance. The engine scans M15 order blocks via impulse displacement (>1.6x ATR) and tracks active imbalances. A 6-factor on-chart score (0–100%) aggregates NY-session USD news filtering, DXY correlation alignment, imbalance status, liquidity sweep detection, order block state, and an overall weighted confidence with score capping on structural conflicts. Execution is handled from a chart HUD with one-click buy/sell, lot sizing, SL/TP edits, auto-exec toggling, breakeven-all, and close-all. Risk controls include daily loss shutdown, daily profit lock, spread filt... 👉 Read | Quotes | @mql5dev
15 11月, 06:00

Smart Money Concepts workflows often require monitoring several timeframes and maintaining consistent zone markup. G7 Institu
Smart Money Concepts workflows often require monitoring several timeframes and maintaining consistent zone markup. G7 Institutional SMC Radar is an MT5 indicator focused on XAUUSD scalping and prop-firm style execution, providing automated zone detection and a confluence-style confidence readout for manual decisions. The tool auto-draws bullish/bearish Fair Value Gaps and ICT Order Blocks, extends them forward, and removes zones after mitigation to reduce chart clutter. A heads-up display outputs a 0–100 confidence score based on structural alignment between detected zones. A background DXY correlation module is included to help validate directional bias. Recommended attachment is M15 or H1, then waiting for higher confidence readings (for example, 70%+) before executing manual entries. The package is positioned as an analytical dashboard rather than an a... 👉 Read | Freelance | @mql5dev
15 11月, 04:00

An MLP gate can be trained directly inside an MQL5 Expert Advisor to avoid the Python export workflow and its operational fai
An MLP gate can be trained directly inside an MQL5 Expert Advisor to avoid the Python export workflow and its operational failures: scaler mismatches, feature drift, missing weight files, and tester discrepancies. The design targets a compact 2-class MLP (ReLU + softmax) retrained every N bars on the current symbol/timeframe, using only closed-bar inference (shift=1). Behavior when untrained is controlled via InpMlpFailOpen. Integration keeps the existing pipeline intact: RSI divergence generates direction, HTF filter validates context, and the MLP acts as the final accept/reject step based on P(up)−P(down) exceeding InpMlpThreshold for the candidate direction. Features are local (RSI, ATR, EMA(50), session sin/cos), with labels built from forward movement over InpMlpHorizon without live-edge leakage. Trade-offs: CPU cost in tester/optimizer, seed determi... 👉 Read | Docs | @mql5dev
15 11月, 02:02

G7 Pro Trade Manager & Prop Firm Equity Protector is an on-chart trade management utility for manual trading on MetaTrader 5,
G7 Pro Trade Manager & Prop Firm Equity Protector is an on-chart trade management utility for manual trading on MetaTrader 5, focused on fast execution and rule-based risk controls. The interface runs directly on the chart and supports scalping and funded-account workflows. Core functions include one-click BUY/SELL with pre-set SL/TP in pips and an on-chart lot sizer. Automated management covers breakeven moves after a configurable profit threshold, plus trailing stops that activate and follow price by defined distances. For prop-firm style limits, a daily drawdown circuit breaker tracks the day’s starting balance versus live equity. When the configured loss threshold is hit, positions can be force-closed and trading locked until the next day. Emergency actions include breakeven-all, partial close, close-profit only, and close-all. Configuration supports symbol... 👉 Read | Docs | @mql5dev
15 11月, 02:00

Chimp Optimization Algorithm (ChOA) extends GWO by using four leaders (attacker, barrier, chaser, driver) and updating each a
Chimp Optimization Algorithm (ChOA) extends GWO by using four leaders (attacker, barrier, chaser, driver) and updating each agent from all four simultaneously. A “social motivation” term adds optional chaotic jumps, but this component is often harmful in continuous search. A continuous BChimp implementation reuses the ChOA core and focuses on coefficient dynamics. The published binary variant can hide issues because sigmoid thresholding collapses scale and sign. A key defect is bias in A: using Ak = f(2*c1gk*rand - 1) yields E[Ak] = f(c1gk - 1), creating systematic drift toward bounds and diagonal motion. Fixing this with Ak = f*c1gk*(2*rand - 1) restores zero-mean steps and stable convergence. The tested setup keeps four-leader elitism, resamples coefficients per coordinate, and drops chaotic replacement for continuous benchmarks. 👉 Read | AppStore | @mql5dev
15 11月, 00:02

Order block detection for XAUUSD and any symbol: the zone is defined as the last opposite candle before a structure break. La
Order block detection for XAUUSD and any symbol: the zone is defined as the last opposite candle before a structure break. Last bearish candle before a close above a confirmed swing high, or last bullish candle before a close below a confirmed swing low. The zone can be drawn as full range (high to low) or body only. Leg validation uses an impulse filter: at least one candle body in the leg must exceed a configurable ATR multiple (default ATR 14, multiplier 1.0). This reduces zones created by slow drift. Swings are confirmed only after bars on both sides close, so zones appear with a delay and do not repaint. Zone lifecycle: fresh zones are highlighted, tested zones are dimmed on first return, and zones are removed when a candle closes through them. History scan defaults to 1500 bars, with limits for maximum live bullish/bearish zones and optional re... 👉 Read | NeuroBook | @mql5dev
15 11月, 00:00

Most MQL5 monitoring ends at terminal logs and Strategy Tester reports. Once an EA depends on external services, correlating
Most MQL5 monitoring ends at terminal logs and Strategy Tester reports. Once an EA depends on external services, correlating decisions and latency across processes becomes manual and unreliable. A native OpenTelemetry OTLP tracer for MQL5 is implemented as a client-only design. It generates W3C trace IDs/span IDs, produces nanosecond-formatted timestamps, and exports OTLP/HTTP JSON via WebRequest(), with no gRPC or protobuf dependency. Instrumentation is layered: core clock/IDs/sampler, tracer with span stack and RAII scope guard, and an exporter with a bounded ring queue plus retry/backoff. OnTimer() performs blocking WebRequest() calls; spans enqueue without blocking, overwriting the oldest on overflow. An EMA-cross EA and a Python scoring service share trace context via the traceparent header, allowing Jaeger to render one end-to-end timeline per b... 👉 Read | AppStore | @mql5dev
14 11月, 22:02