Support Board
Date/Time: Sat, 23 Nov 2024 03:17:57 +0000
ACSIL initialization issue
View Count: 1917
| [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 |
| [2013-06-14 16:34:02] |
| SoundsLikeSun - Posts: 30 |
|
I also precise I am not in autolooping mode. The study proceeds to a full recalculation from beginning to end (" For loop" , for each sc.Index) |
| [2013-06-17 07:30:26] |
| |
|
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. How many study inputs are you using? 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 |
| [2013-06-17 08:07:18] |
| SoundsLikeSun - Posts: 30 |
|
If you are talking about study inputs available in the settings, just a few (16). However, in the study, there are more than a thousand inputs. I know it's weird, but it appears the study is calculating itself several times. First, I can see it visually, as I see the sc.usetool text tags on the graph change two times in front of me. Second, because my study writes and read values in .csv files. I can see it sometimes write the values two times in the files And for sure, it is not a loop responsible for it. Currently, I avoid the bug by detecting early incoherences in the values and forcing the study to terminate. Then I click again on Ok, and it's fine. I use this study in several windows and several chartbooks. |
| [2013-06-17 22:04:21] |
| |
|
Clearly there is some problem with the functioning of your study. You will have to debug this yourself. We do not provide help with that. If you believe there is a problem with the setting of study inputs by Sierra Chart, then provide us a very simple code example which demonstrates the problem and we will test it. This must be a very simple example to demonstrate the problem. If you are not familiar with step-by-step debugging, please refer to this page: http://www.sierrachart.com/index.php?l=doc/doc_DebuggingDLLs.html 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: 2013-06-17 22:06:00
|
| [2013-06-18 07:54:43] |
| SoundsLikeSun - Posts: 30 |
|
Ok, thank you very much for your help. Definitely, there must be a problem somewhere in my code. I just wanted to know whether you were aware of any initialization issue. I guess I will have now to dig into step by step debugging. I will send you a short piece of relevant code, if I find one. |
To post a message in this thread, you need to log in with your Sierra Chart account: