I am guessing this data is not from a MT4 source...? Then it is very likely that the 'volume' associated with each bar is not the count of ticks (the convention used in MT4) but is the actual depth of market and may very well be ~thousands per bar. The Tester does not 'know' this and makes an FXT file with ~thousands of ticks per bar. Hence u have huge FXT files and very slow testing.
...at some point without any error-message it just finishes.
The tester can handle FXT files of up to 2GB in size. If they are any larger, the testing would finish after 2GB of tick data (I don't remember if in this case there are any errors in the log?).
The only solution to this problem is to change all volume info. IMHO, there is no point scaling down this 'volume' since it has nothing to do with the number of ticks per bar. So personally I just change all bars to have a flat volume of 4. This can be easily done with a script (HST file format is known). Note though, that these kind of sources should be used with care! Specifically, I would not rely on them for Testing any expert that is affected by M1 bar movements...
Here ya go. It's a bit old and I haven't used it in a while, but I just checked and it seems fine.
To add comments, please log in or register