How to Deal with Bar0? | Forex Factory

Options

Permalinks
Print Thread

Similar Threads

Deal or no Deal Syndrome and other conditions that affect traders 6 replies

Smaller deal ticket Format 3 replies

Ok Whats The Deal with this spike 18 replies

Whats the deal with backtesting? 1 reply

The Pound has broken several Support lines. That is a big deal right? 2 replies

How to Deal with Bar0?

  • #1
  • First Post: Edited 4:00pm Oct 4, 2024 10:25am | Edited 4:00pm
Hi coders, I have a technical issue that I cannot resolve it. I have an entry condition as follows :-

Inserted Code
double Hi0=iHigh(sym,60,0), Hi1=iHigh(sym,60,1), Lo0=iLow(sym,60,0), Lo1=iLow(sym,60,1);
 
bool BuySignal= ... && Lo0>Lo1 && ...;
 
bool SelSignal= ... && Hi0<Hi1 && ...;

To place a BUY (BuySignal), it must be a "Lo0>Lo1" condition, otherwise my EA should not proceed to BUY, and vice versa for SELL signal.

。 。 。 。 。

Now, during my demo testing, I found that my EA yet placed BUY/SELL orders even through "Lo0<=Lo1" and "Hi0>=Hi1" happened respectively, and this should not happen at all.

。 。 。 。 。

In my opinion, the problem is on the Lo0 and Hi0 because the Bar0 is yet not a complete full bar.

I need coder's help and advice, how to resolve the Bar0 issue ? Thanks.
  • #2
  • Oct 4, 2024 6:23pm Oct 4, 2024 6:23pm
  •  FerruFx
  • Joined May 2007 | Status: MT4/MT5 EAs/Indicators/Alerts coder | 6,542 Posts | Online Now
Quoting chimoong
Now, during my demo testing, I found that my EA yet placed BUY/SELL orders even through "Lo0<=Lo1" and "Hi0>=Hi1" happened respectively
Most probably the trades were triggered correctly but later the lo0 and Hi0 went through their respective Lo1 and Hi1.
MT4/MT5 EAs/Indicators/Alerts coder
  • #3
  • Oct 4, 2024 11:39pm Oct 4, 2024 11:39pm
Quoting chimoong
Hi coders, I have a technical issue that I cannot resolve it. I have an entry condition as follows :- double Hi0=iHigh(sym,60,0), Hi1=iHigh(sym,60,1), Lo0=iLow(sym,60,0), Lo1=iLow(sym,60,1); bool BuySignal= ... && Lo0>Lo1 && ...; bool SelSignal= ... && Hi0<Hi1 && ...; To place a BUY (BuySignal), it must be a "Lo0>Lo1" condition, otherwise my EA should not proceed to BUY, and vice versa for SELL signal. 。 。 。 。 。 Now, during my demo testing, I found that my EA yet placed BUY/SELL orders even through "Lo0<=Lo1" and...
There is no technical issue here and the issue is not with Bar0. When a new bar starts, the very first tick... all of the H, L, O, C would likely be equal to the O of the new bar. This satisfies the condition of "Lo0>Lo1" as long as the previous bar has not closed on the extremes or gaped.

I suggest for you to draw out exactly what you are trying to do. Then either make the correction/ removal to that condition or shift everything by 1 bar: Lo0 becomes Lo1 and Lo1 becomes Lo2... if one needs to compare the lows.

Hope that helps
&quot;Work hard, put in the effort, and follow your dreams...&quot; -Me
  • #4
  • Oct 4, 2024 11:51pm Oct 4, 2024 11:51pm
Quoting chimoong
Hi coders, I have a technical issue that I cannot resolve it. I have an entry condition as follows :- double Hi0=iHigh(sym,60,0), Hi1=iHigh(sym,60,1), Lo0=iLow(sym,60,0), Lo1=iLow(sym,60,1); bool BuySignal= ... && Lo0>Lo1 && ...; bool SelSignal= ... && Hi0<Hi1 && ...; To place a BUY (BuySignal), it must be a "Lo0>Lo1" condition, otherwise my EA should not proceed to BUY, and vice versa for SELL signal. 。 。 。 。 。 Now, during my demo testing, I found that my EA yet placed BUY/SELL orders even through "Lo0<=Lo1" and...
double Hi0=iHigh(sym,60,0), Hi1=iHigh(sym,60,1), Lo0=iLow(sym,60,0), Lo1=iLow(sym,60,1);

bool BuySignal= ... && Lo0>Lo1 && ...;

bool SelSignal= ... && Hi0<Hi1 && ...;
[4 suggestions from me ^_^]
//001 - check with alert whether the four variables have valid values
Alert(StringConcatenate("Check value High: ",(string)Hi0,"|"+(string)Hi1," ; Check value Low: ",(string)Lo0,"|"+(string)Lo1));
//002 - Protection Miss Signal
if(BuySignal==true && SelSignal==true){
// signal rejected
}else{
//Your Trading Code
}
//003 - Check the EA settings: Allow live trading = true and autotrading in MT4 = true.
//004 - Even problematic lot sizes will prevent transactions from occurring, regularly check the experts or Journal tabs to check if there are rejected or problematic task codes
I know that the more I know, the more I don't know
  • #5
  • Oct 5, 2024 5:18am Oct 5, 2024 5:18am
