Support Board
Date/Time: Wed, 15 Jan 2025 16:11:45 +0000
recalculation during run time
View Count: 889
| [2017-07-27 08:44:14] |
| jizzary - Posts: 177 |
|
Hi During runtime I see recalculation events which has not caused by a user nor by the studies What is causing these events at the course of regular trading time ? Is there a way to block them ? Tnx |
xx-01.PNG| [2017-07-27 14:08:20] |
| |
|
This is explained here: Chart Studies: References to Other Charts and Tagging No you cannot block these. 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-07-30 21:47:58] |
| jizzary - Posts: 177 |
|
sorry to go back. I have study A (on chart #1) that is merely reading persistant data from study B (ob chart #3) why forcing it going thru recalculation. study A is the one that makes trading decision - and it definitely doesn't need the recalculation. vice versa, it just complicates things. will be great if you can support thru ACSIL subgraph settings to ignore recacluation in case of being tagged pls consider. tnx Date Time Of Last Edit: 2017-07-30 21:49:12
|
| [2017-07-31 02:40:28] |
| |
|
is merely reading persistant data from study B (ob chart #3) Any recalculation on this chart will cause chart 1 to be recalculated. So you need to understand why chart 3 is being recalculated.
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-07-31 08:27:59] |
| jizzary - Posts: 177 |
|
I think that your conclusion for this specific case is untrue Study-A has all the abilities to manage changing data on study-B persistent data Further, no subhraph other than study-A depends on study-B's data Therefore, I'm sure there is no need for recalculation Since I understand that you can't support every study's needs, I think the best way is to give means that the study developer can use. What I suggest is a control flag thru ACSIL I/F - to allow block any recalculation if this is true for study needs. In this case recalculation mechanis, will skip recalculating a tagged study for recalculation. I don't want to further waste your time on this issue. I think it is a righr attitude. If you agree to adapt it it will be of assistance. Tnx. |
| [2017-08-12 03:58:21] |
| |
|
In regards to: What I suggest is a control flag thru ACSIL I/F - to allow block any recalculation if this is true for study needs. In this case recalculation mechanis, will skip recalculating a tagged study for recalculation. In the next release this variable will be added to accomplish this: sc.MaintainReferenceToOtherChartsForPersistentVariables You will want to set it to 0. 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-08-12 03:58:46
|
| [2017-08-14 09:46:17] |
| jizzary - Posts: 177 |
|
I'm glad I have the opportunity to contribute to this great platform.
|
To post a message in this thread, you need to log in with your Sierra Chart account: