Price Data Generated Errors When Optimizing
Good day, All.
When optimizing an EA I’m getting are out-of-array errors, erroneous results far out of line of what they should be, and terminals crashing altogether. When I run a backtest for any of the passes that are a result of these optimizations, the EA provides what I would assume to be normal results. I'm currently using 16 terminals to take advantage of the 2 threads per core that my 8-core CPU has for the sake of poor-man WFA by given each of the terminals their own stage of the WFA to optimize and forward test. I have confirmed that this issue is not specific to my EA as the stock MACD Sample EA has the same issue and for the same span of time the terminal has been assigned. I have also deleted and redownloaded the data not only for the span of time I'm having issues with but the whole date range for the symbol subject to the WFA. I've had this problem using data from both TickStory and TDS. Not only that, periods of time different from those I had issues with the pervious installation of data will generate these errors so it seems that its an issue with the terminal themselves. I will find one of the terminals which is able to optimize a certain range of time and copy and paste its FXT file in the data folder of a terminal that is not working properly and after clearing out the Tester's cache file, that terminal still does not work.
In the attached file, the terminal on the left shows the results of an optimization that sometimes does and does not have "out of array" errors showing in the journal and the one on the right shows the 2nd type of optimization result I get, and the third causing the terminal to crash all together.
Let me know what I may be missing and thank you for your help!
Send the code so we can take a look. There is no way we can help you otherwise Array errors occur usually when you try to access an array element using an index that is outside the bounds of the array. In other words, you are trying to access an element of the array at an index that doesn't exist within the array's size.
double myArray[5]; // Array with 5 elements here // Trying to access an element at index 6, which is out of bounds double value = myArray[6];
so you can see this is not possible. here we have an array that has only 5 elements (top line), indexed from 0 to 4. Trying to access myArray[6] would result in an "out of array" error because the index 6 is beyond the range of the array. the first line has 5 elements because we start at 0,1,2,3,4 so, [5] elements total
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
You agree to website policy and terms of use
Good day, All.
When optimizing an EA I’m getting are out-of-array errors, erroneous results far out of line of what they should be, and terminals crashing altogether. When I run a backtest for any of the passes that are a result of these optimizations, the EA provides what I would assume to be normal results. I'm currently using 16 terminals to take advantage of the 2 threads per core that my 8-core CPU has for the sake of poor-man WFA by given each of the terminals their own stage of the WFA to optimize and forward test. I have confirmed that this issue is not specific to my EA as the stock MACD Sample EA has the same issue and for the same span of time the terminal has been assigned. I have also deleted and redownloaded the data not only for the span of time I'm having issues with but the whole date range for the symbol subject to the WFA. I've had this problem using data from both TickStory and TDS. Not only that, periods of time different from those I had issues with the pervious installation of data will generate these errors so it seems that its an issue with the terminal themselves. I will find one of the terminals which is able to optimize a certain range of time and copy and paste its FXT file in the data folder of a terminal that is not working properly and after clearing out the Tester's cache file, that terminal still does not work.
In the attached file, the terminal on the left shows the results of an optimization that sometimes does and does not have "out of array" errors showing in the journal and the one on the right shows the 2nd type of optimization result I get, and the third causing the terminal to crash all together.
Let me know what I may be missing and thank you for your help!