Tester Progress Telemetry

A long Strategy Tester pass or optimisation gives no obvious way to check progress except watching the terminal window, which is inconvenient if the test is running unattended or on a remote/headless box. This EA writes a one-row CSV to the sandboxed Files folder every time a new bar closes (or every N bars, to reduce disk writes on a fast test), containing the current wall-clock time, the simulated time reached, percent complete, elapsed wall-clock seconds and an estimated ETA - an outside script can tail this file on a timer and show progress without touching the terminal at all. The honest limitation stated plainly here: MQL4 has no function that reads back the Tester's own configured From/To dates, or the current pass number and total pass count during an optimisation. Neither is exposed to running code on either platform. This EA therefore needs the SAME From/To dates typed into its own inputs, matching whatever was set on the Settings tab, to compute percent complete at all - and during an optimisation, the telemetry file only ever describes the SINGLE pass currently executing on the thread that wrote it, not overall progress across the whole optimisation. A tool claiming to report full-optimisation ETA from inside one EA instance would be guessing at information it cannot actually see. Notes and limitations - If InpRangeFrom/InpRangeTo do not match the Tester's actual configured dates, PercentComplete will be wrong (it may exceed 100% early or never reach it) - there is no way for this EA to detect the mismatch itself, since it has no access to the real configured range. - ETA is estimated by simple linear extrapolation from wall-clock elapsed time versus simulated-time percent complete; a test that runs unevenly (e.g. dense tick data in some periods, sparse in others) will see the ETA estimate wander rather than count down smoothly - this is inherent to linear extrapolation, not a bug. - During an optimisation, each parallel Tester thread writes its OWN telemetry independently; if every thread shares the same InpTelemetryFile name, later writes overwrite earlier ones from other threads, so the file only ever reflects whichever thread wrote most recently. Give each thread a distinct file name (or accept that the file shows one thread's progress as a representative sample) for an optimisation run. - GetTickCount() wraps to zero after roughly 49.7 days of continuous terminal uptime; a single pass running that long in wall-clock time is not a realistic case this EA tries to handle, and is left as a documented limitation rather than worked around.

Expert advisor · MT4 · v1.0 · Free

Tags: Alerts · MT4 Expert Advisor · MQL4 Source Code

Expert advisors (EA) for MT4 & MT5 · PolyMaria