stevehopwoodforex.com
https://www.stevehopwoodforex.com/phpBB3/
Print view

Awesome - original version
https://www.stevehopwoodforex.com/phpBB3/viewtopic.php?t=5232		 Page 34 of 46
Author:  SteveHopwood [ Mon Sep 25, 2017 10:58 am ]
Post subject:  Awesome - original version
V 1n is in post 1.

I have adopted DC's suggestion in his post just above this one.

DC is working on a version with an alternative trade trigger and found some bits and bats that needed fixing last week. These fixes are in 1n.

Thanks DC :clap: :clap: :clap:

:xm:
Author:  taipan [ Tue Sep 26, 2017 2:12 am ]
Post subject:  Awesome - original version
DigitalCrypto » Thu Sep 21, 2017 6:18 pm wrote:
One of the traders in my group, Mike, mentioned that there is a 60% chance of an inside bar followed by a lower close on m1. This means that the entry would be more reliable but naturally less of them. I bring this up because Oanda doesn't present many FBs on live. Where as a bucket shop like Tradersway has literally hundreds of them.

I've incorporated these signals into variations of AO for testing to see if they aid in profit while reducing draw down on the m1 trader. It's too early for results but so far it is producing about 100% better profit with less draw down.

I will keep you guys updated as testing moves forward.

- David
When you are mentioning AO, is that Awesome Oscillator indicator or Accelator Oscillator?
Author:  Gertje [ Tue Sep 26, 2017 5:52 am ]
Post subject:  Awesome - original version
taipan » Tue Sep 26, 2017 2:12 am wrote:
When you are mentioning AO, is that Awesome Oscillator indicator or Accelator Oscillator?
Awesome Original perhaps?
Author:  Weyk [ Wed Sep 27, 2017 8:56 am ]
Post subject:  Awesome - original version
Guys

How can i change the FlyingBuddha shift in the code? I mean i want the EA to make decision if there is a Flying Buddha 2 candle back.

Code: Select all

double GetFlyingBuddha(string symbol, int tf, int ffp, int ffam, int ffpr, int fsp, int fsam, int fspr, int buffer, int shift)
{

   //Code by Baluda. Thanks very much Paul.
   
   double fastMA = iMA( symbol, tf, ffp, 0, ffam, ffpr, shift );
   double slowMA = iMA( symbol, tf, fsp, 0, fsam, fspr, shift );
   double high = iHigh( symbol, tf, shift );
   double low  = iLow( symbol, tf, shift );

   double result = EMPTY_VALUE;
      
   //-- long signal
   if ( buffer == 2 && high < MathMin( fastMA, slowMA ) ) result = low;
     
   //-- short signal
   if ( buffer == 3 && low > MathMax( fastMA, slowMA ) ) result = high;
   
   return ( result );

}//End double GetFlyingBuddha()
I think this way:

double fastMA = iMA( symbol, tf, ffp, 0, ffam, ffpr, shift 2);
double slowMA = iMA( symbol, tf, fsp, 0, fsam, fspr, shift 2 );

Will the above work? Not sure...
Author:  DigitalCrypto [ Wed Sep 27, 2017 9:34 am ]
Post subject:  Awesome - original version
Weyk » Wed Sep 27, 2017 2:56 am wrote:Guys

How can i change the FlyingBuddha shift in the code? I mean i want the EA to make decision if there is a Flying Buddha 2 candle back.

Code: Select all

double GetFlyingBuddha(string symbol, int tf, int ffp, int ffam, int ffpr, int fsp, int fsam, int fspr, int buffer, int shift)

.....
}//End double GetFlyingBuddha()
When you call the GetFlyingBuddha() function you will see at the end is "int shift" you would just send a 2.

Around line 4k you will find code for it.

Code: Select all

double val = GetFlyingBuddha(symbol, TimeFrames[tfIndex], FbFastPeriod, FbFastAvgMode, FbFastPrice, 
                                            FbSlowPeriod, FbSlowAvgMode, FbSlowPrice, 2, 1);
If you change the last variable in that call from 1 to 2 that will give you what you want. You would need to do this for both calls. There is one right below that too.

- David
Author:  DigitalCrypto [ Wed Sep 27, 2017 9:43 am ]
Post subject:  Awesome - original version
BTW just a note to anyone expecting to get the next rendition of Awesome Original with different trade entry. It's proving to be less profitable than AO. In fact it's generating 50% of the return that AO is with the same settings and just using a different entry.

I know when I see "well enough" and I know when to leave it alone. :D
Author:  Weyk [ Wed Sep 27, 2017 11:03 am ]
Post subject:  Awesome - original version
When you call the GetFlyingBuddha() function you will see at the end is "int shift" you would just send a 2.

Around line 4k you will find code for it.
Thanks David, i found that line after my first attempt didn't compile so i searched another.

Cheers.
Author:  SteveHopwood [ Wed Sep 27, 2017 11:11 am ]
Post subject:  Awesome - original version
Weyk » Wed Sep 27, 2017 11:03 am wrote:
When you call the GetFlyingBuddha() function you will see at the end is "int shift" you would just send a 2.

Around line 4k you will find code for it.
Thanks David, i found that line after my first attempt didn't compile so i searched another.

Cheers.
Great to see you delving under the bonnet. :clap: :clap: :clap: All traders should be coders. Even something as simple as you are doing can help you a lot. It will help you hugely once you discover how bog-basic is crapql4.

Ask DC if in doubt about this. He could not have found a line of code a few months ago; now he is spotting my bloops. :lol: :lol: :lol: :clap: :clap: :clap:

:xm:
Author:  DigitalCrypto [ Wed Sep 27, 2017 11:32 am ]
Post subject:  Awesome - original version
Ain't that the truth. It has always been my understanding that traders should be coders. It just takes me a bit to wrap my head around it. The arrays...I don't want to talk about arrays.

BTW here's my Awesome "Outlaw" edition set file. It's booked about almost 4k pips since this weekly open.

Definitely worth setting up a demo account and watching this thing go. I'd appreciate any help and suggestions that can improve it.
Author:  DigitalCrypto [ Wed Sep 27, 2017 12:03 pm ]
Post subject:  Awesome - original version
@Steve,

I did notice that AO is skipping the movement of some stoplosses when BE or JS has been more than reached. For example there will be two trades well into profit. One order's stop will get moved to BE. The other doesn't do anything.

I can see that the trade management module is being called correctly. What I can't see is why it ignores some orders but not others.

I wanted to bring it up in case you had an "aha" idea that you knew about already.
All times are UTC Page 34 of 46

Powered by phpBB® Forum Software © phpBB Limited