Support Board
Support Board
Search Board
Control Panel
View My Posts / Threads
Direct MessagesDate/Time: Sun, 28 Apr 2024 22:59:58 +0000
Post From: ACSIL initialization issue
| [2013-06-14 15:41:08] |
| SoundsLikeSun - Posts: 30 |
|
Hi Sierra Team, I have a question that requires some explanation, so please don't be afraid by its length. Fact is that I have a problem with a study I use everyday. It is a study that enables me to simulate trades on the graph. It uses a lot of inputs. For this study I heavily use the sc.Usetool functionality in order to monitor several values directly on the graph. The study used to work fine but suddenly started to bug (sierra charts freezing while calculating the study). So I isolated the program into several parts, in order to detect what the problem is, and here is what I understood, thanks to the sc.usetool. Whenever I change one of the inputs in the study settings (yes no inputs that trigger different parts of the study) the study is recalculated once. On the graph, I can see through the sc.usetool that some values are not working, as they are set to 0 (where they should have another value). Then, when I click again on apply, without changing any yes no input in the settings, the study is recalculated and this time, everything is correct. So, without changing anything, the inputs inside the study get a different value. I precise that I am working offline, so it is not a problem of new data coming from the market. I mean that nothing changed on the graph. I also precise that the yes no inputs i change are not important, as I created several one for testing, that have absolutely no effect on my study. They are just here to trigger the recalculation when changed. So my conclusion is that the first recalculation of the study initializes the inputs with some randomness. But the second recalculation will make everything ok again. It would be fine with me to click "apply" two times, but the problem is that some parts of the study, when enabled, will generate a bug when the initialization is wrong. Sierra will freeze, calculating indefinitely, and I have to shut it down. Therefore, I never have the possibility to recalculate it a second time in order for it to work So, do you have an idea what the problem could be, as maybe you are aware of this double initialization issue ? I hope my question is clear enough, and I am sorry that it is so long. Thank you very much for your help Best regards, Thomas |