Login Page - Create Account

Support Board


Date/Time: Fri, 19 Apr 2024 14:51:14 +0000



Imported files do not show UTC not local time on chart

View Count: 1655

[2017-11-06 02:30:47]
User953894 - Posts: 58
I'm trying to bring in external data and everything seems to have worked well except the time on the chart for the new instrument does not seem to be converting to display local time.

I brought .csv files into the /data folder (I didn't convert, just opened using the New/Open Intraday Chart command) and had no problem opening an intraday chart. The UTC time is what's used in the .csv folder, and that "raw" UTC time appears on the chart(s) for the imported instruments. My other charts show the local time. As far as I can tell, everything is fine except the UTC time is not being converted. This is especially problematic because I am overlaying the imported chart information and the time seems to prevent the overlay information from displaying properly.
[2017-11-06 18:10:00]
Sierra Chart Engineering - Posts: 104368
Whether the data is from a text file or not, the time zone settings will always have an effect on the UTC Date-Times loaded from the chart data file. It is simply an impossibility for that not to be the case. Know that there are two different Time Settings. Refer to:
Time Zone Setting

Also refer to the text/CSV data format here:
Text/CSV Data Format

And make sure the Date-Times have the proper format.


In any case, this is not anything we would provide any further support for.
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-11-06 20:41:32]
User953894 - Posts: 58
http://www.sierrachart.com/image.php?Image=1510000683404.png

I double-checked the format and time settings that you mention. I even did an update of the import, so I have "new" data to confirm that I continue to get the same type of result. I also confirmed that the standard charts use global time setting and the chart produced from the imported csv data also uses global time setting. But while my standard charts properly show current New York time zone time which matches my PC time, the chart for the csv data shows 5 hours ahead.

The data from the csv file seems to be represented perfectly with all data charted against the time for the record. The only problem is that the chart for imported data all so times 5 hours ahead of all my other charts.
[2017-11-06 22:20:55]
Sierra Chart Engineering - Posts: 104368
The only reasonable conclusion is that the data in the data file, is not actually in UTC 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
[2017-11-06 22:24:42]
Sierra Chart Engineering - Posts: 104368
Actually, we see. When you are opening text data directly, the timestamps are not actually adjusted to the time zone setting and are just displayed as is.

Refer to the Notes here about this:

Text/CSV Data Format: Notes
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: 2017-11-06 22:33:23
[2017-11-07 03:56:29]
User953894 - Posts: 58
Thank you for clearing that up. It certainly was frustrating to recheck my setup and not find any problems. The explanation you provided with the last message makes much more sense.

But now the question is how can I fix this to do the overlays on charts with data from my normal feed.
1) I tried changing the time zone on the text data charts to UTC, but that didn't seem to have any effect.
2) I tried changing the global time zone to UTC, which seems to work fine. It's the least preferred option, but it works.
3) Is there a "batch" process for importing data? I have a couple dozen data files to update and I'll explore a full import which would address the time conversion if it can be done with a straightforward automated process.

Thanks again for your clarifying information. I look forward to any thoughts about a better approach.
[2017-11-07 10:18:57]
Sierra Chart Engineering - Posts: 104368
The only possibility is to import the data into Sierra Chart Intraday data files.

Refer to:
Exporting and Importing Intraday Data Files

There is no way to do a batch import.
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-11-07 19:55:40]
User953894 - Posts: 58
Thanks for that info.

I am curious--opening text data directly seems to work fine. What are the advantages (other than using the UTC functionality) of importing vs. opening text data directly?

Again, thanks!
[2017-11-07 20:37:19]
Sierra Chart Engineering - Posts: 104368
When importing the data, it will load much faster. But if you are fine with the current loading time, then that is OK.

We also have contemplated performing an adjustment of the timestamps to the time zone, but if we do that, it is going to cause an unexpected problem for those who have relied on it working the current way. We can always add an option, but it would be yet another option further complicating things.
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-11-08 12:05:26]
User953894 - Posts: 58
I am continually amazed at the functionality you guys provide.

You can add my name as a vote to include the option to do the time conversion on directly read data.
[2017-11-27 11:21:47]
User953894 - Posts: 58
I've starting having stability issues on a Sierra Charts instance that I use against Forex data. I have about 30 .csv files that are read directly to produce charts. The system will work for hours, but then suddenly begin creating messages in the log about a timer loading issue is occurring (My apolgoies, I thought I had captured the specific and full error message but I don't have it at the time of creating this post).

I'm wondering if you have any suggestions on how to address this. Also, I'm considering having a programmer help me format the file in .scid format instead of reading .csv files. I'm wondering will this help/resolve the problem?
[2017-11-27 17:37:34]
Sierra Chart Engineering - Posts: 104368
This is probably a Windows 10 issue no doubt. We have had a few reports of this over the last month. The first thing we recommend doing is to update to the current version of Sierra Chart following these instructions:
Software Download: Fast Update

If you have a continued problem it is going to certainly be a Windows 10 issue.

Also, I'm considering having a programmer help me format the file in .scid format instead of reading .csv files. I'm wondering will this help/resolve the problem?
No, it will not make any difference.
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: 2017-11-27 17:40:55
[2019-02-01 06:22:14]
uM8137 - Posts: 180
One reason why it would be nice to be able to declare the location of the timestamps in an imported data file is that, due to Daylight Saving time changes throughout the year, it isn't possible to correctly work-around the situation when one wants to import a file that has New York City (NYC) time. NYC time is the most common timestamp for US equity data. However, it is a mix of EST (winter; UTC -5) and EDT (summer; UTC -4) timezones.

In this case, one's data is -5 hours part of the year, and -4 hours for the other part of the year (summer when EDT is used in NYC). So the first, obvious workaround doesn't work: one cannot just set the SierraChart global time zone to be +5 or +4 and have the import of a year of data work correctly; because +5 is the correct setting only part of the year.

Hence it would be quite useful, for correctness sake, to have the ability to say that ones import file has timestamps using the local time in a particular location, such as NYC, and have the adjustment to move each specific time point to UTC happen according to when daylight saving time is in effect or not.

Please consider adding such a feature.

To post a message in this thread, you need to log in with your Sierra Chart account:

Login

Login Page - Create Account