I've used Birt’s CSV2FXT script v0.50 to convert CSV data for 2014 into FXT, however it's showing the errors as shown below when testing on M30 timeframe (any EA):
TestGenerator: spread set to 10
TestGenerator: unmatched data error (volume limit 385 at 2014.01.06 05:30 exceeded)
TestGenerator: unmatched data error (volume limit 239 at 2014.01.07 04:30 exceeded)
TestGenerator: unmatched data error (volume limit 368 at 2014.01.07 22:00 exceeded)
TestGenerator: unmatched data error (volume limit 732 at 2014.01.08 11:30 exceeded)
TestGenerator: unmatched data error (volume limit 197 at 2014.01.08 22:00 exceeded)
TestGenerator: unmatched data error (volume limit 251 at 2014.01.10 03:30 exceeded)
TestGenerator: unmatched data error (volume limit 412 at 2014.01.10 05:00 exceeded)
TestGenerator: unmatched data error (volume limit 239 at 2014.01.10 05:30 exceeded)
...
TestGenerator: unmatched data error (volume limit 149 at 2014.02.24 22:00 exceeded)
TestGenerator: unmatched data error (volume limit 357 at 2014.02.25 00:00 exceeded)
TestGenerator: unmatched data error (volume limit 301 at 2014.02.25 02:00 exceeded)
TestGenerator: unmatched data error (volume limit 179 at 2014.02.25 05:00 exceeded)
TestGenerator: unmatched data error (volume limit 373 at 2014.02.25 20:30 exceeded)
TestGenerator: 1281 generating errors, logged 100 first error records
The goal of this job is to fix the converter script (CSV2FXT.mq4) so above error won't happen. I'm not interested in workarounds, I need the actual fix in the MQL4 source code file, and the files are NOT read-only. I can provide given CSV file where the error happens (linked above). The reason of above errors is most likely wrong calculation of volume (tick_volume) for the higher timeframes which exceeds the expected sum of it. Please provide the patched MQL4 file where unmatched data error won't happen anymore.
Related posts:
- https://www.mql5.com/en/forum/126281
- https://www.mql5.com/en/forum/133540/page2
It's the same as all 'unmatched data errors', only in this case the volume is unmatched (usually O/C/H/L are unmatched). It means the tester is using data from a lower timeframe to test the EA on a larger timeframe, but the volume in the larger timeframe is not the sum of volumes of the lower timeframes... Hence - unmatched data error - this is literally the problem.