winsteadglenn wrote:If anyone is using the slope feature, please let us know what works for you.
Hi Glen, I'm on board with the London line disabled and a 5M slope OOTB. Will keep you posted.
winsteadglenn wrote:If anyone is using the slope feature, please let us know what works for you.
Hi Glen,winsteadglenn wrote:If anyone is using the slope feature, please let us know what works for you.
Read my previous post of yesterday where I referred to the Point value. YOu have to adapt the value of 'stoplevel' in order to be able to make comparisons with values of 'Bid' and 'Ask'. Empty4 has the internal routine 'Point', but for a 5digit criminal you have to go to 10^-4. That is what you do here with the variable 'factor'.HiArt99 wrote:Hi Steve,
still struggling to get this EA to work for me on my Alpari UK demo account. I noticed in the comment that Fractal high is 0.00000 so I added this line to GetFractals just after v is calculated:
if(Symbol()=="EURGBP" && v > 0)Print("v = ",DoubleToStr(v, Digits),"; v - Ask = ",DoubleToStr(v - Ask, Digits),"; StopLevel = ",DoubleToStr(StopLevel, Digits));
This has returned the following data:
07:40:05 Balls to the Wall EURGBP,M1: v = 0.78996; v - Ask = -0.00016; StopLevel = 20.00000
It appears that FracHigh will never be set as "v - Ask > StopLevel" can not become TRUE. Should StopLevel be converted in to pips?. Easy enough to do and happy to make the adjustment locally; I'll just have to remember to make that amendment on each update.
Why this should be an issue for me and not for other folks, I am unsure. But thanks for any advice.
P.S.
Adjusting the StopLevel calculation to:
double StopLevel = MarketInfo(Symbol(), MODE_STOPLEVEL) / factor;
has caused a Fractal High comment to be displayed, as well as lot size, stop loss and take profit calculations.
So it appears that the answer to my question is YES!
Nice one. Thanks.HiArt99 wrote:Hi Steve,
still struggling to get this EA to work for me on my Alpari UK demo account. I noticed in the comment that Fractal high is 0.00000 so I added this line to GetFractals just after v is calculated:
if(Symbol()=="EURGBP" && v > 0)Print("v = ",DoubleToStr(v, Digits),"; v - Ask = ",DoubleToStr(v - Ask, Digits),"; StopLevel = ",DoubleToStr(StopLevel, Digits));
This has returned the following data:
07:40:05 Balls to the Wall EURGBP,M1: v = 0.78996; v - Ask = -0.00016; StopLevel = 20.00000
It appears that FracHigh will never be set as "v - Ask > StopLevel" can not become TRUE. Should StopLevel be converted in to pips?. Easy enough to do and happy to make the adjustment locally; I'll just have to remember to make that amendment on each update.
Why this should be an issue for me and not for other folks, I am unsure. But thanks for any advice.
P.S.
Adjusting the StopLevel calculation to:
double StopLevel = MarketInfo(Symbol(), MODE_STOPLEVEL) / factor;
has caused a Fractal High comment to be displayed, as well as lot size, stop loss and take profit calculations.
So it appears that the answer to my question is YES!
Code: Select all
double StopLevel = MarketInfo(Symbol(), MODE_STOPLEVEL);
if (!CloseEnough(StopLevel, 0) ) StopLevel/= factor;
Bias calculation:vivaldi wrote:Just a few minutes ago, this order started.
As you can see, the EA did not take the first fractal as SL. Therefore, the SL it took, is rather big : 22 pips (see the red line) and the Target = 66 pips.
I don't think this was the intention of Paulus. Paulus would almost certainly have taken the SL at 1.2515, which leads to a target of around 16 pips. Much more realistical in a TFM1.
This is version 1f. I started it about half an hour ago. I am not sure as to how the Bias calculation works when you start the EA after the official morningopeninghour .But anyways, here we got a Bias = short and because of that, this resulted in the current order.
SteveHopwood wrote: If a fractal is too close to the market for the stop loss to pass the stop level test, it looks for the next most recent fractal, and so on until it finds one that is close enough.
I am away for two days now, without internet access (only just found out about the Dongle and not bought one yet). Whilst I am away, you guys give some thought about what to do about too-distant stops and I will make the adjustment when I return - or one of the coders can do it.