mql5
member

This article presents an architecture where exit modules never modify a position directly. Each module produces a proposal. A policy engine ranks all well-formed proposals in a strict, documented order. A validator checks the candidates in that order against risk invariants and broker constraints, and the first candidate that passes is handed to an execution adapter, the only component that interacts with the trade server. A reconciliation step then compares the broker-side position with

Read More

The Greatest Swing Value breakout strategy requires several conditions and calculations to be applied in a specific order. The system first identifies a bullish or bearish setup; It then finds the required number of qualifying failure bars and calculates their average swing. That value is multiplied by a breakout factor and projected from the current bar open to define the entry threshold.


Each setup remains valid for the current bar only. While it is active, the strategy

Read 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

Read More

In the previous article, From Basic to Intermediate Level: Random Access (II), it was shown how we can work with files while ensuring random access to the data or information they contain. It was also explained and demonstrated that the same concept does not always produce the same result when we looking only at a file’s internal contents. However, when looking at the results displayed in the terminal, there will be no differences between one implementation and another, since the implementation

Read More

In the previous article I put a small indicator under the MetaEditor profiler and let two columns of numbers tell me where its time was going. The profiler answers one question well: where is this program slow? It has nothing to say about a different and often costlier question, the one where the program is fast enough but simply wrong. A line draws smoothly, the terminal reports no error, and yet the values it plots are quietly incorrect. For that class of problem MetaEditor ships a separate

Read More