Support Board
Date/Time: Fri, 14 Mar 2025 17:57:59 +0000
Passing a tick's time to an .SCID file tick - issue
View Count: 530
| [2022-07-02 19:57:54] |
| User419467 - Posts: 13 |
|
When passing a tick's time to an .SCID file tick, the chart malfunctions. The header works well, as do the current date, prices and volumes. Everything feeds well into the live intraday .SCID file. The time, however, does not. The documentation provided refers to conflicting formats. These include the epoch start date (31-12-1899 in Windows, 30-12-1899 in documentation, and 1970 in Unix). Further, 2 methods for time appear in the documentation: milliseconds from the previous midnight in some, and milliseconds from one of the above epoch start dates in other documentation. Additionally, microseconds instead of milliseconds appear to succeed or precede SC versions (using version 2400 currently). The integer part of the binary bits allocated to date and time works well, and gives the date correctly from the second epoch start. The decimal part, for time, gives the problem. Currently working on the hypothesis that the decimal bit provides a start time and timezone shift, with SC then adding the actual timestamps. Programming in C#.NET and other .NET languages. Can't directly use the C++ classes as wrappers for memory leaks and other issues will need to be constructed. Any advice on this matter will be highly appreciated. Thank you,
|
| [2022-07-02 22:28:40] |
| User431178 - Posts: 614 |
|
Did you read this - Intraday Data File Format: s_IntradayRecord Structure Member Descriptions Datetime is int64, no decimal part, timezone is always UTC for SCID. |
| [2022-07-03 09:59:43] |
| |
|
From documentation: This is a 64-bit integer. It represents the number of microseconds since the SCDateTime epoch of December 30, 1899.
Refer to: Intraday Data File Format: DateTime Always use this new format and do not use the old format that is made in reference to versions earlier than 2151. No this is not correct: The documentation provided refers to conflicting formats. These include the epoch start date (31-12-1899 in Windows, 30-12-1899 in documentation, and 1970 in Unix). The documentation does not refer to conflicting formats. Only one format is mentioned.
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: 2022-07-03 10:01:47
|
To post a message in this thread, you need to log in with your Sierra Chart account: