Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sun, 08 Sep 2024 01:32:01 +0000
Chart data errors and the message log
View Count: 1401
| [2015-08-06 05:50:24] |
| i960 - Posts: 360 |
|
Is there any way we can: 1. Potentially provide configuration ability to control what pops up the message log, perhaps in general settings based on severity? 2. Make it so errors in chart recalculations don't pop up the message log? Someone else had previously touched on it here: https://www.sierrachart.com/supportboard/showthread.php?t=21457 Here's why this is becoming highly annoying: I have more than a few instruments where data is either missing (not on Barchart, IB problem, etc) or where a specific rollover method won't work with the given contract completely, and every single time a chart recalc happens the message log pops up and blocks all trading until the thread yields enough so I can close the message log (which is now streaming line after line for back adjustment calculations, etc). Then guess what happens 5 seconds later? Message log pops up again. I don't mind that being written to the message log, but it's a problem when the log keeps popping up on every new market open/close, etc. I trade Asian session into European session and this frequently happens right when London opens - making me scramble to close it just so I can see what's actually going on in the open. It also frequently happens when IB does a server reset, like clockwork, message log pops up as it recalcs every chart on reconnect. Now I'd love to just fix the underlying data issues, but those might be related to things I cannot control, what I could control however is what is important enough to pop up the log - if I had that ability to control it. Right now, the minimum severity is not controllable in any way. While I can see how wanting to immediately know of chart data integrity issues, there are times when it's either unfixable or won't be fixed on any fast timeframe, and the log will keep coming up. Here's some of the errors I see that'll cause the log to pop up: Error Jumping to date in file: RMU03.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMX03.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMF04.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMH04.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMK04.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMN04.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMU04.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMX04.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMF05.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMH05.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMK05.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMN05.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMU05.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMX05.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMF06.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMH06.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMK06.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMN06.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMU06.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMX06.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMF07.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMH07.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMK07.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMN07.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMU07.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMX07.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMF08.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMH08.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMK08.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMN08.dly. | 2015-08-05 01:08:00 * Error Jumping to date in file: RMU08.dly. | 2015-08-05 01:08:00 * Error while getting daily open price with date 2003-09-04 from file. C:\SierraChart\Data\RMU03.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2003-09-04 from file. C:\SierraChart\Data\RMX03.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2003-11-06 from file. C:\SierraChart\Data\RMX03.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2003-11-06 from file. C:\SierraChart\Data\RMF04.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2004-01-04 from file. C:\SierraChart\Data\RMF04.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2004-01-04 from file. C:\SierraChart\Data\RMH04.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2004-03-04 from file. C:\SierraChart\Data\RMH04.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2004-03-04 from file. C:\SierraChart\Data\RMK04.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2004-05-06 from file. C:\SierraChart\Data\RMK04.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2004-05-06 from file. C:\SierraChart\Data\RMN04.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2004-07-04 from file. C:\SierraChart\Data\RMN04.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2004-07-04 from file. C:\SierraChart\Data\RMU04.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2004-09-04 from file. C:\SierraChart\Data\RMU04.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2004-09-04 from file. C:\SierraChart\Data\RMX04.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2004-11-04 from file. C:\SierraChart\Data\RMX04.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2004-11-04 from file. C:\SierraChart\Data\RMF05.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2005-01-06 from file. C:\SierraChart\Data\RMF05.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2005-01-06 from file. C:\SierraChart\Data\RMH05.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2005-03-04 from file. C:\SierraChart\Data\RMH05.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2005-03-04 from file. C:\SierraChart\Data\RMK05.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2005-05-05 from file. C:\SierraChart\Data\RMK05.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2005-05-05 from file. C:\SierraChart\Data\RMN05.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2005-07-04 from file. C:\SierraChart\Data\RMN05.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2005-07-04 from file. C:\SierraChart\Data\RMU05.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2005-09-04 from file. C:\SierraChart\Data\RMU05.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2005-09-04 from file. C:\SierraChart\Data\RMX05.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2005-11-04 from file. C:\SierraChart\Data\RMX05.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2005-11-04 from file. C:\SierraChart\Data\RMF06.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2006-01-05 from file. C:\SierraChart\Data\RMF06.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2006-01-05 from file. C:\SierraChart\Data\RMH06.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2006-03-04 from file. C:\SierraChart\Data\RMH06.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2006-03-04 from file. C:\SierraChart\Data\RMK06.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2006-05-04 from file. C:\SierraChart\Data\RMK06.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2006-05-04 from file. C:\SierraChart\Data\RMN06.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2006-07-06 from file. C:\SierraChart\Data\RMN06.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2006-07-06 from file. C:\SierraChart\Data\RMU06.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2006-09-04 from file. C:\SierraChart\Data\RMU06.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2006-09-04 from file. C:\SierraChart\Data\RMX06.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2006-11-04 from file. C:\SierraChart\Data\RMX06.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2006-11-04 from file. C:\SierraChart\Data\RMF07.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2007-01-04 from file. C:\SierraChart\Data\RMF07.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2007-01-04 from file. C:\SierraChart\Data\RMH07.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2007-03-04 from file. C:\SierraChart\Data\RMH07.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2007-03-04 from file. C:\SierraChart\Data\RMK07.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2007-05-04 from file. C:\SierraChart\Data\RMK07.dly. Error: Date not found | 2015-08-05 01:08:01 Error while getting daily open price with date 2007-05-04 from file. C:\SierraChart\Data\RMN07.dly. Error: Date not found | 2015-08-05 01:08:02 Error while getting daily open price with date 2007-07-05 from file. C:\SierraChart\Data\RMN07.dly. Error: Date not found | 2015-08-05 01:08:02 Error while getting daily open price with date 2007-07-05 from file. C:\SierraChart\Data\RMU07.dly. Error: Date not found | 2015-08-05 01:08:02 Error while getting daily open price with date 2007-09-06 from file. C:\SierraChart\Data\RMU07.dly. Error: Date not found | 2015-08-05 01:08:02 Error while getting daily open price with date 2007-09-06 from file. C:\SierraChart\Data\RMX07.dly. Error: Date not found | 2015-08-05 01:08:02 Error while getting daily open price with date 2007-11-04 from file. C:\SierraChart\Data\RMX07.dly. Error: Date not found | 2015-08-05 01:08:02 Error while getting daily open price with date 2007-11-04 from file. C:\SierraChart\Data\RMF08.dly. Error: Date not found | 2015-08-05 01:08:02 Error while getting daily open price with date 2008-01-04 from file. C:\SierraChart\Data\RMF08.dly. Error: Date not found | 2015-08-05 01:08:02 Error while getting daily open price with date 2008-01-04 from file. C:\SierraChart\Data\RMH08.dly. Error: Date not found | 2015-08-05 01:08:02 Error while getting daily open price with date 2008-03-06 from file. C:\SierraChart\Data\RMH08.dly. Error: Date not found | 2015-08-05 01:08:02 Error while getting daily open price with date 2008-03-06 from file. C:\SierraChart\Data\RMK08.dly. Error: Date not found | 2015-08-05 01:08:02 Error while getting daily open price with date 2008-05-04 from file. C:\SierraChart\Data\RMK08.dly. Error: Date not found | 2015-08-05 01:08:02 Error while getting daily open price with date 2008-05-04 from file. C:\SierraChart\Data\RMN08.dly. Error: Date not found | 2015-08-05 01:08:02 Error while getting daily open price with date 2008-07-04 from file. C:\SierraChart\Data\RMN08.dly. Error: Date not found | 2015-08-05 01:08:02 Error while getting daily open price with date 2008-07-04 from file. C:\SierraChart\Data\RMU08.dly. Error: Date not found | 2015-08-05 01:08:02 Error while getting daily open price with date 2008-09-04 from file. C:\SierraChart\Data\RMU08.dly. Error: Date not found | 2015-08-05 01:08:02 Symbol Error - VIX-201508-CFE-USD is unknown, unavailable, or improperly formatted. The contract description specified for VIX is ambiguous; Symbol Error - D-201509-LIFFE_NF is unknown, unavailable, or improperly formatted. No security definition has been found for the request | 2015-08-05 13:16:28 Symbol Error - D-201509-LIFFE_NF is unknown, unavailable, or improperly formatted. No security definition has been found for the request | 2015-08-05 13:16:28 Symbol Error - D-201509-LIFFE_NF is unknown, unavailable, or improperly formatted. No security definition has been found for the request | 2015-08-05 13:16:28 you must specify the multiplier or trading class.. IB Error Code: 200. Request ID: 21. | 2015-08-05 13:16:31 HD Request # 2334 | Error downloading historical Intraday data for VIX-201508-CFE-USD. The symbol is unknown to the server. | 2015-08-05 13:16:31 * Message from IB: No historical data query found for ticker id:21. IB Error Code: 366. Request ID: 21. | 2015-08-05 13:16:31 Interactive Brokers | Symbol Error: Unknown symbol with ID 100015 is unknown, unavailable, or improperly formatted. | 2015-08-05 13:16:34 Interactive Brokers | Symbol Error: Unknown symbol with ID 100005 is unknown, unavailable, or improperly formatted. | 2015-08-05 13:16:34 HD Request # 2345 | Message from IB: No security definition has been found for the request. IB Error Code: 200. Request ID: 22. | 2015-08-05 13:16:46 HD Request # 2345 | Error downloading historical Intraday data for D-201509-LIFFE_NF. The symbol is unknown to the server. | 2015-08-05 13:16:46 * Message from IB: No historical data query found for ticker id:22. IB Error Code: 366. Request ID: 22. | 2015-08-05 13:16:46 Error Jumping to date in file: WIK04.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIM04.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIN04.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIQ04.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIU04.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIV04.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIX04.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIZ04.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIF05.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIG05.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIH05.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIJ05.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIK05.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIM05.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIN05.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIQ05.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIU05.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIV05.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIX05.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIZ05.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIF06.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIG06.dly. | 2015-08-05 13:22:39 * Error Jumping to date in file: WIK04.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIM04.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIN04.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIQ04.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIU04.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIV04.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIX04.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIZ04.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIF05.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIG05.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIH05.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIJ05.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIK05.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIM05.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIN05.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIQ05.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIU05.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIV05.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIX05.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIZ05.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIF06.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: WIG06.dly. | 2015-08-05 13:22:46 * Error Jumping to date in file: ESU95.dly. | 2015-08-05 13:30:16 * Error Jumping to date in file: ESZ95.dly. | 2015-08-05 13:30:16 * Error Jumping to date in file: ESH96.dly. | 2015-08-05 13:30:16 * Error Jumping to date in file: ESM96.dly. | 2015-08-05 13:30:16 * Error Jumping to date in file: ESU96.dly. | 2015-08-05 13:30:16 * Error Jumping to date in file: ESZ96.dly. | 2015-08-05 13:30:16 * Error Jumping to date in file: ESH97.dly. | 2015-08-05 13:30:16 * Error Jumping to date in file: ESM97.dly. | 2015-08-05 13:30:16 * Error Jumping to date in file: ESU95.dly. | 2015-08-05 15:00:07 * Error Jumping to date in file: ESZ95.dly. | 2015-08-05 15:00:07 * Error Jumping to date in file: ESH96.dly. | 2015-08-05 15:00:07 * Error Jumping to date in file: ESM96.dly. | 2015-08-05 15:00:07 * Error Jumping to date in file: ESU96.dly. | 2015-08-05 15:00:07 * Error Jumping to date in file: ESZ96.dly. | 2015-08-05 15:00:07 * Error Jumping to date in file: ESH97.dly. | 2015-08-05 15:00:07 * Error Jumping to date in file: ESM97.dly. | 2015-08-05 15:00:07 * Error Jumping to date in file: ESU95.dly. | 2015-08-05 17:37:21 * Error Jumping to date in file: ESZ95.dly. | 2015-08-05 17:37:21 * Error Jumping to date in file: ESH96.dly. | 2015-08-05 17:37:21 * Error Jumping to date in file: ESM96.dly. | 2015-08-05 17:37:21 * Error Jumping to date in file: ESU96.dly. | 2015-08-05 17:37:21 * Error Jumping to date in file: ESZ96.dly. | 2015-08-05 17:37:21 * Error Jumping to date in file: ESH97.dly. | 2015-08-05 17:37:21 * Error Jumping to date in file: ESM97.dly. | 2015-08-05 17:37:21 * Symbol Error - VIX-201508-CFE-USD is unknown, unavailable, or improperly formatted. The contract description specified for VIX is ambiguous; Symbol Error - D-201509-LIFFE_NF is unknown, unavailable, or improperly formatted. No security definition has been found for the request | 2015-08-05 20:30:26 Symbol Error - D-201509-LIFFE_NF is unknown, unavailable, or improperly formatted. No security definition has been found for the request | 2015-08-05 20:30:26 Symbol Error - D-201509-LIFFE_NF is unknown, unavailable, or improperly formatted. No security definition has been found for the request | 2015-08-05 20:30:26 Interactive Brokers | Symbol Error: Unknown symbol with ID 100022 is unknown, unavailable, or improperly formatted. | 2015-08-05 20:30:31 Interactive Brokers | Symbol Error: Unknown symbol with ID 100015 is unknown, unavailable, or improperly formatted. | 2015-08-05 20:30:31 Error Jumping to date in file: ESU95.dly. | 2015-08-05 20:30:47 * Error Jumping to date in file: ESZ95.dly. | 2015-08-05 20:30:47 * Error Jumping to date in file: ESH96.dly. | 2015-08-05 20:30:47 * Error Jumping to date in file: ESM96.dly. | 2015-08-05 20:30:47 * Error Jumping to date in file: ESU96.dly. | 2015-08-05 20:30:47 * Error Jumping to date in file: ESZ96.dly. | 2015-08-05 20:30:47 * Error Jumping to date in file: ESH97.dly. | 2015-08-05 20:30:47 * Error Jumping to date in file: ESM97.dly. | 2015-08-05 20:30:47 * you must specify the multiplier or trading class.. IB Error Code: 200. Request ID: 39. | 2015-08-05 20:30:58 HD Request # 2426 | Error downloading historical Intraday data for VIX-201508-CFE-USD. The symbol is unknown to the server. | 2015-08-05 20:30:58 * Message from IB: No historical data query found for ticker id:39. IB Error Code: 366. Request ID: 39. | 2015-08-05 20:30:58 HD Request # 2427 | Message from IB: No security definition has been found for the request. IB Error Code: 200. Request ID: 40. | 2015-08-05 20:30:58 HD Request # 2427 | Error downloading historical Intraday data for D-201509-LIFFE_NF. The symbol is unknown to the server. | 2015-08-05 20:30:58 * Message from IB: No historical data query found for ticker id:40. IB Error Code: 366. Request ID: 40. | 2015-08-05 20:30:58 Symbol Error - VIX-201508-CFE-USD is unknown, unavailable, or improperly formatted. The contract description specified for VIX is ambiguous; Symbol Error - D-201509-LIFFE_NF is unknown, unavailable, or improperly formatted. No security definition has been found for the request | 2015-08-05 22:14:02 Symbol Error - D-201509-LIFFE_NF is unknown, unavailable, or improperly formatted. No security definition has been found for the request | 2015-08-05 22:14:02 Symbol Error - D-201509-LIFFE_NF is unknown, unavailable, or improperly formatted. No security definition has been found for the request | 2015-08-05 22:14:02 Interactive Brokers | Symbol Error: Unknown symbol with ID 100028 is unknown, unavailable, or improperly formatted. | 2015-08-05 22:14:06 Interactive Brokers | Symbol Error: Unknown symbol with ID 100024 is unknown, unavailable, or improperly formatted. | 2015-08-05 22:14:06 Error Jumping to date in file: ESU95.dly. | 2015-08-05 22:14:10 * Error Jumping to date in file: ESZ95.dly. | 2015-08-05 22:14:10 * Error Jumping to date in file: ESH96.dly. | 2015-08-05 22:14:10 * Error Jumping to date in file: ESM96.dly. | 2015-08-05 22:14:10 * Error Jumping to date in file: ESU96.dly. | 2015-08-05 22:14:10 * Error Jumping to date in file: ESZ96.dly. | 2015-08-05 22:14:10 * Error Jumping to date in file: ESH97.dly. | 2015-08-05 22:14:10 * Error Jumping to date in file: ESM97.dly. | 2015-08-05 22:14:10 * HD Request # 2468 | Message from IB: No security definition has been found for the request. IB Error Code: 200. Request ID: 52. | 2015-08-05 22:14:56 HD Request # 2468 | Error downloading historical Intraday data for D-201509-LIFFE_NF. The symbol is unknown to the server. | 2015-08-05 22:14:56 * Message from IB: No historical data query found for ticker id:52. IB Error Code: 366. Request ID: 52. | 2015-08-05 22:14:56 you must specify the multiplier or trading class.. IB Error Code: 200. Request ID: 53. | 2015-08-05 22:14:57 HD Request # 2469 | Error downloading historical Intraday data for VIX-201508-CFE-USD. The symbol is unknown to the server. | 2015-08-05 22:14:57 * Message from IB: No historical data query found for ticker id:53. IB Error Code: 366. Request ID: 53. | 2015-08-05 22:14:57 In the Robusta Coffee case (RM), the contract simply doesn't go back past 2009, but if I have a long-term chart with some arbitrarily long span of time (4000 days or something), it's not reasonable for one to have to perfectly input the exact number of days such that it won't cause an error due to being before the contract started trading. Same thing with ES, it specifically throws errors because it didn't come to life as a tradable contract until ESU97. Sierra knows how to *not* try and chart this missing data, but it doesn't know how to ignore the errors such that it doesn't immediately pop up the message log. VIX, I don't understand what the problem is - it charts fine. Same thing with D-201509-LIFFE_NF, it also throws errors but charts fine (both historical and intraday). These two I'm using IB data for, as I already pay for enough data and don't need high accuracy on these. |
| [2015-08-06 06:43:31] |
| |
|
Messages like these are triggered by error messages from Interactive Brokers TWS: HD Request # 2468 | Message from IB: No security definition has been found for the request. IB Error Code: 200. Request ID: 52. | 2015-08-05 22:14:56 HD Request # 2468 | Error downloading historical Intraday data for D-201509-LIFFE_NF. The symbol is unknown to the server. | 2015-08-05 22:14:56 * The bolded text is from Interactive Brokers. And also we strongly recommend that you reduce the number of days loaded in the charts as necessary, to a point where you avoid errors resulting from data not being available for historical futures contracts. it's not reasonable for one to have to perfectly input the exact number of days such that it won't cause an error due to being before the contract started trading.
Yes it is reasonable. Not precisely, but approximately to avoid errors.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2015-08-06 07:09:15
|
| [2015-08-06 07:16:18] |
| i960 - Posts: 360 |
|
Messages like these are triggered by error messages from Interactive Brokers TWS:
HD Request # 2468 | Message from IB: No security definition has been found for the request. IB Error Code: 200. Request ID: 52. | 2015-08-05 22:14:56 HD Request # 2468 | Error downloading historical Intraday data for D-201509-LIFFE_NF. The symbol is unknown to the server. | 2015-08-05 22:14:56 * I know it's from IB, but I'm simply using the definitions that are there. A similar one exists for W-######-LIFFE_NF and C-######-LIFFE_NF-GBP. Perhaps the problem here is that IB no longer uses that as the exchange label. It should be ICEEUSOFT: https://www.interactivebrokers.com/en/index.php?f=2222&ns=T&exch=iceeusoft&showcategories=FUTGRP I have just tested this with D, C, and W and there are no errors after that. The Sierra side data still needs to be fixed so others don't run into this and it also needs the rollover periods fixed because they aren't defined. I don't know what's up with the VIX contract, I believe I'm using the one provided server side. Yes it is reasonable.
If one wanted to chart a contract from the beginning of inception of that contract they'd have to change the days to load every single day! If something came to life 100 days ago, and I set the chart to load exactly 100 days back then I have to reset the chart to 101 days the next day, or 120 days 20 days after the fact. That isn't reasonable. Think about how this would affect somebody trying to trade a new contract introduced - they'd be throwing errors for months on end until there were enough data. You're thinking with a coding mindset here. It shouldn't be throwing errors for something that's *pragmatically* a non-error situation to the overwhelming majority of users. A reasonable approach from a coding standpoint is to simply only throw errors on missing data files **only if a previous datafile in the continuous series has already been loaded**. It's still free to report it to the log, but it shouldn't be a hard error. If the number of successfully loaded contracts in a continuous contract being assembled is >0, *then* make it a hard error. Date Time Of Last Edit: 2015-08-06 07:26:52
|
| [2015-08-06 07:59:51] |
| i960 - Posts: 360 |
|
So literally, changing the code to simply not throw a hard error if a prior contract in the series hasn't been successfully loaded yet is considered "user discussion". Nevermind the fact that it completely fixes the problem, reduces annoyance of your users, does not affect existing behavior in any way, and fixes new contract issues that *will* be a problem when/if they're introduced. LIFFE_NF symbols are still busted as well. It's ICEEUSOFT. Date Time Of Last Edit: 2015-08-06 08:00:34
|
| [2015-08-06 08:15:33] |
| |
|
We will see about preventing some of those messages from opening the Message Log. But the messages will not be removed. We will check on the symbols specifications to make sure they are what Interactive Brokers currently requires. Please allow us at least a week for this. We are quite backlogged now. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2015-08-06 08:30:42] |
| i960 - Posts: 360 |
|
Yeah that's fine. To be clear I never meant remove the messages - only not pop up the message log in that specific scenario. It happens to me multiple times a day at this point. As far as LIFFE_NF goes, it should be safe to just change the 3 contracts (D, C, and W) to be ICEEUSOFT. IB changed the exchange label at some point - most likely due to ICE ownership changes. Contract rollover is fairly straight forward for these as well. Date Time Of Last Edit: 2015-08-06 08:31:10
|
| [2015-08-08 02:14:01] |
| |
|
Symbol Settings have been updated. But we did not add any new rollover settings at this time.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2015-08-10 09:56:38] |
| |
|
A reasonable approach from a coding standpoint is to simply only throw errors on missing data files **only if a previous datafile in the continuous series has already been loaded**
As we said, the errors will always be reported. In the case of Continuous Futures Contract charts, this features still is relatively new. The functionality is enormously complicated, and many things can go wrong and do go wrong. Detailed reporting is important.It is hard for us to know, what errors should open the Message Log and which ones should not because there are so many different reasons for error messages. It is hard to know this without actual practical information from long-term usage. In the case of the Continuous Futures Contract feature, there would never be missing files. But there can be empty data files. But even if the file is empty it does not mean that the data does not exist. The data may fill in when the data is re-downloaded for that file. **only if a previous datafile in the continuous series has already been loaded**
Even this does not have a definitive conclusion to it. There can be missing data between contract months due to historical data download failures.
Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2015-08-10 10:00:12
|
| [2015-10-15 23:08:21] |
| i960 - Posts: 360 |
|
Can we please make these failure to load data files go to the message log but *not* pop up the message log? Actually, maybe this is better explained another way: The problem is not with the errors going to the message log. The problem is with the message log *forcibly* being opened over and over no matter how many times I minimize the message log to stop it from spamming the window with 1000s of log lines and preventing me from even using Sierra during the time it's doing this. I can literally minimize it when it first pops up and 5 seconds later it'll unminimize itself and hammer me with log lines - preventing any form of reacting to charts or trading. This usually happens at the worst possible times too, such as market open of Asia or European markets and I'm left trying to minimize the window as fast as possible just to see what's going on - yet it keeps popping back up on me. |
| [2015-10-16 01:11:07] |
| |
|
We already solved this. What message are you referring to now? It will have an asterisk at the end of it. Also, what you can do is just move it to the edge of the screen. Because in this way, it will not open and it will not get the focus. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2015-10-16 01:12:02
|
| [2015-10-16 05:08:05] |
| i960 - Posts: 360 |
|
They're just generic contract loading issues as touched upon earlier in the thread (contracts earlier than existence), etc. What specifically is telling the message log window to restore itself and take focus? There has to be code in there that's telling it do such a thing. If a user minimizes the window, they don't want it popping up, ever - unless they care to look at it. A common approach some people use is to cause the minimized icon to blink or otherwise indicate something has changed - but without the window popping back up. I have a single screen and moving it to the edge of the screen isn't really the best option - not to mention that Windows 7 likes to make that very difficult by assuming that the window wants to go full top/bottom width when moved to the edge. |
| [2015-10-16 05:13:46] |
| |
|
The Message Log will not take the focus. If this is happening on your system it is system specific. We have verified this now. We caused a message to be added to the Message Log after we minimized the Message Log and it did restore itself, but it did not take the focus. Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
| [2015-10-16 05:30:52] |
| i960 - Posts: 360 |
|
Okay, simply restoring itself is the issue then. Why must the window pop back up in my face and disrupt things? Go load a newer contract, set the number of days to like 10000, daily chart (I don't necessarily use this, but it's to illustrate a point), then "reload and recalculate" and watch what happens. The message log will pop up and you cannot even minimize it quickly because of the pure volume of log lines pegging the window. I don't watch 3-4 contracts, I watch around 20-30 so you can imagine what this is like when just a single legitimate error causes the message log to restore. I am forced to get spammed with 1000s of non-error log lines (things like contract rollover status messages, etc.) before I can even get rid of the window. I thought I could side-step the problem by simply minimizing the window so that they went to the log but I didn't have to see them - unfortunately the log is making a point about restoring itself and that's the really annoying part. You have to understand this happens to me all the time - if my trading service is disconnected or a contract starts trading again from another session, etc. this message log will force it's way into the picture. It's not absolutely necessary for the window to restore, that's the intrusive behavior. It's perfectly normal to emit log lines to a minimized window without it popping back up. The win32 API has to be told a window should be restored and that's what the code is doing. Most people only want to see the message log when something is wrong and when something is wrong they check the logs. Most of the time only critical things like a disconnection etc are what people care about. I could care less about contract loading errors unless I'm setting up a new contract. To answer your question about what I saw this time, it was basically something along the lines of being unable to determine the rollover point based on volume. Other times it's been non-existent contract months. In all cases, it's the asterisk messages that are doing it because SC is saying to windows "yes, please restore this window." Date Time Of Last Edit: 2015-10-16 05:33:04
|
| [2015-10-16 05:46:21] |
| |
|
Must have been this message: "Unable to determine transition date based on volume from files" Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: