Need Help: iBarShift: Smaller TF Shift from Bigger TF | Forex Factory

Options

Permalinks
Print Thread

Similar Threads

Simple Help with iBarShift Please 4 replies

How do I iBarShift in reverse? 8 replies

iBarShift 3 replies

What does this do? iBarShift 2 replies

Bug w/ iBarShift function? 0 replies

Attachments: Need Help: iBarShift: Smaller TF Shift from Bigger TF
Exit Attachments

Need Help: iBarShift: Smaller TF Shift from Bigger TF

  • #1
  • First Post: Edited 9:07pm Jun 20, 2022 8:39pm | Edited 9:07pm
Hi coders, kindly advise and help.

Inserted Code
   int tTF=5;
 
   int b0M1Sf=iBarShift(Symbol(),1,iTime(Symbol(),tTF,0),true);
   int b1M1Sf=iBarShift(Symbol(),1,iTime(Symbol(),tTF,1),true);
   int b2M1Sf=iBarShift(Symbol(),1,iTime(Symbol(),tTF,2),true);
 
   {Alert(Symbol()+" M"+IntegerToString(tTF)+" Bar0/Bar1/Bar2 : "+IntegerToString(b0M1Sf)+" / "+IntegerToString(b1M1Sf)+" / "+IntegerToString(b2M1Sf))}

I would like to get the shift of smaller TF starting from bigger TF, but the output of different pairs are different, could you please advise :-

1) What is the solution to get the correct output results ?

2) Is this the bug of mq4 / MT4 and can never be resolved ?

Thanks
Attached Image (click to enlarge)
Click to Enlarge Name: iBarShift.png Size: 59 KB
  • #2
  • Jun 21, 2022 2:33pm Jun 21, 2022 2:33pm
When you access another instrument via code (i.e., not the chart on which the indi is attached to), or even if it's the same instrument but a different timeframe, you can easily get missing data.
When it happens, you can catch the error 4066 which is basically that the history hasn't updated. This is quite common for fetching info on other instruments/TFs, and there's no easy workaround.
Depending on how your test script is, for example if the results are erroneous on the first launch, most of the time if you launch it a second time it should work. That's because between the first call and the second call, the history has been downloaded.

One way to prevent this, is simply to compare the iTime(M5, bar 0), it should at least be the same value for your batch of symbols. Same thing for iTime(M1, bar 0) If you have a different value for a particular symbol, it means the isn't complete.
  • #3
  • Jun 21, 2022 2:43pm Jun 21, 2022 2:43pm
Quoting Oliver.Twist
When you access another instrument via code (i.e., not the chart on which the indi is attached to), or even if it's the same instrument but a different timeframe, you can easily get missing data. When it happens, you can catch the error 4066 which is basically that the history hasn't updated. This is quite common for fetching info on other instruments/TFs, and there's no easy workaround. Depending on how your test script is, for example if the results are erroneous on the first launch, most of the time if you launch it a second time it should work....
Thanks Oliver for your reply. Is there any solution to get the correct output ? If yes, could you please write down your codes so that I can test your codes. FYI, I have no programming background and I'm learning now, thanks again.

For my codes above, it is pretty simple, no error at all. The only issue I don't know how to get the correct output. I suggest you to test my codes in your MT4, then you can see the incorrect / inconsistent output.
  • #4
  • Jun 22, 2022 9:32am Jun 22, 2022 9:32am
Quoting chimoong
Hi coders, kindly advise and help. int tTF=5; int b0M1Sf=iBarShift(Symbol(),1,iTime(Symbol(),tTF,0),true); int b1M1Sf=iBarShift(Symbol(),1,iTime(Symbol(),tTF,1),true); int b2M1Sf=iBarShift(Symbol(),1,iTime(Symbol(),tTF,2),true); {Alert(Symbol()+" M"+IntegerToString(tTF)+" Bar0/Bar1/Bar2 : "+IntegerToString(b0M1Sf)+" / "+IntegerToString(b1M1Sf)+" / "+IntegerToString(b2M1Sf))} I would like to get the shift of smaller TF starting from bigger TF, but the output of different pairs are different, could you please advise :- 1) What is the solution to get...

