Buggy iClose ?

[Deleted] 2013.12.20 14:31

Today Friday 20 December 2013 (GMT+1), I have identified two situations where iClose at first returned incorrect values.

What follows are snippets from my log-files (time-stamped GMT+1).

I have had my expert running for about a week now, and these two instances are the only two where I've seen incorrect behavior.

Has anyone else experienced similar issues ?

Simon Gniadkowski 2013.12.20 14:43 #1

numbnaive:

Today Friday 20 December 2013 (GMT+1), I have identified two situations where iClose at first returned incorrect values.

How do you ensure you have uptodate data for USDCAD and USDCHF ?

William Roeder 2013.12.20 15:08 #2

numbnaive: 2013-12-20 00:00:03.7687|TradePlatform.MT4.Core.Nlog.NlogEntryLogger|Debug|4|, <-- ###MQL###|iClose|USDCHF|1440|1

You appear to be looking at the D1 bar 1 value, but if your chart isn't the D1, the D1 may not have been updated yet. Find the correct bar index ALWAYS.

#define HR2400 86400       // 24 * 3600
int      TimeOfDay(datetime when){  return( when % HR2400          );         }
datetime DateOfDay(datetime when){  return( when - TimeOfDay(when) );         }
datetime Today(    datetime when=0){      if(when == 0)  when = TimeCurrent();
                                          return(DateOfDay( TimeCurrent() )); }
:
datetime yesterday  = Today() - 1;
int      iD1        = iBarShift(NULL, PERIOD_D1, yesterday);
double   closeEOD   = iClose(NULL, PERIOD_D1, iD1);

[Deleted] 2013.12.20 15:19 #3

RaptorUK:
How do you ensure you have uptodate data for USDCAD and USDCHF ?

I wait for GetLastError to return 0. The snippets below support that I discard results if the error code is 4066 (requested history update is in update state)

2013-12-20 14:06:14.6517|TradePlatform.MT4.Core.Nlog.NlogEntryLogger|Debug|6|, <-- ###MQL###|iClose|USDCAD|1440|1
2013-12-20 14:06:14.6567|TradePlatform.MT4.Core.Nlog.NlogEntryLogger|Debug|6|, --> 4066:requested history data in update state|1.06625000
2013-12-20 14:06:14.6567|TradePlatform.MT4.Core.Nlog.NlogEntryLogger|Error|11|Handler execution failed with error 'MQL returned error: '4066:requested history data in update state' for method iClose(USDCAD, 1440, 1). Failure Context: [HandlerName=NaiveUsdCad, Discriminator=17523NaiveUsdCad].QuoteReceived(1.06773000;1.06796000;1387551978)'. Failure Context: [HandlerName=NaiveUsdCad, Discriminator=17523NaiveUsdCad].QuoteReceived(1.06772000;1.06794000;1387551978),
2013-12-20 14:06:14.6567|TradePlatform.MT4.Core.Nlog.NlogEntryLogger|Debug|6|, <-- ###ERR###|Handler execution failed with error 'MQL returned error: '4066:requested history data in update state' for method iClose(USDCAD, 1440, 1). Failure Context: [HandlerName=NaiveUsdCad, Discriminator=17523NaiveUsdCad].QuoteReceived(1.06773000;1.06796000;1387551978)'. Failure Context: [HandlerName=NaiveUsdCad, Discriminator=17523NaiveUsdCad].QuoteReceived(1.06772000;1.06794000;1387551978)
2013-12-20 14:06:14.6567|TradePlatform.MT4.Core.Nlog.NlogEntryLogger|Debug|6|, Method execution time: 12 ms.
2013-12-20 14:06:14.6567|TradePlatform.MT4.Core.Nlog.NlogEntryLogger|Debug|6|, Connection closed
2013-12-20 14:06:14.8027|TradePlatform.MT4.Core.Nlog.NlogEntryLogger|Debug|4|, Connection opened
2013-12-20 14:06:14.8027|TradePlatform.MT4.Core.Nlog.NlogEntryLogger|Debug|4|, --> 17523|NaiveUsdCad|QuoteReceived|1.06771000;1.06794000;1387551979|
2013-12-20 14:06:14.8027|TradePlatform.MT4.Core.Nlog.NlogEntryLogger|Debug|4|, <-- ###MQL###|iClose|USDCAD|1440|1

2013-12-20 14:06:14.8027|TradePlatform.MT4.Core.Nlog.NlogEntryLogger|Debug|4|, --> 0:no error|1.06625000

Problems with gaps in need help to convert Please Help

[Deleted] 2013.12.20 15:35 #4

WHRoeder:
You appear to be looking at the D1 bar 1 value, but if your chart isn't the D1, the D1 may not have been updated yet. Find the correct bar index ALWAYS.

You are right, I am looking at daily closes ie. D1 and 1 bar back.

I understand what you are trying to do with the code -- ensuring I get the right bar.

The problem is not missing a bar, as the return values iClose() return do not match any previous close values.

The problem is that iClose has reported incorrect values, at first (even after ensuring all historic data is loaded), then it reports correct values.

Computational issues at the broker, or a bug deep down Metatrade ?

IOPEN function not returning [WARNING CLOSED!] Any newbie Help Needed ("zero divide"

Ian Venner 2013.12.20 15:37 #5

I wonder if MT4 rewrites the last bar each time, so if ticks were missed it is corrected on the chart as per HLOC. You would have to record all recieved ticks to verify if that is the case, then disconnect the internet a couple of minutes before the end of a bar, then reconnect after begin time of the next bar. If previous bar is corrected on the chart your log will show a difference and you will know your errors are caused by some missed ticks at the end of a bar.

Timestamps of the Open/High/Low/Close Unexpected results from Low[0] function sleep alternative

Simon Gniadkowski 2013.12.20 16:44 #6

numbnaive:

I wait for GetLastError to return 0. The snippets below support that I discard results if the error code is 4066 (requested history update is in update state)

And how long do you wait for the data to arrive before trying it again ? after you get the error 4066 it goes away . . . then some time later the data will have arrived, just because you don't get a new error 4066 doesn't mean the data has now arrived and is updated.

My EA seems to Please Help Community of Expertise

[Deleted] 2013.12.20 17:16 #7

RaptorUK:
And how long do you wait for the data to arrive before trying it again ? after you get the error 4066 it goes away . . . then some time later the data will have arrived, just because you don't get a new error 4066 doesn't mean the data has now arrived and is updated.

I generally try again at next tick -- in the snippet above, I try after approximately 150ms == 0.15second.

I am seriously disturbed if what you write is correct: "just because you don't get a new error 4066 doesn't mean the data has now arrived and is updated"

How is one then to know when data has arrived and is available ?

Please Help Community of Expertise Is it possible to

[Deleted] 2013.12.20 17:23 #8

SDC:

What closing rate for USDCAD on 19-Dec-2013 do others have ?

PREDICT time period BrainSystem: Trading System Development Making money on forex

Simon Gniadkowski 2013.12.20 17:59 #9

numbnaive:

I generally try again at next tick -- in the snippet above, I try after approximately 150ms == 0.15second.

I am seriously disturbed if what you write is correct: "just because you don't get a new error 4066 doesn't mean the data has now arrived and is updated"

How is one then to know when data has arrived and is available ?

Off the top of my head . . . save it's open time, if you get an error 4066 re-read until you get a different open time . . . or just wait a reasonable number of seconds, I have seen 15 seconds suggested.

Bars synchronization Problems with gaps in Function is getting some

[Deleted] 2013.12.20 18:16 #10

Thank you all for your input, in particular RaptorUK.

Since my EA is used for trading, I have devised these steps in order to mitigate the risk of data-corruption:

1) try to acquire EOD closing rates well in advance before they are actually needed. My algo allows for this.

2) have a human verify the values each day

3) compute HLOC-bars myself from the ticks received and compare with the acquired and humanly-accepted values

4) in case of continued discrepancies, invite the broker for coffee :-)

It just dawned on me that I am using build 509 (24 Jun 2013) -- could this really be the issue ??

Indicators on current bar mt5 strategy tester ticks Volatility Quality Index

1 2

New comment