New article How to Evaluate the Expert Testing Results has been published:
The article gives formulas and the calculation order for data shown in the Tester report.
Before starting to test, the testing subsystem loads
the expert, sets its parameters previously defined by the user, and
calls the init() function. Then the Tester plays through the generated
sequence and calls the start() function every time. When the test
sequence is exhausted, the Tester calls the deinit() function. At this,
the entire trading history generated during testing is available. The
expert efficiency can be analyzed at this moment.
Hi Slawa et al,
Very much a NuB here.
I need a Back Test and Optimization Report Summary that doesn't include all of the trades. I'm hoping to add in the picture of the graph as well. But this looks like just what I need thanks (< 8)
Before I start, what and where are the two programs that generate the Mt4 Optimization and Back Test reports? Are they compiled (C++) MQL4 and are they directly accessible by us? It would be great if they were as I just need to eliminate the large lists of all of the trades and could possibly temporarily disable this aspect of them. Or just have to separate report Summary versions: One with the trades included and one without.
But *.mqh files go into the include folder and not *.mq4 files done't they? I tried it both as an mq4 and an mqh file and in both instances the compiler checks them out as being just fine themselves. However as soon as the EA is compiled, it goes crazy as it encounters 2 init, 2 deinit sections and flags these as errors and a whole LOT of: ')' - unbalanced right parenthesis errors. I've looked it over and I can't see how it can work in the setup with putting basically what are 2 complete EAs together and combining the code into one init section and one deinit section.
So I tried 'Copying and pasting' everything from your ReportSummary program that is in the init and deinit sections into an EA and 'remarked these out in your report EA and I can get these two functioning alright this way, but then it does the same thing with the 'start' function which being the body of the program is huge. Thus it would basically melding the two EAs together. But I know that include files can and do work very well for such things. But aren't they usually just a bunch of indivdiual function definitions etc so that one can just call them from any EA at any time without having to remake them every time?
Their is little doubt that you and the other folks here know a LOT more about this than I do and that I am making a fundamental error right from the very start? I'm fairly certain that what I have been trying: combining them both into one physical EA, is not the problem and approach to use. What fundamental mistake am I making right at the very start of this please that thwarts the whole thing for me?