kelisa wrote:Great adoptation/analysis with the 10.2. Great job CC.

FreddyFX wrote:my watch starts with a minute and not with an hour !!

so what is this thing about higher TFs before lower ??

coolncalm wrote:

FreddyFX wrote:my watch starts with a minute and not with an hour !!

so what is this thing about higher TFs before lower ??

LOL!! Freddy, maybe you can take on the challenge of adapting the system to work on the M1 TF

FreddyFX wrote:Indeed, evaluating if I have what it takes to get that done !!

RJo wrote:

coolncalm wrote:That’s it. Just a straightforward “trade with the bias, trade with an edge, in any market, on any TF” system...

What? My cerebrum just melted and it's running all over my desk.

But seriously, thanks for sharing your adaptation of 10.2A. Having limited coding knowlege, I would like to see all of the trading conditions for entries and exits defined in a purely objective manner. Coders might be more apt to adopt the system if you remove any subjective language i.e:

Buy
DP,0 > WP,0 > MP,0 and
TMA,0 > 0.2 and
DP, 1> WP,1 > MP,1 and
TMA,1 <0.2

Language like "near" would become:

TMA,0 > 0.2 - 5 pips and
TMA,0 < 0.2 + 5 pips

0 or 1 being the price shift, of course. Just a suggestion.

RJo wrote:I will code entry conditions using the iCustom command (to be pasted into an EA) and I will try to make each indi callable via iCustom, if not already callable. I already have Steve's 10.2 TMA...for EA indi and my own DWM...for EA indi. In any event, the conditions will be posted as a spec. Just be aware that instructions like "make allowance for the volatility of the pair" will be represented as ATR levels, etc. in order to quantify the instructions. I cannot promise anything for exits or an entire EA, but we shall see.

RJo wrote:I was able to lay out the conditions in a commercial EA builder and use it to generate an EA. WARNING: THE CODE IS NOT OPTIMIZED, and THIS EA HAS NOT BEEN TESTED. In case the software publishers are reading this, copyrights are included in full.

The inputs are preset to alert based on: any one of the four sets of DWM conditons for a UT plus a matching CSS trigger plus a matching Fast trigger, and the same for a DT. Neither the SMA's, nor the SEMA4x, nor the ATR are included at this time. I opted for Baluda's CSSDiff indi not because of any particular preference, but because he was generous enough to post his mq4 file for public use.

Other important input defaults:
MicroAccount=true (mini)
CompletedBars=false (this should have no effect at this time)
TradeorAlert=false (alert)--DO NOT SET THIS TO TRUE
FiveDigits==true
OrderIncludeTPSL=false(ECN type dealer)
TMALowerLevel1=-0.55
TMALowerLevel2=-0.8
TMAHigherLevel1=0.55
TMAHigherLevel2=0.8

You'll probably get multiple alerts in rapid succession due to my use of shift 0 which checks every Bid price. Again, this is merely a starting point. And... if your dealer has Sunday bars and you're trading on Sunday, DWM will be based on Thursday's data for a few hours due to AddSundaytoMonday... I think.