@roar Thank You very much! Yes, I will do the rest by myself. Thanks a lot again!

Thank you very much for your help! I created a screenshot to explain what I am searching for, the red indicator is 25SMA and I want to get as an alert how many candles ago the price crossed 25SMA. So, I want to get alert about the number that is marked as yellow.

Thank you very much for your help! I made this change, but unfortunately it still doesn't work as expected.
The initial idea was to implement following logic:
If price is above MA, check when it crossed above MA and alert
If price is below MA, check when it crossed below MA and alert

Hello,

I would like to get information about how many candles ago price crossed MA, I created EA for that, but unfortunately it doesn't work. What is wrong there, link to shared project is here https://fxdreema.com/shared/RANrLu32c?

Thanks a lot!

The problem is that SL/TP-s are not triggered when testing multicurrency EA using "Open prices only" modelling. I will describe the problem in step-by-step tutorial:

1. Please find from here https://fxdreema.com/shared/5ZhNrcDpb a very simple MA based EA (it takes trades in every MA cross), after that move the file into MT5 Experts folder

2. Please run the test with following parameters
   

3. Please observe during the simulation how SL/TP-s are triggered in Strategy visualization window (you will notice that they are not triggered at all) e.g EURGBP currency pair (this problem is not related with certain currency pair, you can check also some other pair)
   

4. Check the Balance / Equity graph - at the end it will drop to zero, because all orders are getting stop-out's, and that is explainable because TP/SL-s are not triggered, total amount of losses are bigger than equity and that's why all orders get Stop-out's.
   

In conclusion testing multicurrency EA using "Open prices only" modelling is not working properly, because TP/SL-s are not triggered. It is working if you use other type of modelling, e.g "Every tick" modelling.

@roar Thank You very much! Yes, I will do the rest by myself. Thanks a lot again!

@l-andorrà said in FRACTALS DEFINITION:

@mmaarits Yes, reading backwards is alway more effective. However, the only way to do it is by creating a loop to do that. That is not my field of expertise, though. Maybe roar could give us a hand?

@roar Can You help me out? That would be awesome!

My original idea was to have 4 variables:

• latest_Fractal_up
• previous_Fractal_up
• latest_Fractal_down
• previous_Fractal_down

First condition is that previous Fractal up and Fractal down must not have default values (that means I have stored also previous Fractals values and not only latest Fractals values).
After that for a SELL trade, the second condition is that latest_Fractal_up < previous_Fractal_up
AND latest_Fractal_down < previous_Fractal_down
and vice versa for the BUY trade.
BUT, I need to update previous_Fractal_up/down variables if new Fractal appears, that means previous_Fractal_up/down needs to replace with latest_Fractal_up/down value. Unfortunately, I am not able to implement that logic.

The better idea would be to implement logic in another way, because previously written algorithm needs to run EA for a while until it gets all Fractals values. Much better way would be, that EA reads Fractal values backward. That means, EA checks if Candle ID 3 has fractal values, if not, then check Candle ID 4. If Candle ID 4 has upper Fractal value then the EA stores it and continues this checking process until both previous (not only latest) Fractal up and down values are stored.

@l-andorrà No, I do not want to compare fractal up and fractal down, instead of that I would like to compare one Fractal before the very last Fractal and the last Fractal. That means: one fractal up before the very last fractal up > last fractal up AND one fractal down before the very last fractal down > last fractal down = SELL
And vice versa for the BUY trade: one fractal up before the very last fractal < last fractal up AND one fractal down before the very last fractal < last fractal down.

@l-andorrà said in FRACTALS DEFINITION:

n you need to store all those values into three different variab

Why it is necessary to have three different variables? Can You explain it a little bit more?

ggrobot stores Fractal values, compares it with current candle close and then takes trades.
But I want:

• If the latest downward Fractal is lower than previous downward Fractal AND latest upward Fractal is also lower than previous upward Fractal - then it is a SELL trade.
• If latest upwards Fractal is higher than previous upward Fractal AND latest downward Fractal is also higher than previous downward Fractal - then it is a BUY trade.