dclayw » Sat Oct 21, 2017 1:49 pm wrote:I started running a test with v1m and H4PeakHiLo730.set on 19/9. At that time I did pick up the fact that some of the inputs, i.e. "Take every sgnal inputs" and "Trade closure inputs" used to be global inputs under previous versions of the EA, but under v1m these inputs became time frame specific. I just changed those inputs for "Time Frame 1" to match what they were in the original set file. If you just load the original set file against v1m then those particular inputs will take on default values as set by the EA, not the values as shown in the original set file.
It all gets very complicated and shows the importance of having some means of quality/version control when doing comparison testing. I agree this can be difficult when an EA is changing a lot with bugs being fixed and new functionality added. Nonetheless, if you're running tests for comparsion purposes and things change then you need to tweek the tests to account for those changes or start the test again, otherwise you're not comparing apples with apples, and it becomes difficult to get meaningful results out of it.
Anyway, just sharing my experience. I have been running H4PeakHiLo730 since 19/9 against v1m and have not had any problems with global basket closure, not that I've noticed anyway. All I've done with this EA is what I said above and I've just let the test run in the background, just to see what it will do. The general strategy in this EA is very sound in my opinion.
Here is the set file I'm running with:
And here is the results so far, been running for about 5 weeks now. I do close all trades on Friday evenings at 23:45 using APTM. There was slight problem with this in that pendings were being left open. Tommaso was kind enough to address that recently with an update to APTM.
