Buggy iClose ? - page 2

 
numbnaive:

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

That is the current release version.
 
509 is the latest, non-beta
 
numbnaive:
The last USDCAD tick on 19-Dec-2013
2013-12-19 22:59:49.3002|TradePlatform.MT4.Core.Nlog.NlogEntryLogger|Debug|4|, --> 7176|NaiveUsdCad|QuoteReceived|1.06625000;1.06653000;1387497593|
...
Now follows the incorrect closing rate (approximately 12 hours later)
2013-12-20 10:59:56.5527|TradePlatform.MT4.Core.Nlog.NlogEntryLogger|Debug|15|, <-- ###MQL###|iClose|USDCAD|1440|1
2013-12-20 10:59:56.5527|TradePlatform.MT4.Core.Nlog.NlogEntryLogger|Debug|15|, --> 0:no error|1.06846000
...
Now follows the correct closing rate (approximately 15 hours later)
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

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

I dont see what is the point of the above log entries.

My close on 19-Dec was 1.0665 (4 digit broker) .

 
SDC:

I dont see what is the point of the above log entries.

My close on 19-Dec was 1.0665 (4 digit broker) .

The point of logging is first and foremost simply to re-establish the events of the programme. From there, the list goes on with benefits -- and ultimately a developer should be able via the log-files to identify if there is a bug in the code or faulty data, if an incident occurs.


By the way, thanks for sharing your closing rate.

 

well I know what the point of a log file is, but I do not see how those particular log entries relate to the issue or what conclusion you are drawing from them.

 

The point is that iClose() last Friday (20-Dec-2013) returned two different values for USDCAD close on 19-Dec-2013; the former being incorrect.

The opening post goes in more depth explaining the issue.