Posts made by roar

@kiwi789 I think theyre pretty straightforward:

• Init: this happens once, when the EA is loaded onto a chart
• Timer: this happens at regular time intervals (set by you)
• Tick: this happens at every tick (price update)
• Trade: this happens when there's some trade action
• Chart: this happens when there's some user input on the chart
• Deinit: this happens when the EA is removed from the chart

@ambrogio this code returns the minimum stop in points - divide by 10 to get pips

SymbolInfoInteger(Symbol(),SYMBOL_TRADE_STOPS_LEVEL)

https://www.mql5.com/en/docs/constants/environment_state/marketinfoconstants

@jsauter86 FXTM has good history, for EURUSD and other majors at least.

@malospelos mt5 has a more accurate tester. Your history quality still depends on your broker, just like on mt4.

@malospelos mt5 lol

@01punchman actually, I was wrong. The cross condition works just like you have it. Fxdreema is smarter than I thought lol

And yes, candle ID1 from more settings.

@01punchman here's one issue, at least. The FALSE output (yellow) of "cross above" does not mean "cross below". You need a separate condition block for the down cross.
Also, you need to use ID 1 in the conditions, if you want to look back at your tests with completed candles. If there's a cross when the candle is still moving, that information may be lost when the candle completes. There's a million posts in the forum about this ID issue.

@cesardefez yes, thats correct for buys. Just change v to V, its case-sensitive.

Here's explanation of the variables box
https://fxdreema.com/forum/topic/10894/scan-historical-data-for-conditions-values/8

In a case of loop block, orange happens on each loop iteration, yellow happens after the loop has completed. See block information

@cesardefez for example, this one counts the sell pending orders.

@jzfusion try using these lines of code:

vdSwapSell=NormalizeDouble(SymbolInfoDouble(Symbol(), SYMBOL_SWAP_SHORT),3);
vdSwapBuy=NormalizeDouble(SymbolInfoDouble(Symbol(), SYMBOL_SWAP_LONG),3);

https://www.mql5.com/en/docs/marketinformation/symbolinfodouble
https://www.mql5.com/en/docs/constants/environment_state/marketinfoconstants#enum_symbol_info_double

@cdwilder1 nowadays you can open conflicting positions on MT5 as well, if you open a hedging account with your broker.

The MT5 default account type is netting account, but many MT5 brokers seem to offer more hedging accounts as its a familiar system for old MT4 users.

@cesardefez if you dont care if theyre runnig trades or pending orders, use function OrdersTotal() to get that value.
https://docs.mql4.com/trading/orderstotal

If you need to separate running trades and pending orders, you have to use "for each trade" loop and just count the loop iterations into some variable.

@cdwilder1 when I started learning this forex stuff, MT5 was already out and I started with it. I still do everything in MT5 , MT4 is just for the forum examples as people seem to be stuck with it I dont really know why MT4 is still so popular, maybe there's some licence fees of MT5 that brokers dont want to pay, and thus they advertise MT4 for everyone...

MT5 indeed has a superior testing environment for the EAs. Fxdreema is nearly 100% identical for mql4/mql5.
As for this particular project, there is no difference at all. Just open the MT4 project in a browser tab, open an empty MT5 project in another tab, and copy-paste the blocks.

@seb-0 nowadays many mt5 brokers dont advertise their netting accounts very visibly, dont know why... maybe they get more swaps from the hedging trades.

Anyway, netting is the "default" method in mt5 (at launch it was the only option), every broker should be able to provide those accounts - just email them and ask nicely, thats how I get the accounts.

@seb-0 yes, you can simulate netting:
when you get a "sell signal", check first if there's already some buy trades open -> if yes, dont open new sells, but instead close an equal amount of buy trades. And vice versa... Only complication would be varying lot amounts, not in this particular project though.

I didn't develop this idea any further, its just some interesting phenomenon that seems to work in certain market conditions.... maybe I'll return to this after some 5 years lol

If you think this stochastics setup is effective, go ahead and provide some backtest results for us ; )

@leeds7878 the system rounds off the lot amount, and the more precise value is lost -> accumulation will never happen.

You'll need 2 separate variables for the lot amount: one precise value for the calculations, and one rounded value for the actual trade

@cdwilder1 yes, it's "relative" or something like that.
For example, if rel is set to 0.7, I can read the conditon as "standard deviation is not more than 70% of ATR".

@cdwilder1 yeah, working with arrays is usually custom code.
But in essence, an array is just a storage space (a table) of multiple variables. And the number of these part-variables is dynamic, you can "declare" 10000 variables inside the array just as easily as 2 variables - thats the useful thing in arrays.

Could you possibly explain the logic behind the streak being set to -1, why if condition five is false streak gets adjusted in block 6 by +1, and the V6+2 in the same block? I'm trying to understand the thought process behind this. I'm sure you have very good reasons for doing it this way, but I don't immediately understand why. Hahah.

• I dont see where I set streak to -1. I set current_is_bull to -1 in the first block, just because the value has to be something else than 0 or 1. If it was 0 and the loop detects a bear candle in the first iteration, that one bear candle would be counted twice, in a sense.
• I adjusted streak by 1 after my visual testing suggested trying it
  I think the reason is that streak actually counts the successive bars after the first bull/bear candle has been detected -> when there is actually 2 successive bull candles, the streak variable value is only 1 at that point, before making the adjustment...
• Reason behind the +2 adjustment: 1 for the reason I explain above, +1 to extend the id range to the candle before the streak began (reading from right to left), in case there's a candle wick making the extreme point

I find this a bit difficult to explain, I'll make a picture as well Hope you get at least something out of it

@bertkuiper does it trade when you disable the "certain hour" filter, just "once a day"? Does your broker allow automated trading?

@bertkuiper I tested your EA with current time and got the trade, no problem...

Check these buttons: