Home › Forums › Tickstory Lite › Issue/Bug tracking › GBPNZD [M15] FXT fails
-
AuthorPosts
-
Hi Jlao,
It sounds to me that you’re coming across the MT4 4GB FXT size limitation. You can find out more about this in our FAQ under the question “My back-test doesn’t complete fully and stops at a certain date. What’s happening?”:
Regards.
Hi,
Thanks for the reply.
I’m not sure that the 4Gb limitation is the origin of my problem, because I can perform 8 years backtest (Every Tick mode) with the other 35 pairs, and as you will see on the the enclosed image, these other pairs have bigger size.
By the other hand, if I try to backtest few months (i.e. always after 2011 year) for GBPNZD M15, I get this error message from MT4: MT4i – Data Integrity Checker: no data for testing, so it seems there is a problem inside the FXT file….
Regards,
jlao
Hi Jlao,
This one is a tough one because we’ve often seen some odd behaviour when larger than 4GB FXTs are used (although it’s impressive that you dont outwardly appear to be having problems with the other pairs).’
If there is something off with the 2011 year, this should be easy to prove by simply exporting only that year (i.e. FXT < '4GB) and theoretically you should get the same error. If you can confirm this and ideally the month it occurs, we can look into this further.Regards.
Hi,
I have made your directions and something happens in 2010 year.I followed these steps (always for GBPNZD – M15):
1) I exported the FTX file and for only 1 year (2011) –> the backtest was succesfull!! from January to December!!
2) I exported the FXT file and for only 1 year (this time 2010) –> backtest stopped at 2010.10.08 and I got MT4 Journal error message like this: “TestGenerator: invalid file for ‘GBPNZD15’”Below you will find MT4i – data Integrity Checker summary data for 2010:
Thanks!!
jlao
Hi JLao,
Thanks for the information We are currently in the process of trying to reproduce the issue with the information you have given. We’ll update you when we have more details.
Thanks.
Hi JLao,
We’ve done some further tests and it appears that there is an issue with the underlying data for GBPNZD on the 8th October 2010 at around 06:10 (there could be others). It seems there is a zero price somewhere in the mix which is causing the “invalid data” issue. The fix will most likely involve trying to filter out all anomalous (zero priced) data which will hopefully resolve the issue. We’ll let you know when we have an update.
Thanks for assisting us with identifying the problem.
Regards.
Hi JLao,
This issue has now been resolved by filtering out any tick that has a bid or ask price that is zero. This filtering only occurs during the MT4 export. File exports, charts and data viewer will still show the anomalous data for completeness.
For information about downloading this update, please see viewtopic.php?f=4&t=696&p=3303
Thanks again for taking the time to report the issue.
Kind regards.
-
AuthorPosts
You must be logged in to reply to this topic.