From my investigation and confirmed that it was triggered incorrectly. My TF=60, let's say for the BUY condition of "Lo0>Lo1", the Lo0 started at 2024.10.04 08:00, during 2024.10.04 08:00 to 2024.10.04 08:30, the price of Lo0 fell below Lo1 (Lo0<Lo1), but at 2024.10.04 08:32, my EA yet placed a BUY trade, very weird.

FYI, for the past one whole week, it happened numerous times for both BUY and SELL.

If I do a print :-

Inserted Code
Print(Symbol()+" /Lo0 "+DoubleToStr(Lo0,Digits)+" /Hi0 "+DoubleToStr(Hi0,Digits));

The print output were correct, but in the real situation of my demo testing, the conditions of "Lo0>Lo1" and "Hi0<Hi1" did not work properly. I think most likely is the tick issue i.e. if there is no tick for Lo0 and Hi0, the High, Low and Close will be revised / equal to Open Price.

Quoting FerruFx
{quote} Most probably the trades were triggered correctly but later the lo0 and Hi0 went through their respective Lo1 and Hi1.
Quoting tzamo
{quote} There is no technical issue here and the issue is not with Bar0 ...
Quoting Zorox
{quote} [4 suggestions from me ^_^] ...
  • #6
  • Oct 5, 2024 5:56am Oct 5, 2024 5:56am
Quoting chimoong
From my investigation and confirmed that it was triggered incorrectly. My TF=60, let's say for the BUY condition of "Lo0>Lo1", the Lo0 started at 2024.10.04 08:00, during 2024.10.04 08:00 to 2024.10.04 08:30, the price of Lo0 fell below Lo1 (Lo0<Lo1), but at 2024.10.04 08:32, my EA yet placed a BUY trade, very weird. FYI, for the past one whole week, it happened numerous times for both BUY and SELL. If I do a print :- Print(Symbol()+" /Lo0 "+DoubleToStr(Lo0,Digits)+" /Hi0 "+DoubleToStr(Hi0,Digits)); The print output were correct, but in the real...
You may find more success using the previous candle's low/high compared to the low/high of the candle before that.

That should help with:
Quoting chimoong
I think most likely is the tick issue i.e. if there is no tick for Lo0 and Hi0, the High, Low and Close will be revised / equal to Open Price.
Software Developer and Music Producer
News Fundamentals All Time Return: 1,159.1%
  • #7
  • Oct 5, 2024 6:21am Oct 5, 2024 6:21am
Quoting jblanked
{quote} You may find more success using the previous candle's low/high compared to the low/high of the candle before that. That should help with: {quote}
Noted with thanks. I'm applying Price Action Strategy and focusing on the Bar0 changes but not so much of previous / past bars.
  • #8
  • Edited 6:51am Oct 6, 2024 6:40am | Edited 6:51am
Quoting chimoong
Hi coders, I have a technical issue that I cannot resolve it...
It seems you have a general mis-understanding how price is represented in bars, or you mis-understood what foreposters are trying to tell you.
Take your buy condition:
Inserted Code
bool BuySignal = ... && Lo0 > Lo1 && ...;

You can only expect valid signals if both lows don't change anymore. In your example it's the low of your bars 0 and 1. The only time Low0 doesn't change anymore is at the BarClose event. So, theoretically you must only check for signals at BarClose time. For M5 that's for example at 00:04:59, 00:09:59 and so on.

Now there's no platform in the world that offers you a BarClose event as part of the real-time data stream. Why? Because nobody knows when the last tick arrives. There can always be another tick between the received last tick and the end of the current timeframe (e.g. another tick between 04:59 and 05:00). This tick may change the shape of the formed bar and may invalidate your signal.

The only signal you can react on is the BarOpen event, which is the first tick of the new bar. Only when this first tick has arrived you know that the previous bar is now closed and fix/doesn't change anymore.

So, on first tick of the new bar you check for trade signals. As you want to compare the last two *finished* bars your above logic now becomes:
Inserted Code
bool BuySignal = ... && Lo1 > Lo2 && ...;

This is what foreposters tried to tell you. I hope you now can see better where your mis-understanding is.

In other words: If you want to compare a bar with the previous bar you always have to wait until both bars are closed. Otherwise your comparison may be easily invalid. You can never compare Bar1 and Bar0, as Bar0 by definition is never closed/always open.
It takes blood, sweat and enough tears to wash away the blood.
  • #9
  • Last Post: Oct 7, 2024 2:38am Oct 7, 2024 2:38am
Quoting emmzett
{quote} ... In other words: If you want to compare a bar with the previous bar you always have to wait until both bars are closed. Otherwise your comparison may be easily invalid. You can never compare Bar1 and Bar0, as Bar0 by definition is never closed/always open.
Thanks. I think the only way is firstly to get the iBarShift of lower TF of Bar0 (higher TF), then use the iBarShift to get the lowest low and highest high (for lower TF), finally to compare to previous Bar1 (higher TF).
0 traders viewing now