A PPO-based RL trading pipeline tested a behavioural-cloning loop that re-trains the policy from its own live demo trades. Over two months, models produced under heavier cloning degraded and shifted toward inaction, including cases where they stopped trading entirely.
Live decisions were logged as (observation, action) with outcome metadata. Cloning applied weighted cross-entropy after each rollout plus a two-epoch pre-training pass for final models. Weights came from trade R-multiples, spread across all steps in a trade.
Two failures surfaced. A feature-schema change invalidated most buffered episodes without purge. More materially, after usable episodes appeared, final-model evaluation showed higher Hold shares, far fewer Buy/Sell actions, more negative Sharpes, and 12 models that never traded. Trials using only the light callback did not show the same s...
👉 Read | Docs | @mql5dev
Live decisions were logged as (observation, action) with outcome metadata. Cloning applied weighted cross-entropy after each rollout plus a two-epoch pre-training pass for final models. Weights came from trade R-multiples, spread across all steps in a trade.
Two failures surfaced. A feature-schema change invalidated most buffered episodes without purge. More materially, after usable episodes appeared, final-model evaluation showed higher Hold shares, far fewer Buy/Sell actions, more negative Sharpes, and 12 models that never traded. Trials using only the light callback did not show the same s...
👉 Read | Docs | @mql5dev
👍26🔥25🤩19❤12
Classic volatility indicators (EWMA, ATR, GARCH) collapse price action into squared returns, so a steady selloff and a noisy range can look identical. This article implements the Guyon–Lekeufack path-dependent volatility model in MQL5, explicitly retaining direction.
The model predicts volatility from two streaming features: a trend term (kernel-weighted signed returns) and an activity term (kernel-weighted squared returns). Both use a two-timescale exponential mixture (fast/slow half-lives). The per-bar update is O(1): four accumulators, cached decays, no lookback arrays or matrix work.
Calibration splits the problem: a simplex searches six kernel parameters while linear regression solves the three coefficients exactly, with leakage-safe, chronological out-of-sample testing against EWMA and GARCH(1,1). Results show the trend component materially impr...
👉 Read | Docs | @mql5dev
The model predicts volatility from two streaming features: a trend term (kernel-weighted signed returns) and an activity term (kernel-weighted squared returns). Both use a two-timescale exponential mixture (fast/slow half-lives). The per-bar update is O(1): four accumulators, cached decays, no lookback arrays or matrix work.
Calibration splits the problem: a simplex searches six kernel parameters while linear regression solves the three coefficients exactly, with leakage-safe, chronological out-of-sample testing against EWMA and GARCH(1,1). Results show the trend component materially impr...
👉 Read | Docs | @mql5dev
❤85👍29🤩27🔥23👨💻4🏆2👀1
Educational example of a trend-following Expert Advisor in MQL5, focused on structure and runtime safety. Signals are generated on closed bars and evaluated only once per new bar: BUY when fast MA crosses above slow MA (bar 2: fast ≤ slow, bar 1: fast > slow), SELL on the inverse. The EA waits for the first new crossover after startup, maintains a single position, and reverses on an opposite signal.
Order logic includes free margin validation via OrderCalcMargin, lot normalization to symbol min/max/step, and SL/TP adjustment to SYMBOL_TRADE_STOPS_LEVEL. Execution applies a spread filter, slippage limit, and retries on requotes or price changes, but only until the signal bar ends. Indicator handles are released in OnDeinit, with English/Polish messages based on terminal language.
Runs only in Strategy Tester and on demo; live trading is blocked. Provided “as...
👉 Read | CodeBase | @mql5dev
Order logic includes free margin validation via OrderCalcMargin, lot normalization to symbol min/max/step, and SL/TP adjustment to SYMBOL_TRADE_STOPS_LEVEL. Execution applies a spread filter, slippage limit, and retries on requotes or price changes, but only until the signal bar ends. Indicator handles are released in OnDeinit, with English/Polish messages based on terminal language.
Runs only in Strategy Tester and on demo; live trading is blocked. Provided “as...
👉 Read | CodeBase | @mql5dev
❤21🤩7👍4🔥2😁2✍1🎉1
Educational example of a trend-following Expert Advisor in MQL5, focused on structure and runtime safety. Signals are generated on closed bars and evaluated only once per new bar: BUY when fast MA crosses above slow MA (bar 2: fast ≤ slow, bar 1: fast > slow), SELL on the inverse. The EA waits for the first new crossover after startup, maintains a single position, and reverses on an opposite signal.
Order logic includes free margin validation via OrderCalcMargin, lot normalization to symbol min/max/step, and SL/TP adjustment to SYMBOL_TRADE_STOPS_LEVEL. Execution applies a spread filter, slippage limit, and retries on requotes or price changes, but only until the signal bar ends. Indicator handles are released in OnDeinit, with English/Polish messages based on terminal language.
Runs only in Strategy Tester and on demo; live trading is blocked. Provided “as...
👉 Read | Docs | @mql5dev
Order logic includes free margin validation via OrderCalcMargin, lot normalization to symbol min/max/step, and SL/TP adjustment to SYMBOL_TRADE_STOPS_LEVEL. Execution applies a spread filter, slippage limit, and retries on requotes or price changes, but only until the signal bar ends. Indicator handles are released in OnDeinit, with English/Polish messages based on terminal language.
Runs only in Strategy Tester and on demo; live trading is blocked. Provided “as...
👉 Read | Docs | @mql5dev
❤21👍9🤩5🔥4😐2✍1
Educational mean-reversion Expert Advisor built around Bollinger Bands, with an optional RSI filter. Entry logic uses two completed bars: BUY when bar 2 closes below the lower band and bar 1 returns inside the bands (optional RSI on bar 2 below 30). SELL mirrors this using the upper band (optional RSI above 70).
Exits trigger on a touch of the current middle band (BUY: Bid ≥ middle, SELL: Ask ≤ middle) or Stop Loss. Trading hours restrict only new entries, including overnight windows such as 22:00–06:00; closing always remains active. An option is provided to force closing outside the time window. Max concurrent positions is configurable.
Implementation details include indicator handles with CopyBuffer validation, switchable filters, server-time windows crossing midnight, free margin/lot/stop-level checks, spread filtering, and order retry logic. Demo and S...
👉 Read | VPS | @mql5dev
Exits trigger on a touch of the current middle band (BUY: Bid ≥ middle, SELL: Ask ≤ middle) or Stop Loss. Trading hours restrict only new entries, including overnight windows such as 22:00–06:00; closing always remains active. An option is provided to force closing outside the time window. Max concurrent positions is configurable.
Implementation details include indicator handles with CopyBuffer validation, switchable filters, server-time windows crossing midnight, free margin/lot/stop-level checks, spread filtering, and order retry logic. Demo and S...
👉 Read | VPS | @mql5dev
❤23🤩13👍11🔥9🏆2😁1😐1
Educational breakout Expert Advisor using pending orders and a daily range built from M1 bars. After the configured range window (for example 00:00–07:00 server time), the EA calculates High/Low and places one set of orders per day: BuyStop above High with spread/shift, and SellStop below Low with shift. SL is set beyond the opposite side of the range, while TP is computed via a configurable risk/reward ratio.
On fill, the opposite pending order is deleted. Unfilled orders are removed at a cancel time, and an open position can be closed at a specified time. Breakout sides are skipped when price is already beyond the trigger level, and ranges outside min/max width are ignored. After terminal restart, order history is used to restore state and prevent duplicate daily placement.
The code demonstrates CTrade BuyStop/SellStop, broker distance adjustments for SL/...
👉 Read | Forum | @mql5dev
On fill, the opposite pending order is deleted. Unfilled orders are removed at a cancel time, and an open position can be closed at a specified time. Breakout sides are skipped when price is already beyond the trigger level, and ranges outside min/max width are ignored. After terminal restart, order history is used to restore state and prevent duplicate daily placement.
The code demonstrates CTrade BuyStop/SellStop, broker distance adjustments for SL/...
👉 Read | Forum | @mql5dev
🔥20👍16❤15🤩5🤣3😁2🏆1
Spread Monitor is a single-file MQL5 Expert Advisor that displays the current spread for the attached symbol in a chart-corner panel with color status.
The EA reads SYMBOL_SPREAD (points) on a throttled, user-defined interval and stores samples in a fixed-size rolling buffer. From this in-memory history it recalculates current, average, minimum, and maximum spread, and counts how many samples exceed a configurable warning level to quantify how often spreads are elevated.
The status row switches to red when the current spread is above the warning threshold and green otherwise. History resets when the EA is removed, the symbol changes, or the terminal restarts. Panel objects use a fixed name prefix, enabling clean removal on exit without touching unrelated chart objects.
No orders are placed, modified, or closed, and trading by other programs is not blocked. I...
👉 Read | Docs | @mql5dev
The EA reads SYMBOL_SPREAD (points) on a throttled, user-defined interval and stores samples in a fixed-size rolling buffer. From this in-memory history it recalculates current, average, minimum, and maximum spread, and counts how many samples exceed a configurable warning level to quantify how often spreads are elevated.
The status row switches to red when the current spread is above the warning threshold and green otherwise. History resets when the EA is removed, the symbol changes, or the terminal restarts. Panel objects use a fixed name prefix, enabling clean removal on exit without touching unrelated chart objects.
No orders are placed, modified, or closed, and trading by other programs is not blocked. I...
👉 Read | Docs | @mql5dev
👍22❤19🔥11🤩9🤣2
PropGuard Lite is a risk guard for prop firm accounts (FTMO-style rules) and any MT5 setup that needs enforced loss limits. It never opens trades on live or demo charts; it monitors equity including floating P/L and acts only on risk events.
When a limit is hit, it closes positions (all or one magic number), oldest first, deletes pending orders, and keeps closing anything reopened by other EAs. Daily halts clear on the next trading day; max-loss halts persist until manually reset.
Daily loss can be based on initial capital or a day-start reference (balance or higher of balance/equity). Max loss is a percent of initial capital. A buffer triggers slightly early to allow for slippage. Day boundaries use a configurable reset hour and time zone offset.
State is restart-safe: references are rebuilt from deal history, halts are stored in terminal globals. Include...
👉 Read | Signals | @mql5dev
When a limit is hit, it closes positions (all or one magic number), oldest first, deletes pending orders, and keeps closing anything reopened by other EAs. Daily halts clear on the next trading day; max-loss halts persist until manually reset.
Daily loss can be based on initial capital or a day-start reference (balance or higher of balance/equity). Max loss is a percent of initial capital. A buffer triggers slightly early to allow for slippage. Day boundaries use a configurable reset hour and time zone offset.
State is restart-safe: references are rebuilt from deal history, halts are stored in terminal globals. Include...
👉 Read | Signals | @mql5dev
🔥10❤9👍9🤩9
AccountGuard provides a single-header account lock for MT5 Expert Advisors, controlled via compile-time #define settings and embedded into the .ex5. Licensed accounts can be listed as login-only or server:login pairs, with flexible separators. Optional switches allow any demo account, a fixed expiry timestamp, and a Strategy Tester bypass for backtesting.
Integration uses AG_Init() in OnInit() and AG_Allowed() as a gate before any new orders, while existing exits and trailing logic continue to run. AG_Reason() supplies a concise lock message for panels or logs. Runtime inputs include a custom alert message and an internal self-test covering 32 scenarios.
Default behavior is fail-closed: empty lists, typos, expiry, or missing account data result in LOCKED, with automatic rechecks. Expiry uses server-derived time to reduce clock rollback abuse. No DLLs, WebReq...
👉 Read | Docs | @mql5dev
Integration uses AG_Init() in OnInit() and AG_Allowed() as a gate before any new orders, while existing exits and trailing logic continue to run. AG_Reason() supplies a concise lock message for panels or logs. Runtime inputs include a custom alert message and an internal self-test covering 32 scenarios.
Default behavior is fail-closed: empty lists, typos, expiry, or missing account data result in LOCKED, with automatic rechecks. Expiry uses server-derived time to reduce clock rollback abuse. No DLLs, WebReq...
👉 Read | Docs | @mql5dev
❤13👍10🤩8🔥3👏1
Strategy Tester does not cover live-chart conditions such as terminal restarts, EAs starting before account connect, multiple chart instances, server-side history changes, or chart button clicks. A demo-account bench is provided to validate these scenarios and emit a PASS/FAIL report.
LiveTestDriver.mq5 reads phase A/B/C from MQL5\Files\LiveTestBench\phase.txt, runs phase checks, then exits via TerminalClose(). Execution is blocked on non-demo accounts. ExampleDailyLock.mq5 is the EA under test, using global variables for persistence, enforcing one instance per account via GlobalVariableSetOnCondition, and exposing an Unlock button. ExampleDailyLock_DemoTest.mq5 builds a demo-only variant using DEMO_ONLY without modifying the EA source. run_live_test.ps1 writes startup config, launches a portable terminal per phase, and prints results.
Phase A validates start...
👉 Read | Freelance | @mql5dev
LiveTestDriver.mq5 reads phase A/B/C from MQL5\Files\LiveTestBench\phase.txt, runs phase checks, then exits via TerminalClose(). Execution is blocked on non-demo accounts. ExampleDailyLock.mq5 is the EA under test, using global variables for persistence, enforcing one instance per account via GlobalVariableSetOnCondition, and exposing an Unlock button. ExampleDailyLock_DemoTest.mq5 builds a demo-only variant using DEMO_ONLY without modifying the EA source. run_live_test.ps1 writes startup config, launches a portable terminal per phase, and prints results.
Phase A validates start...
👉 Read | Freelance | @mql5dev
❤12👍10⚡2🔥2🤩2👨💻1
TesterReport.mqh parses Strategy Tester reports saved as HTML (Backtest tab -> Report -> HTML) and exposes deals, reconstructed closed trades, and key summary figures for post-processing in MQL5. Typical uses include report comparison, portfolio aggregation, CSV export, and validation against account history.
Parsed settings include EA name, timeframe, currency, and initial deposit. Each Deals row is mapped to SReportDeal with time, ticket, symbol, type/direction, volume, price, commission, swap, profit, balance, and comment.
Closed trades (SReportTrade) are rebuilt because the HTML report has no position IDs. Each exit is matched against the oldest open entry on the same symbol with the opposite side. Partial closes and reversals generate multiple trades; entry commission is allocated pro-rata by closed volume. NetProfit() and balance drawdowns are com...
👉 Read | AppStore | @mql5dev
Parsed settings include EA name, timeframe, currency, and initial deposit. Each Deals row is mapped to SReportDeal with time, ticket, symbol, type/direction, volume, price, commission, swap, profit, balance, and comment.
Closed trades (SReportTrade) are rebuilt because the HTML report has no position IDs. Each exit is matched against the oldest open entry on the same symbol with the opposite side. Partial closes and reversals generate multiple trades; entry commission is allocated pro-rata by closed volume. NetProfit() and balance drawdowns are com...
👉 Read | AppStore | @mql5dev
👍9❤7🔥2🤩2
A chart-side risk panel calculates position size before any order is sent, with explicit handling of broker volume rules.
For the active symbol it shows spread in points and the spread cost per 1.00 lot, plus point value per 1.00 lot derived from tick value and tick size for correct pricing on metals, indices, and non-USD crosses. It also prints the broker’s min/step/max volume.
Risk can be set as % of balance, % of equity, or fixed account-currency amount. With a stop distance in points, it computes loss per 1.00 lot, the raw lot size, the lot rounded down to the volume step, and the actual money at risk after rounding.
Edge cases are made visible: when the raw lot is below broker minimum (risk cap cannot be respected), and when step rounding shifts real risk away from the requested value, with highlighting above a 10% gap. Read-only indicator: no ...
👉 Read | NeuroBook | @mql5dev
For the active symbol it shows spread in points and the spread cost per 1.00 lot, plus point value per 1.00 lot derived from tick value and tick size for correct pricing on metals, indices, and non-USD crosses. It also prints the broker’s min/step/max volume.
Risk can be set as % of balance, % of equity, or fixed account-currency amount. With a stop distance in points, it computes loss per 1.00 lot, the raw lot size, the lot rounded down to the volume step, and the actual money at risk after rounding.
Edge cases are made visible: when the raw lot is below broker minimum (risk cap cannot be respected), and when step rounding shifts real risk away from the requested value, with highlighting above a 10% gap. Read-only indicator: no ...
👉 Read | NeuroBook | @mql5dev
❤6👍5
PortfolioWeights.mqh adds portfolio-weight computation to MQL5 using matrix/vector types and no DLL. Inputs are return series per component, including symbols or daily PnL streams from multiple Expert Advisors.
Five long-only allocations are provided: InverseVolatility, RiskParity (cyclical coordinate descent), HierarchicalRiskParity using single-linkage on distance sqrt((1-corr)/2) with order[] output, MinimumVariance with optional per-component cap, and MaximumDiversification. Risk contributions per component are also reported.
Covariance estimation includes Ledoit-Wolf shrinkage, shrinking correlations toward zero based on optimal intensity on unit-variance scaled returns, improving stability when observations are limited relative to dimension. Minimum-variance and maximum-diversification are solved via active-set QP with bounds and one equality.
...
👉 Read | NeuroBook | @mql5dev
Five long-only allocations are provided: InverseVolatility, RiskParity (cyclical coordinate descent), HierarchicalRiskParity using single-linkage on distance sqrt((1-corr)/2) with order[] output, MinimumVariance with optional per-component cap, and MaximumDiversification. Risk contributions per component are also reported.
Covariance estimation includes Ledoit-Wolf shrinkage, shrinking correlations toward zero based on optimal intensity on unit-variance scaled returns, improving stability when observations are limited relative to dimension. Minimum-variance and maximum-diversification are solved via active-set QP with bounds and one equality.
...
👉 Read | NeuroBook | @mql5dev
❤7👍5🤩1
ICT Model Tracker is a non-trading indicator that detects and measures a strict ICT setup sequence on any chart using closed bars only. It marks the liquidity sweep inside a killzone, the MSS with displacement and FVG (or iFVG), then the limit entry with SL/TP, and tracks each setup through expiry or outcome without repainting. Single file, no DLL.
A deliberately published negative baseline is included: US100.cash M5, Jan 2025 to Aug 2026, default settings averaged -0.05R per trade across 690 setups and 425 trades (profit factor 0.91), with no profitable configuration in the tested set. This is presented as model measurement rather than a coding issue, with independent replay matching events and stats.
Features include NY-time killzones with DST handling, multiple liquidity references, outcome labels (+R, -1R, EXP, MISS), and a stats panel segmented ...
👉 Read | Freelance | @mql5dev
A deliberately published negative baseline is included: US100.cash M5, Jan 2025 to Aug 2026, default settings averaged -0.05R per trade across 690 setups and 425 trades (profit factor 0.91), with no profitable configuration in the tested set. This is presented as model measurement rather than a coding issue, with independent replay matching events and stats.
Features include NY-time killzones with DST handling, multiple liquidity references, outcome labels (+R, -1R, EXP, MISS), and a stats panel segmented ...
👉 Read | Freelance | @mql5dev
👍16❤7🔥2👨💻2👀1
DrawdownBootstrap.mqh estimates prospective drawdown depth over coming months using historical daily P/L series. Instead of treating the backtest’s single time order as representative, it applies Monte Carlo reordering to quantify expected drawdown percentiles and the frequency of exceeding the historical worst.
The implementation uses stationary bootstrap (Politis/Romano, 1994): each simulated path starts at a random day, advances sequentially, and jumps to a new random day with probability 1/meanBlock. Keeping multi-day blocks preserves losing streaks and clustered losses that are lost when sampling days independently. Each path records maximum peak-to-trough decline; Quantile() returns interpolated percentiles.
A deterministic mulberry32 RNG (CSeededRandom) ensures reproducible results across machines. Daily inputs can be money P/L (fixed lots) ...
👉 Read | Calendar | @mql5dev
The implementation uses stationary bootstrap (Politis/Romano, 1994): each simulated path starts at a random day, advances sequentially, and jumps to a new random day with probability 1/meanBlock. Keeping multi-day blocks preserves losing streaks and clustered losses that are lost when sampling days independently. Each path records maximum peak-to-trough decline; Quantile() returns interpolated percentiles.
A deterministic mulberry32 RNG (CSeededRandom) ensures reproducible results across machines. Daily inputs can be money P/L (fixed lots) ...
👉 Read | Calendar | @mql5dev
❤8👍6🤩3👌1
A filter is available for detecting whether the current bar is pushing into a local extreme, based on local high/low extrema with an ATR buffer.
Breach conditions are defined as: High breach when high[i] exceeds (local high extremum minus ATR times a multiplier). Low breach when low[i] falls below (local low extremum plus ATR times a multiplier). The ATR multiplier controls tolerance around the extremum.
Two operating modes are supported. Live bar mode evaluates the active, unclosed bar in real time. Closed-bar-only mode evaluates confirmed bars only, which is typically safer for automated execution that relies on settled OHLC values.
The intended use is as a gating layer for entry indicators that do not account for local extremes and may otherwise trigger buys into local highs or sells into local lows. Visual output flags risk zones: red markers in...
👉 Read | NeuroBook | @mql5dev
Breach conditions are defined as: High breach when high[i] exceeds (local high extremum minus ATR times a multiplier). Low breach when low[i] falls below (local low extremum plus ATR times a multiplier). The ATR multiplier controls tolerance around the extremum.
Two operating modes are supported. Live bar mode evaluates the active, unclosed bar in real time. Closed-bar-only mode evaluates confirmed bars only, which is typically safer for automated execution that relies on settled OHLC values.
The intended use is as a gating layer for entry indicators that do not account for local extremes and may otherwise trigger buys into local highs or sells into local lows. Visual output flags risk zones: red markers in...
👉 Read | NeuroBook | @mql5dev
❤13👍9🤩3🔥1
BacktestOverfitting.mqh calculates the Probability of Backtest Overfitting (PBO) for an MT5 optimization. PBO measures how often the pass that ranks best in one half of the history ends up in the lower half across all passes on the other half. High PBO indicates parameter selection driven mainly by noise rather than repeatable edge.
The implementation follows combinatorially symmetric cross-validation (Bailey, Borwein, Lopez de Prado, Zhu, 2017). Daily results are emitted per pass from OnTester() as frames, then consolidated into a matrix in OnTesterDeinit() after the final pass.
History is partitioned into S equal day blocks; all S/2 vs S/2 in-sample/out-of-sample combinations are evaluated (for S=16: C(16,8)=12,870 splits). Selection uses in-sample Sharpe (or mean with PBO_MEAN), then ranks the chosen pass out of sample to form logits. Output includes PBO, los...
👉 Read | Freelance | @mql5dev
The implementation follows combinatorially symmetric cross-validation (Bailey, Borwein, Lopez de Prado, Zhu, 2017). Daily results are emitted per pass from OnTester() as frames, then consolidated into a matrix in OnTesterDeinit() after the final pass.
History is partitioned into S equal day blocks; all S/2 vs S/2 in-sample/out-of-sample combinations are evaluated (for S=16: C(16,8)=12,870 splits). Selection uses in-sample Sharpe (or mean with PBO_MEAN), then ranks the chosen pass out of sample to form logits. Output includes PBO, los...
👉 Read | Freelance | @mql5dev
❤11👍5🔥3😁2
Most “EA does not work” reports come from the trading environment, not the code: terminal AutoTrading disabled, netting vs hedging mismatch, unsupported filling mode, stops inside StopsLevel/FreezeLevel, or volume not matching step and limits.
TradeEnvCheck is a read-only script that generates a single report before installing or commissioning an EA. Run it once on a chart for the target symbol. Output goes to the Experts log, a short on-chart summary, and a text file at MQL5\Files\TradeEnvCheck_<symbol>.txt. No trading actions are performed.
The report captures account details, margin mode with hedging/netting implications, required trading permissions, and margin call/stop out levels. Per symbol it lists trade/execution/profit modes, price/contract parameters, supported filling modes (and the one to use), allowed order/expiration types, stops and freeze lev...
👉 Read | Forum | @mql5dev
TradeEnvCheck is a read-only script that generates a single report before installing or commissioning an EA. Run it once on a chart for the target symbol. Output goes to the Experts log, a short on-chart summary, and a text file at MQL5\Files\TradeEnvCheck_<symbol>.txt. No trading actions are performed.
The report captures account details, margin mode with hedging/netting implications, required trading permissions, and margin call/stop out levels. Per symbol it lists trade/execution/profit modes, price/contract parameters, supported filling modes (and the one to use), allowed order/expiration types, stops and freeze lev...
👉 Read | Forum | @mql5dev
❤12👍11🔥2🤩2
Single-layer neurons can learn linearly separable logic (AND/OR/NAND/NOR) but fail on XOR/XNOR, a concrete example of why “one neuron learns everything” is false.
The workaround borrows from digital electronics: build XOR as a small circuit composed of gates the neuron can already model. A NOR and an AND feed a second NOR, matching the XOR truth table.
In MQL5, this is implemented by storing separate weights and biases per internal gate, training only NOR and AND via finite-difference gradient updates. XOR output is then computed by composing these learned gates, effectively embedding a tiny network inside one neuron—useful for designing non-linear decision logic in trading code without expanding model complexity.
👉 Read | CodeBase | @mql5dev
The workaround borrows from digital electronics: build XOR as a small circuit composed of gates the neuron can already model. A NOR and an AND feed a second NOR, matching the XOR truth table.
In MQL5, this is implemented by storing separate weights and biases per internal gate, training only NOR and AND via finite-difference gradient updates. XOR output is then computed by composing these learned gates, effectively embedding a tiny network inside one neuron—useful for designing non-linear decision logic in trading code without expanding model complexity.
👉 Read | CodeBase | @mql5dev
👍8🤩6❤5
GapTracker scans any symbol and timeframe for opening gaps where the bar open is a configurable number of points away from the prior close. Gaps are categorized as daily (first bar of a new server day), weekend/holiday (first bar after a pause beyond a threshold, 36h default), and optionally intraday bar-to-bar.
Each gap is tracked until filled, defined as price trading back to the previous close. The gap bar counts, so same-bar closures report as 0 bars to fill, with an optional cutoff after N bars.
On-chart output uses rectangles from previous close to open, extended to the fill bar or the latest bar if still open, with size labels and configurable colors; filled gaps turn grey. Drawing is capped (200 recent gaps by default) to limit clutter, with hover tooltips for full details.
Realtime alerts support pop-up, push, and sound, while CSV logging r...
👉 Read | CodeBase | @mql5dev
Each gap is tracked until filled, defined as price trading back to the previous close. The gap bar counts, so same-bar closures report as 0 bars to fill, with an optional cutoff after N bars.
On-chart output uses rectangles from previous close to open, extended to the fill bar or the latest bar if still open, with size labels and configurable colors; filled gaps turn grey. Drawing is capped (200 recent gaps by default) to limit clutter, with hover tooltips for full details.
Realtime alerts support pop-up, push, and sound, while CSV logging r...
👉 Read | CodeBase | @mql5dev
👍8❤7🤩6🔥5✍2
This follow-up completes a doubly linked list in MQL5 built around operator overloading, moving from “push/read” basics to a safer, more usable container.
A class destructor is added to guarantee allocated nodes are released, eliminating MT5 resource warnings and enabling predictable lifetime management when lists go out of scope.
The list gains non-destructive element access: values can be read or modified by index without consuming nodes, with optional syntax that keeps call sites compact via overloaded operators.
For deletion, the implementation is refactored so a manager class owns list structure while node objects handle linkage, simplifying pointer updates. Edge-node removal initially crashes due to missing head/tail fixes, then is corrected with explicit boundary handling.
Finally, the article explores an advanced pattern: overloading subscript ...
👉 Read | AlgoBook | @mql5dev
A class destructor is added to guarantee allocated nodes are released, eliminating MT5 resource warnings and enabling predictable lifetime management when lists go out of scope.
The list gains non-destructive element access: values can be read or modified by index without consuming nodes, with optional syntax that keeps call sites compact via overloaded operators.
For deletion, the implementation is refactored so a manager class owns list structure while node objects handle linkage, simplifying pointer updates. Edge-node removal initially crashes due to missing head/tail fixes, then is corrected with explicit boundary handling.
Finally, the article explores an advanced pattern: overloading subscript ...
👉 Read | AlgoBook | @mql5dev
🔥9👍7❤3🤩3