Support Board
Date/Time: Sun, 22 Dec 2024 19:42:14 +0000
Chartbook causes infinite loading loop
View Count: 1226
| [2015-05-18 04:06:16] |
| i960 - Posts: 360 |
|
GBM-201506-DTB [CBV] 240 Min #2 | Symbols used for continuous contract chart: | 2015-05-17 21:03:08
HRZ14 | 2015-05-17 21:03:08 GBM-201503-DTB | 2015-05-17 21:03:08 GBM-201506-DTB | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: Checking for volume based rollover dates. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: Volume based rollover from GBM-201412-DTB to GBM-201503-DTB occurs at 2014-12-04 | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: Volume based rollover from GBM-201503-DTB to GBM-201506-DTB occurs at 2015-03-04 | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: Performing continuous futures contract back adjustment calculations. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: GBM-201412-DTB Open price on 2014-12-04 is 128.26. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: GBM-201503-DTB Open price on 2014-12-04 is 129.59. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: GBM-201412-DTB price difference to GBM-201503-DTB is 1.33. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: GBM-201503-DTB Open price on 2015-03-04 is 130.99. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: GBM-201506-DTB Open price on 2015-03-04 is 129.17. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: GBM-201503-DTB price difference to GBM-201506-DTB is -1.8200001. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: Back adjust amount for symbol GBM-201412-DTB is -0.49000001. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: Back adjust amount for symbol GBM-201503-DTB is -1.8200001. | 2015-05-17 21:03:08 Chart #5 is performing a full recalculation because it has been tagged. Chartbook: fly_busted.cht | 2015-05-17 21:03:08 Chart #2 has tagged chart #5 for full recalculation. Chartbook: fly_busted.cht | 2015-05-17 21:03:08 Chart #2 has tagged chart #6 for full recalculation. Chartbook: fly_busted.cht | 2015-05-17 21:03:08 Chart #2 has tagged chart #5 for full recalculation. Chartbook: fly_busted.cht | 2015-05-17 21:03:08 Chart #2 has tagged chart #6 for full recalculation. Chartbook: fly_busted.cht | 2015-05-17 21:03:08 Chart #6 is performing a full recalculation because it has been tagged. Chartbook: fly_busted.cht | 2015-05-17 21:03:08 Chart #5 is performing a full recalculation because it has been tagged. Chartbook: fly_busted.cht | 2015-05-17 21:03:08 Chart Settings have been synchronized between Destination chart number #5 and Source data chart number #2. Performing a chart reload of source data chart. | 2015-05-17 21:03:08 Date rule based rollover from GBM-201412-DTB to next contract occurs at 2014-12-08. | 2015-05-17 21:03:08 Date rule based rollover from GBM-201503-DTB to next contract occurs at 2015-03-06. | 2015-05-17 21:03:08 Date rule based rollover from GBM-201506-DTB to next contract occurs at 2015-06-08. | 2015-05-17 21:03:08 Checking Intraday data file for symbol GBM-201412-DTB for the date range from 2014-09-08 to 2014-12-08. | 2015-05-17 21:03:08 Checking Daily data file for symbol HRZ14 for the date range from 2014-09-08 to 2014-12-08. | 2015-05-17 21:03:08 Checking Intraday data file for symbol GBM-201503-DTB for the date range from 2014-12-08 to 2015-03-06. | 2015-05-17 21:03:08 Checking Daily data file for symbol GBM-201503-DTB for the date range from 2014-12-08 to 2015-03-06. | 2015-05-17 21:03:08 Checking Intraday data file for symbol GBM-201506-DTB for the date range from 2015-03-06 to 0. | 2015-05-17 21:03:08 Checking Daily data file for symbol GBM-201506-DTB for the date range from 2015-03-06 to 2015-05-15. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2 | Symbols used for continuous contract chart: | 2015-05-17 21:03:08 HRZ14 | 2015-05-17 21:03:08 GBM-201503-DTB | 2015-05-17 21:03:08 GBM-201506-DTB | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: Checking for volume based rollover dates. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: Volume based rollover from GBM-201412-DTB to GBM-201503-DTB occurs at 2014-12-04 | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: Volume based rollover from GBM-201503-DTB to GBM-201506-DTB occurs at 2015-03-04 | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: Performing continuous futures contract back adjustment calculations. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: GBM-201412-DTB Open price on 2014-12-04 is 128.26. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: GBM-201503-DTB Open price on 2014-12-04 is 129.59. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: GBM-201412-DTB price difference to GBM-201503-DTB is 1.33. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: GBM-201503-DTB Open price on 2015-03-04 is 130.99. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: GBM-201506-DTB Open price on 2015-03-04 is 129.17. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: GBM-201503-DTB price difference to GBM-201506-DTB is -1.8200001. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: Back adjust amount for symbol GBM-201412-DTB is -0.49000001. | 2015-05-17 21:03:08 GBM-201506-DTB [CBV] 240 Min #2: Back adjust amount for symbol GBM-201503-DTB is -1.8200001. | 2015-05-17 21:03:08 Chart #2 has tagged chart #5 for full recalculation. Chartbook: fly_busted.cht | 2015-05-17 21:03:09 Chart #2 has tagged chart #6 for full recalculation. Chartbook: fly_busted.cht | 2015-05-17 21:03:09 Chart #2 has tagged chart #5 for full recalculation. Chartbook: fly_busted.cht | 2015-05-17 21:03:09 Chart #2 has tagged chart #6 for full recalculation. Chartbook: fly_busted.cht | 2015-05-17 21:03:09 Chart #6 is performing a full recalculation because it has been tagged. Chartbook: fly_busted.cht | 2015-05-17 21:03:09 Chart Settings have been synchronized between Destination chart number #6 and Source data chart number #2. Performing a chart reload of source data chart. | 2015-05-17 21:03:09 Date rule based rollover from GBM-201412-DTB to next contract occurs at 2014-12-08. | 2015-05-17 21:03:09 Date rule based rollover from GBM-201503-DTB to next contract occurs at 2015-03-06. | 2015-05-17 21:03:09 Date rule based rollover from GBM-201506-DTB to next contract occurs at 2015-06-08. | 2015-05-17 21:03:09 Checking Intraday data file for symbol GBM-201412-DTB for the date range from 2014-09-08 to 2014-12-08. | 2015-05-17 21:03:09 Checking Daily data file for symbol HRZ14 for the date range from 2014-09-08 to 2014-12-08. | 2015-05-17 21:03:09 Checking Intraday data file for symbol GBM-201503-DTB for the date range from 2014-12-08 to 2015-03-06. | 2015-05-17 21:03:09 Checking Daily data file for symbol GBM-201503-DTB for the date range from 2014-12-08 to 2015-03-06. | 2015-05-17 21:03:09 Checking Intraday data file for symbol GBM-201506-DTB for the date range from 2015-03-06 to 0. | 2015-05-17 21:03:09 Checking Daily data file for symbol GBM-201506-DTB for the date range from 2015-03-06 to 2015-05-15. | 2015-05-17 21:03:09 The tagging/ref-counting might want to consider the concept of "depth" as it's ending up in a situation where it cannot detect a loop. I'm simply trying to create another chart for a 2nd spread, of which an existing chart in the same chartbook also uses the same source chart causing the entire thing to flip out and constantly reload 2 charts continuously making it unusable. (Yes, I realize there are spread butterfly and spread 3/4 chart studies - that's not the point as it doesn't have anything to do with the type of spread I'm charting) Date Time Of Last Edit: 2015-05-18 04:10:31
|
 fly_busted.cht - Attached On 2015-05-18 04:05:22 UTC - Size: 165.98 KB - 425 views |
