Support Board
Date/Time: Wed, 27 Nov 2024 19:29:37 +0000
Contradictory Documentation for sc.UpdateStartIndex
View Count: 333
| [2023-07-17 04:46:09] |
| User208107 - Posts: 13 |
|
#1: During normal chart updating sc.UpdateStartIndex will always be equal to the last index of the prior sc.ArraySize before the chart update.
(https://www.sierrachart.com/index.php?page=doc/ACSIL_Members_Variables_And_Arrays.html#scUpdateStartIndex:~:text=During%20normal%20chart%20updating%20sc.UpdateStartIndex%20will%20always%20be%20equal%20to%20the%20last%20index%20of%20the%20prior%20sc.ArraySize%20before%20the%20chart%20update.)#2: The call into the study function will just be an update call with [sc.UpdateStartIndex] set to the prior array size.
(https://www.sierrachart.com/index.php?page=doc/ACS_ArraysAndLooping.html#WhenTheStudyFunctionIsCalled:~:text=The%20call%20into%20the%20study%20function%20will%20just%20be%20an%20update%20call%20with%20sc.Index/sc.UpdateStartIndex%20set%20to%20the%20prior%20array%20size.)If there is a chart update without a new bar, according to #1, sc.UpdateStartIndex = sc.ArraySize - 1; according to #2, sc.UpdateStartIndex = sc.ArraySize. If there is a chart update with a new bar, according to #1, sc.UpdateStartIndex = sc.ArraySize - 2; according to #2, sc.UpdateStartIndex = sc.ArraySize - 1. |
| [2023-07-17 08:33:02] |
| Sierra_Chart Engineering - Posts: 17198 |
|
We will correct number 2. : The call into the study function will just be an update call with [sc.UpdateStartIndex] set to the prior array size minus 1.
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 |
| [2023-07-17 10:44:12] |
| User208107 - Posts: 13 |
|
Thanks. Also, could you elaborate on the option you mention here: While technically there is an option to cause a study function to be called at every market data update, that is simply something which is impractical and leads to problems.
(https://www.sierrachart.com/index.php?page=doc/ACS_ArraysAndLooping.html#WhenTheStudyFunctionIsCalled:~:text=While%20technically%20there%20is%20an%20option%20to%20cause%20a%20study%20function%20to%20be%20called%20at%20every%20market%20data%20update%2C%20that%20is%20simply%20something%20which%20is%20impractical%20and%20leads%20to%20problems.)I have a lean ACSIL algorithm that will only run once for every new bar. If this option would enable me to override the minimum 10ms chart update interval and call the study function every n market updates (or even every 5ms), the extra speed in reacting to new bars would relatively benefit my fills a lot. Likewise for a way to override the minimum 10ms remote buffer delay, but I didn't see anything in the documentation about lowering that (besides the DTC protocol). |
| [2023-07-17 11:11:11] |
| Sierra_Chart Engineering - Posts: 17198 |
|
That option is no longer available. We will remove that sentence. There is no way to get faster updates than 10 ms and the DTC protocol server is no longer an option for that. 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: 2023-07-17 11:11:26
|
To post a message in this thread, you need to log in with your Sierra Chart account: