Support Board
Date/Time: Wed, 27 Nov 2024 19:47:50 +0000
Post From: Contradictory Documentation for sc.UpdateStartIndex
| [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). |