Support Board
Date/Time: Tue, 22 Apr 2025 07:51:33 +0000
Request: Access to ACSIL Market Depth Delete Commands and immediate access to buffers.
View Count: 281
[2024-12-22 19:49:55] |
AndyB - Posts: 105 |
Hi, I have been working on parsing depth files to recreate the depth of market with sub-batch price updates and depth updates fully synchronized. I output these into my own market depth files and matched trades via .scid files for use in Sierra Chart, employing the Historical Market Depth study to read them. Issue with "Extend Last Known Depth" When using the "Extend Last Known Depth" option, I noticed that the depth rectangles extend through the spread when observing granular bid/ask price movements and trades. This behavior doesn't align with realistic depth scenarios. Could you update the logic for this study so that depth rectangles finalize when a delete command is encountered? Depth Visualization and Zero Depth Detection I’ve created a custom depth visualization and found ACSIL Depth Bars to be the most efficient for performance. However, I cannot access a flag for deleted price levels, which makes it challenging to identify when a price level’s depth has been reduced to zero (excluding the spread, as depth cannot exist there in futures). This means I need to go read the file manually, find the associated timestamp, and check to see if there's a delete command. This is essential data in highly volatile scenarios. -Using GetNextHigherPriceTickIndex only outputs price tick indexes with updates (assuming add/modify command records). -DepthDataExistsAt only checks if any depth data exists at a bar index, not whether a price level’s depth is zero. Would it be possible to add functionality for detecting when a price level’s depth has been reduced to zero? Additional Requests -File Positioning Functionality: Could you introduce a DateTimeToFilePosition function that returns the byte offset in depth or .scid files, allowing quick access to specific file locations, if the proposed request cannot be implemented? -Real-Time File Buffer Access (arguably the most important thing for me): I modify depth and .scid files locally and output them back to Sierra Chart. However, the buffer flush rate (minimum 500ms as per documentation) is too slow for algorithmic signaling. Could you enable real-time access to file buffers to reduce latency? Thank you for your assistance. Let me know if you need any further clarification! Best regards |
[2025-01-27 04:17:16] |
AndyB - Posts: 105 |
Any consideration here?
|
[2025-01-30 04:47:21] |
Sierra_Chart Engineering - Posts: 19299 |
No, we do not have time for this. The only thing we can do is reduce this interval: However, the buffer flush rate (minimum 500ms as per documentation) is too slow for algorithmic signaling.
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 |
[2025-01-30 14:36:40] |
AndyB - Posts: 105 |
That would be wonderful. Thank you for the response. How low would you be able to reduce it to?
|
[2025-01-30 22:09:43] |
Sierra_Chart Engineering - Posts: 19299 |
20 ms. This will be out in the next release.
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-01-30 22:45:01
|
[2025-01-31 16:45:40] |
AndyB - Posts: 105 |
best news ive heard all week. thank you so much
|
To post a message in this thread, you need to log in with your Sierra Chart account: