Support Board
Date/Time: Sat, 28 Dec 2024 21:58:21 +0000
How to import tick data that contains milliseconds from a CSV file?
View Count: 1121
[2016-04-21 20:24:04] |
User760942 - Posts: 120 |
Hi SC, Your documentation below explains what Time Format to use when importing tick data from a .csv that contains seconds, but not milliseconds. http://www.sierrachart.com/index.php?page=doc/doc_TextCSVDataFormat.html#TimeFormat Any tips on what Time Format I should use when importing tick data from a .csv that contains milliseconds? thnks |
[2016-04-21 20:59:08] |
Sierra Chart Engineering - Posts: 104368 |
We are updating the documentation now. Just give us about 10 minutes. You also need to be on version 1398. 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 |
[2016-04-21 22:03:34] |
User760942 - Posts: 120 |
Great. I just checked out the updated documentation. The HH:MM:SS.MS seems to suggest only two digits can appear in the millisecond section. Does this mean only 10 MS granularity can be used? Such as this: 01:22:43.54 Or could i use 1 MS granularity? Such as this: 01:22:43.547 |
[2016-04-21 23:11:34] |
Sierra Chart Engineering - Posts: 104368 |
From 1 to 3 digits for the milliseconds.
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 |
[2016-04-21 23:13:30] |
Sierra Chart Engineering - Posts: 104368 |
So .1 would be equivalent to 100 milliseconds. You could also do .100. 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: