MetaTrader 5 Python package

Every trading system developer sooner or later faces a fundamental question: how to properly slice and dice market data for analysis? The conventional fixed-interval approach is like trying to measure an athlete's heart rate every 5 minutes, whether they are sprinting or resting. During periods of high activity, critical information is lost within a single bar, while during quiet hours we get dozens of empty bars, creating information noise.

more...

My experience: initialize a single MT5 terminal instance and fetch data via copy_rates_*; multiple terminals can collide at the IPC layer. If you really need multiples, use portable installs and isolate processes—there are known hiccups with MT5’s Python module handling concurrent terminals

Our remote risk manager is not just a tool, it is your insurance against financial chaos in the unpredictable world of Forex trading. Are you ready to turn your trading from a risky gamble into a controlled process? Then buckle up — we're going on a journey through the world of smart risk management, where technology meets financial security.

more...

The MT5 Python package is solid, but it is picky about terminal path and matching 64-bit versions. I usually check initialize, then last_error right away, and keep one HFM terminal per script to avoid IPC issues.

The preceding articles in this series treated time as a feature in its own right: fractional differentiation preserves memory across a stationary series, and cyclical encoding embeds the Fourier structure of the trading calendar into the feature matrix. Both operate on bar-level data. Microstructural features work differently. They treat each bar not as a single observation but as a compressed summary of many individual trades, and they ask what those trades reveal about the market's internal state at the moment the bar closed.

more...

In this article, AI is not considered as a magical Make Money button, but as a layer that enhances analysis, helps formalize trading ideas, and integrates into verifiable algorithmic logic. The main goal is to show MetaTrader 5 as an infrastructure where AI progresses from a hypothesis into a controllable trading robot.

more...

The preceding articles in this Feature Engineering for ML series derived features from price geometry (Part 1), from the trading calendar (Part 3), from the bid-ask spread and price impact (Parts 5–6), from the information content of the trade-direction sequence (Part 7), and, most recently, from the timing of regime changes themselves (Part 10). This eleventh installment returns to price geometry, but at a coarser structural level: the swing highs and swing lows that define support, resistance, and trend.

more...

We built a reader that opens an ONNX file and tells us what is inside it. It works, and the report is accurate, but it arrives as a wall of text in the Experts tab. Thirteen layers scroll past with their input and output names. To understand the connections, we must trace those names by eye, line by line, while keeping the graph's structure in mind. A model with two parallel branches reads exactly like a model with one long chain, because a list has no way to show that two layers run side by side. The thing we most want to know about a network, its shape, is the one thing a list cannot give us. This article is for MetaQuotes Language 5 (MQL5) developers and algorithmic traders who want to see the model they are running rather than read about it.

more...