| [2015-05-18 06:00:15] |
| |
|
You have an obvious configuration problem here where you have 2 charts of different time frames per bar referring to the same source chart. Refer to help topic 30.3 here: https://www.sierrachart.com/index.php?page=doc/helpdetails30.html#h30.3 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 |
| [2015-05-18 06:10:21] |
| i960 - Posts: 360 |
|
Did you even open the chartbook or just assume it was that problem? Every single chart in that chartbook is using 240 minute bars. I'm well aware of the other problems it causes to have mismatched times with 2 separate references and that isn't it in this case.
Date Time Of Last Edit: 2015-05-18 06:11:07
|
| [2015-05-18 06:17:41] |
| |
|
We do not need to look at the Chartbook because we understand the problem. If it is not the timeframe per bar, then it is another dependent chart setting, like the Days to Load.
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: 2015-05-18 06:18:15
|
| [2015-05-18 06:24:16] |
| i960 - Posts: 360 |
|
Nope, that ain't it either. You're assuming you once again to immediately know the problem and that the user is at fault. Days to load is 180 days in every single chart.
|
| [2015-05-18 06:46:03] |
| |
|
We are not understanding the purpose of the continued questions. There is some other setting then. And the answer is the same. What is your objective? 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 |
| [2015-05-18 06:54:44] |
| i960 - Posts: 360 |
|
So what you're telling me here is that it's my problem, it's "some other setting," the software is without any problems, and that I should just randomly keep changing things until it stops trying to load charts in an infinite loop? Yes, the answer is the same: it's a bug; but once again you won't take ownership. You already know this section of the software is brittle and prone to problems, pushing it back on me isn't going to make that problem go away. |
| [2015-05-18 07:39:17] |
| |
|
Your response is puzzling to us. However, after contemplating it, we think that the reason for it is you did not understand what the help topic was explaining. We have clarified it. Help topic 30.3 explains that you need to set up another source chart which a destination chart can reference. This is the proper solution. Once again here it is: https://www.sierrachart.com/index.php?page=doc/helpdetails30.html#h30.3 There is no bug here. You already know this section of the software is brittle and prone to problems, pushing it back on me isn't going to make that problem go away. No, we are not aware of this. The help topic only explains a scenario which can develop due to an improper configuration.The documentation has also been updated to explain the different chart settings which will cause a reload in this case. 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: 2015-05-18 10:09:30
|
| [2015-05-18 07:40:34] |
| i960 - Posts: 360 |
|
I think the way you treat your paying customers is downright rude. You have this twisted attitude that users reporting issues are out to annoy or harass you in someway and that the user by default is wrong. What you fail to remember is that the users reporting bugs are simply doing it because they want to make the software BETTER and not necessarily turn it into their own personal feature catalog. Without users reporting issues regularly you're at the mercy of finding them yourself and potentially running into other issues down the line from people not speaking up when they should have. If every interaction is like pulling teeth the users will just not bother at a certain point and ultimately the product suffers as a result. I rarely ask for features and I regularly report outages and other issues the second I see them helping you to keep the software stable and reliable. When I report issues and am treated like crap over it its just straight up unreasonable. Some of us have professional developer experience in both approach and even the same languages the software is written in. We know how to report bugs and we know what is a user land issue and a software/vendor issue before reporting it. Date Time Of Last Edit: 2015-05-18 07:41:51
|
| [2015-05-18 07:43:12] |
| |
|
You are entitled to your own opinion. We do not agree. The way you are treating us is quite poor. 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: 2015-05-18 07:45:02
|
| [2015-05-18 07:47:18] |
| i960 - Posts: 360 |
|
No I don't need a refund. I believe in the software and my aim is to help here. I am not the only one SC support treats like this - come on now be honest with yourself there has been a history of these type of exchanges with support and users. From the beginning of the thread you kept telling me it was this problem or that problem of which none of those were the problem and I kept reiterating that. Attitude goes both ways here and you need to have a better perception of those users who just want selfish changes and those users who are here because they believe in the product (which I do).
|
To post a message in this thread, you need to log in with your Sierra Chart account: