Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Mon, 06 May 2024 15:13:33 +0000
Conflicting data for Rollover between 2 Instances of S/C
View Count: 684
| [2017-06-13 18:40:15] |
| User68474 - Posts: 195 |
|
I'm seeing conflicting data (i.e. OHLC) for the ES rollover which just occurred last week. I have two instances of S/C on two different computers with both set to Rithmic Data ESU7 with "Continuous-Date Rule Rollover-Back Adjusted". Is this a S/C issue or Rithmic issue?
|
| [2017-06-13 18:47:43] |
| |
|
What exactly is the conflicting data. Be specific. You may need to re-download the data: https://www.sierrachart.com/index.php?page=doc/ContinuousFuturesContractCharts.html#ReDownloading 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 |
| [2017-06-13 23:38:48] |
| User68474 - Posts: 195 |
|
I was able to reconcile the difference by ReDownloading. For some reason one of the data files must have been corrupted during rollover, as I traced a -1.25 tick differential back to June 1st on the new (ESU7) Continuous chart. They are synched now. That had never happened before over many years with S/C.
Date Time Of Last Edit: 2017-06-13 23:39:51
|
| [2017-06-14 02:41:30] |
| |
|
OK that is good.
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: