Support Board
Date/Time: Fri, 12 Dec 2025 09:43:35 +0000
Post From: Upcoming Development and Internal Number Precision Improvement Project
| [2025-12-12 03:20:32] |
| Sierra_Chart Engineering - Posts: 21806 |
|
Another major long-overdue task, that we must do, is that Sierra Chart must support fractional volume/trade/size values. For example US stock market data, from NASDAQ will begin to trade in fractional quantities in February 2026. This is already supported for Market depth data, and it is supported for Trading quantities but it is not supported, for market data volumes for trades. This is also necessary for crypto currency exchanges. We have to go from an integer to a double precision floating point value. This is extensive work which will take 1-2 months. The Intraday data file format will also be adapted to support this. Another critical thing related to the above, is that the internal storage of data within charts needs to go from 4 byte floats to 8 byte double precision floats. This will also improve accuracy with studies. All of the above, will cause incompatibility with ACSIL studies and they will need to be recompiled. This will just be a recompile but inevitably there will be warnings that the compiler will generate. Like for example if you are assigning a value from a Subgraph Data array into a four byte float, then there will be a warning about loss of precision. This can be ignored. Generated DLLs will probably have this new suffix appended after these changes _64D rather than _64. D means double. These changes will increase the memory use of Sierra Chart. The increase would be estimated to be about 80 to 90% more. We would recommend, that a system is equipped with a minimum of 32 GB . This is far more than anything Sierra Chart would ever need, but we just recommend having this amount of memory in a computer system at a minimum. We are thinking in terms of a desktop system. Or a server. We do not believe there will be any performance degradation with the above changes. And once these changes are deployed, it will break compatibility with existing DLLs and they will need to be recompiled and we are not going to be supporting in the current versions, two different interfaces for ACSIL or different versions. Newer versions will simply support the single interface which is updated to use double values. 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, use the Teton service: Sierra Chart Teton Futures Order Routing Date Time Of Last Edit: 2025-12-12 03:56:16
|