Looking at alert time in your example: 09:03:30, M5 Bar 0, would read 2 , 0, 1 ,2, counting strats at 0.
  • #5
  • Jun 22, 2022 9:42am Jun 22, 2022 9:42am
Quoting Asw
{quote} Looking at alert time in your example: 09:03:30, M5 Bar 0, would read 2 , 0, 1 ,2, counting strats at 0.
Hi ASW, I suggest you to test my codes yourself as my intention is to get Smaller TF Shift (M1) from Bigger TF (M5). At 09:03:30, the output should read 0,5,10, but in actual fact that not all the pairs are same output ...

My Pic link : https://www.forexfactory.com/attachm...3?d=1655775620
  • #6
  • Jun 22, 2022 10:24am Jun 22, 2022 10:24am
Quoting chimoong
{quote} Hi ASW, I suggest you to test my codes yourself as my intention is to get Smaller TF Shift (M1) from Bigger TF (M5). At 09:03:30, the output should read 0,5,10, but in actual fact that not all the pairs are same output ... My Pic link : https://www.forexfactory.com/attachm...3?d=1655775620
your code looks at the M1 Timeframe and checks the start of the current M5 bar, last M5 bar and previous M5 bar
  • #7
  • Jun 22, 2022 10:28am Jun 22, 2022 10:28am
Quoting Asw
{quote} your code looks at the M1 Timeframe and checks the start of the current M5 bar, last M5 bar and previous M5 bar
Yes, correct, but why the output are varies ? Please advise. If you have the solution to get the correct output for all the pairs, kindly provide your codes, appreciated.
  • #8
  • Jun 22, 2022 10:40am Jun 22, 2022 10:40am
Quoting chimoong
{quote} Yes, correct, but why the output are varies ? Please advise. If you have the solution to get the correct output for all the pairs, kindly provide your codes, appreciated.
You need to make sure the chats data is upto date, bring up all the charts you are scanning for data and use the arrow key to load all data, then try.

You are looking at M1 data and getting the M5 bar, not looking at M5 data, looking for M1 bar.
  • #9
  • Jun 22, 2022 11:36am Jun 22, 2022 11:36am
Quoting Asw
{quote} You need to make sure the chats data is upto date, bring up all the charts you are scanning for data and use the arrow key to load all data, then try. You are looking at M1 data and getting the M5 bar, not looking at M5 data, looking for M1 bar.
Hi ASW, I already updated all the historical data many times for all the charts and all the pairs, yet cannot get the standardised correct output for all the pairs.

Have you tested yourself ? Are you getting the correct answers ? If yes, please provide your codes for me to test. Please advise, thanks
  • #10
  • Jun 22, 2022 2:31pm Jun 22, 2022 2:31pm
Quoting chimoong
{quote} Hi ASW, I already updated all the historical data many times for all the charts and all the pairs, yet cannot get the standardised correct output for all the pairs. Have you tested yourself ? Are you getting the correct answers ? If yes, please provide your codes for me to test. Please advise, thanks

What are you trying to achieve ?
  • #11
  • Jun 22, 2022 3:34pm Jun 22, 2022 3:34pm
You're getting the correct results, they're just not what you expect.

- put a 5m mtf candle on the 1m chart, and see for yourself where the 1m shifts are for every 5m candle as the minutes go by
- dont assume that the market watch time is the time that every symbol's last quote is
  • #12
  • Edited 10:02pm Jun 22, 2022 8:41pm | Edited 10:02pm
Quoting Asw
{quote} What are you trying to achieve ?
Hi ASW, what I want to achieve is my pic link https://www.forexfactory.com/attachm...3?d=1655775620 and stated clearly in red text and with the Alert to tell you the output ...

Sadly to say that I suggested you two times to test the codes yourself but you reluctant to do so and ended up with only your imaginations that kept on telling wrong answers. I really do not know how to explain further to you. Imagination with false assumptions don't work my dear friend ...
  • #13
  • Jun 22, 2022 8:43pm Jun 22, 2022 8:43pm
Quoting jeanlouie
You're getting the correct results, they're just not what you expect. - put a 5m mtf candle on the 1m chart, and see for yourself where the 1m shifts are for every 5m candle as the minutes go by - dont assume that the market watch time is the time that every symbol's last quote is
Hi Jean, thanks for your clarification. I would assume that this would be the inefficiency of mq4 and there is no solution at all to get the correct output ....
  • #14
  • Jun 22, 2022 11:51pm Jun 22, 2022 11:51pm
Quoting chimoong
{quote} Hi ASW, what I want to achieve is my pic link https://www.forexfactory.com/attachm...3?d=1655775620 and stated clearly in red text and with the Alert to tell you the output ... Sadly to say that I suggested you two times to test the codes yourself but you reluctant to do so and ended up with only your imaginations that kept on telling wrong answers. I really do not know how to explain further to you. Imagination with false assumptions don't work my dear friend ...

You are misinterpreting ASW's question to you, it's completely legitimate why he asked you this question because he wants to know what you are trying to achieve for the end product (note: I said end product, not your intermediate objective you posted in your screenshot), so that he can advise if there is a better way to code this, rather than the code you published here. Your approach is likely to be completely wrong in the first place, which is why it is not worth people's time to even test them in the first place. In other words, people need to know the BIG PICTURE before they can advise correctly. It's just common sense.
  • #15
  • Jun 23, 2022 1:21am Jun 23, 2022 1:21am
Quoting eess
{quote} You are misinterpreting ASW's question to you, it's completely legitimate why he asked you this question because he wants to know what you are trying to achieve for the end product (note: I said end product, not your intermediate objective you posted in your screenshot), so that he can advise if there is a better way to code this, rather than the code you published here. Your approach is likely to be completely wrong in the first place, which is why it is not worth people's time to even test them in the first place. In other words, people...
In my 1st post "1) What is the solution to get the correct output results ?" ... this is what I want to achieve, thanks
  • #16
  • Jun 23, 2022 3:25am Jun 23, 2022 3:25am
Quoting chimoong
{quote} In my 1st post "1) What is the solution to get the correct output results ?" ... this is what I want to achieve, thanks

Either you don't understand English or you are trying not to give more information, anyway no one can help you like that, you are on your own. Good luck. Anyone who wants to help you is just wasting their time playing guessing game with incomplete information.
  • #17
  • Jun 23, 2022 3:38am Jun 23, 2022 3:38am
Quoting eess
{quote} Either you don't understand English or you are trying not to give more information, anyway no one can help you like that, you are on your own. Good luck. Anyone who wants to help you is just wasting their time playing guessing game with incomplete information.
Hi Eess, kindly look at the pic : https://www.forexfactory.com/attachm...3?d=1655775620

1) At Market Watch time XX.03.XX, the correct output should be 3 / 8 / 13 but the codes gave the wrong output for some of the pairs as :-
a) 2 / 7 / 12

2) At Market Watch time XX.05.XX, the correct output should be 0 / 5 / 10 but the codes gave the wrong output for some of the pairs as :-
a) 4 / 9 / 14
b) 5 / 10 / 15

3) At Market Watch time XX.06.XX, the correct output should be 1 / 6 / 11 but the codes gave the wrong output for some of the pairs as :-
a) 4 / 9 / 14
b) 6 / 11 / 16

4) At Market Watch time XX.07.XX, the correct output should be 2 / 7 / 12 but the codes gave the wrong output for some of the pairs as :-
a) 1 / 6 / 11

Hope the above simple explanation can enlighten you, thanks ...
  • #18
  • Edited Jun 24, 2022 12:18am Jun 23, 2022 5:22am | Edited Jun 24, 2022 12:18am
Quoting chimoong
...I would like to get the shift of smaller TF starting from bigger TF, but the output of different pairs are different...
Quoting jeanlouie
...You're getting the correct results, they're just not what you expect.
JeanLouie is right. In general it doesn't matter whether one timeframe is larger or smaller. Key here is that you access two timeframes which both may be different from the current one. A timeseries different from the current chart timeframe needs to be preloaded and synchronized before one can expect correct results. If you don't do this (like you do in your code) you will get different results for every call until data is synchronized.

Quoting chimoong
2) Is this a bug of mq4 / MT4 and can never be resolved?
No, this is not an MQL bug. It's expected behavior and documented in the language reference. The bug is in front of the computer and needs to be fixed there.

Quoting chimoong
1) What is the solution to get the correct output results?
The best way to forcefully preload and synchronize a timeseries different from the current chart timeframe is to use ArrayCopyRates(MqlRates &array[], ...), and copy the timeseries to a local array. Calling iBarShift() or iTime() also loads/synchronizes the series but with a big catch. Data accessed this way only stays synchronized as long as you constantly access it. If for example you call your code once and say - the next time after 20 minutes, at the second call data will be most probably out of sync again. That's because the terminal monitors access to all timeseries and if you stop accessing one it automatically stops updating them and resources are released. This happens "after some time" which from my observations is about after 15 minutes.

To make sure data stays up-to-date call ArrayCopyRates() on every tick. It will not allocate new resources on each call as it only manages a pointer to the terminal's internal data structures.

After loading the timeseries the first time you have to wait until data synchronization finished. Begin of synchronization is signaled by ERR_HISTORY_WILL_UPDATED, there is no documented way to detect the end of it (although there are ways). So I recommend to call ArrayCopyRates() on every tick and in your main code you wait for about 10 seconds until calling iBarShift()/iTime() the first time. After those 10 seconds your timeframes will be synced and your code example will work flawless.

As you access two timeframes which may be different from the current one you have to manage two local arrays (one for each timeframe) and call ArrayCopyRates() for each of them.
It takes blood, sweat and enough tears to wash away the blood.
  • #19
  • Last Post: Edited 2:27pm Jun 23, 2022 1:58pm | Edited 2:27pm
Quoting chimoong
1) At Market Watch time XX.03.XX, the correct output should be 3 / 8 / 13
2) At Market Watch time XX.05.XX, the correct output should be 0 / 5 / 10
3) At Market Watch time XX.06.XX, the correct output should be 1 / 6 / 11
4) At Market Watch time XX.07.XX, the correct output should be 2 / 7 / 12
If your real and true intent is to produce above output depending on the time displayed in the title bar of the "MarketWatch" window then I suggest to not involve timeseries access at all. That's just not the right tool to achieve what you want. Instead use a snippet like the following. It will work for all standard timeframes except for PERIOD_W1 as the small one.

Inserted Code
int largeTimeframe = PERIOD_M5;
int smallTimeframe = PERIOD_M1;
 
int minutes = TimeCurrent()/60;
 
int offset0 = (minutes % largeTimeframe) / smallTimeframe;
int offset1 = offset0 + largeTimeframe/smallTimeframe;    
int offset2 = offset1 + largeTimeframe/smallTimeframe;    
  
Alert(Symbol() +" M"+ IntegerToString(largeTimeframe) +" Bar0/Bar1/Bar2 : "+ IntegerToString(offset0) +" / "+ IntegerToString(offset1) +" / "+ IntegerToString(offset2));
Attached Image(s) (click to enlarge)
Click to Enlarge Name: Calculation of timeframe offsets.png Size: 7 KB
Click to Enlarge Name: Results of offset calculation.png Size: 11 KB
It takes blood, sweat and enough tears to wash away the blood.
0 traders viewing now