The Awesome Basket Forward Test

[lamdog330]

Hi guys. for what it's worth I'm having no issues whatsoever with global closures (both symbol and basket) using the latest v1q on a live account (Bully Bully Pepperstone). Using H4 PeakHiLo730.set, nice steady profits with low DD.

How are they compare to Global Prime?

[SWG123]

Great news thanks for sharing. Could you drop your set file please

Told you in my post.

[1Direction]

Told you in my post.

I understand you are using H4 PeakHiLo730.set the problem is that this set file was not originally designed for the last version and a lot of new settings were added to awesome which could be messing up with global basket closure so if you have a working version of H4 PeakHiLo730.set for 1q I would really appreciate if you could pm the file or upload it here.

Thank you in advance
1D

[barry]

Sorry for the delay in responding. I have attached the EA, which shows as v1g on-screen, plus the preset, which I exported from the platform, so it's definitely the preset I'm using. I'll be interested to see what you find.

[lamdog330]

Told you in my post.

Maybe it does make a difference. Can you export your set file instead of letting us know which set file you've used? We are a sharing community, otherwise, why are we here?

[WhoKnows]

Thanks for posting the files. It is a 2 min job comparing these with BC. I am no coder, but I can do comparisons
To save myself typing I will refer the 1Direction files as D and Barry's files as B.

- MQ4 files - both Awesome 1g MQ4 files are identical.

- EXE fliles - They are different, with a BUT...
The D version is a little bit 410 bytes longer and only a very small section appears to be the same.
The problem is that you can't make sense of compiles EXE's.
You both mentioned that on screen they displayed as 1g. So I assume both EXEs were compiled from identical MQ4 files, but the compiling was done with different versions of Empty4 editor, resulting in different EXEs. I have seen that before.

- SET-files - They are different. See the attach. However only TF1 is used so most differences are not relevant. Make sure to study the attach to check yourself.
As far as I can see the following differences are important:
Trade1MaxSignalsToFollow=4 (5 in the D set)
Trade1MinimumDistanceBetweenSignalsPips=20 (10 in the D set)
Trade1UsePercentageOfAtrForDistance=false (true in the D set)
Trade1CloseOnOppositeFB=false (true in the D set)

The difference in Trade1CloseOnOppositeFB=false (true in the D set) might explain why the B set resulted in a much higher DD compared to the D set.

set file compare.PNG

So possibly one riddle solved. Still need to test it side by side with the same broker and same exe file to confirm the above thoughts.
...............
Does anybody already have an idea about the post I made in the Awesome Original thread.http://www.stevehopwoodforex.com/phpBB3 ... 09#p157609 on the strange behaviour on 1Direction's MTF set at MyFXBook.
That is one that really worries/baffles me.

[dclayw]

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:

Awesome Magic 128 (H4 PeakHiLo730).set

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.

awtradereport.PNG

awtradechart.PNG

[SWG123]

I understand you are using H4 PeakHiLo730.set the problem is that this set file was not originally designed for the last version and a lot of new settings were added to awesome which could be messing up with global basket closure so if you have a working version of H4 PeakHiLo730.set for 1q I would really appreciate if you could pm the file or upload it here.

Thank you in advance
1D

Hi 1D - here is the set I am using with v1q. As far as I can remember the only changes I made were cosmetic, changing the display settings to make it more readable on my screen.

[1Direction]

I understand you are using H4 PeakHiLo730.set the problem is that this set file was not originally designed for the last version and a lot of new settings were added to awesome which could be messing up with global basket closure so if you have a working version of H4 PeakHiLo730.set for 1q I would really appreciate if you could pm the file or upload it here.

Thank you in advance
1D

Hi 1D - here is the set I am using with v1q. As far as I can remember the only changes I made were cosmetic, changing the display settings to make it more readable on my screen.

Thanks a lot! I'll set it up for next week on 1q would enjoy to see a global basket closure

[Wavegarrick]

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.

As usual nice work and clear direction, Dave. You earn another step up in my respect for you

Cheers
Leon