Posts made by roar

Update 29.8.2023: Refactored the EA to work on modern hedging method mt5 accounts. Also simplified the strategy to what matters the most (theres lots of useless/low impact stuff in original version), in essence the strategy is this:

• Build long/short positions with RSI
  - When above 70, sell
  - When below 30, buy
  - Before selling/buying another time, wait for the RSI to visit level 50. This discourages trading against strong trends.
• There must be a mechanism that favors closing the positions rather than letting long/short position grow bigger and bigger
  - Only allow the position to grow if price is above daily median (buy) or below median (sell)
  - Trades that shrink the total position don't have that rule, so positions naturally stay small
• Lastly, limit the trading actions to more volatile half of the day by comparing fast and slow ATR values

The reduced strategy is not quite as profitable as the original one, but still clearly on the black after 6700 trades. Feel free to add your ideas to this.

https://fxdreema.com/shared/rCGHpDKod

@bardiamsa its EURUSD 5 minute. Read the posts for more info, especially about account type

I think what's needed is x value as a datetime, y value as a pixel coordinate. A mix between label-type object and normal object.

So one option is to use rectangle label (fixed pixel coordinates) and continually update the x value with ChartTimePriceToXY function (ignore the Price->Y conversion in that function).

There is a function called PipValue hidden in the background, you can test what it gives.

So you want a fixed Y point but moving X coordinate? Or both fixed - then you could use "rectangle label" object.

@TipsyWisdom you mean something like the period separator lines?

@MrDaisyBates stack overflow most often means you have some kind of infinite loop, yes. There's many "run block x" links in your project, maybe some of them create a loop

@xavier-joao-mpete not for free, hehe. We can discuss in PM.

The difference between = and == is actually very very important (I confuse them often myself lol).

= sets the variable value
== compares two variables together, returning True if they match, False if they dont match

edit: hmm, dont know why I ended up answering to 2 year old thread

@MrDaisyBates Hi! I dont immediately see any obvious error... To help troubleshooting, you should put some Print() statements here and there, checking the sizes of your array. This often leads to clues to solving the error.

Try checking the array size and id variable before your block #36, as it seems to are getting outside range there.

Actually, I think the issue is a bit more nuanced than simply taking the closest available data point. Lets say the SL and TP are both inside the H and L of a history candle. Now the tester has to decide, did the trade hit TP before it hit SL, because they both were possible with certain intra-candle movement patterns. Now, I think the tester favors the profitable side there as well - it always acts like TP was hit before SL.

@MrDaisyBates tester will take Open, High, Low or Close price, whatever is closest. And remember these are always 1-min OHLC, so if you use 1-hour chart the effect is less noticeable because there are 60*4 data points available.

But yes, fixed levels are a fundamental issue because they don't (can't) respect the limited nature of history data

@TipsyWisdom said

ah ok, accounting for what has been said so far, I could also put all closing conditions, under a once per minute and it would also solve all this?

Yes, it helps. Basically, if you do your trading actions on open/close prices, everything is fine because metatrader usually has the open & close prices for every candle. Problems arise the moment you make trading actions at any fixed level (pending order, fixed SL, fixed TP, trailing stop) because metatrader might not have data exactly for the level you want.

@seb-0 no, I meant fixed stops are probably just as problematic on "open prices" modelling, but if you dont use fixed stops and instead do every entry and exit action once per bar, then you can use the rough modelling without noticeable difference.

I find it more my style to quickly test a lot of EA iterations on rough data, rather than focusing on 100% tick data at the cost of much slower development. Can't do any HFT strategies using this approach, naturally.

@seb-0 I agree, I've thought about this effect many times myself... In essence, if your TP (or trailing SL) triggers at such a price point where the tester doesnt have data, you get extra profit all the way to the nearest available price point.

The effect is negligible if you trade big timeframes, or check your triggers on candle close only (in this case "open prices only" testing mode is perfectly fine to use), but it will cause serious problems when you make your trading actions on every tick and small scale, especially with trailing stop.

Naturally, 99% of those glorious mql5.com Market EAs abuse the heck out of this.

@Nils its probably better to place a pending order then. If you want to use market order, put your delay before the buy block

@make_123 try making your own thread, and using better grammar