Login Page - Create Account

Support Board


Date/Time: Tue, 23 Apr 2024 06:29:28 +0000



[Programming Help] - Chartbook Charts unnecessarily tagged for full recalculation issue?

View Count: 1146

[2020-11-25 07:49:42]
User92573 - Posts: 477
Dear Support

I'm experiencing unexpected log entries - and charts tagged for full recalculation?

I have noticed that when I update studies, e.g. (show/hide) even a Simple MA on a chart in the chartbook the linked/associated studies (same symbol) are tagged for full recalculation as expected but at the same time many (not all) of the other charts are also being unnecessarily tagged for full recalculation.

In most of the cases I have monitored, it is the chart numbers that follow the one being updated that are tagged e.g. show/hide a study on chart #48, tags #48 and above. The same action on chart #1, seems to tag chart #1 and above for full recalculation. This is why I feel there is some form dependency being retained when charts are duplicated?

These are different symbols and not linked to the chart being updated. The only two common elements is that they were created using the 'duplicate chart' option in the chart menu and 'apply study collection' >> after which the symbols, links and references where applicable were changed/updated.

Could there be a legacy issue or retention of some parameters whereby Sierra Charts believes the link still exists?

I have noticed this in the past and rather than deleting all charts/studies and starting again from scratch as I've done previously, is there a solution to remove any unnecessarily retained dependencies?

Many thanks
Date Time Of Last Edit: 2020-11-25 08:04:18
[2020-11-25 09:11:00]
Sierra Chart Engineering - Posts: 104368
This is explained here:
High CPU Usage | Inactive User Interface | Poor Performance | Long Time to Load Chart Data | Charts Reloading Often: 30.9 References to Other Charts / Continuous Full Recalculation of Charts
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
[2020-11-25 11:03:51]
User92573 - Posts: 477
Dear Support

This is still causing major issues as I'm noticing that full recalculation occurs even when changes have not been made. This results in everything such as scrolling, changing chart focus etc. to almost freeze - certainly to a point the charts are unworkable until the recalculation has completed.


I've already been through the suggested section in detail and resolved that as you suggest its definitely down to charts that reference other charts.

Not Study Collections AND not Duplicate Chart.


The study is based entirely on Sierra Charts own example which is presented as the correct way to program this specific study, and which can be found in:

Studies8
SCSFExport scsf_ReferenceDataFromAnotherChart(SCStudyInterfaceRef sc)


So I had assumed this example would already deal with any possible issues it may create as a result of its use.

Would you please review the example study to ascertain why SC's own example is causing the "tagged for full calculation" on even a small number of charts - unless of course this is a required action.

That would help me enormously.

Many thanks



PS Even making changes to a chart (such as hide/show a study) that 'does not' include any study which references another chart - will cause a "tagged for full recalculation" of all charts in the chartbook 'that do' have studies reference by other charts.


The biggest issue has to be re-calculation without any user event having been made. This can have a real impact when trading and the chartbook itself decides it needs to complete a full-recalculation.



Thanks again. Great Support/Platform!
Date Time Of Last Edit: 2020-11-26 12:38:56
[2021-03-14 16:28:11]
User791263 - Posts: 151
User92573, what version are you on?
Have you tried the exact same chartbook/charts on an older version, such as pre V2011?
SC reversed their long-touted great feature that you could run older versions, however,-- trying your charts on pre-V2010 might show if your problem is related to SC's recalc "improvement" like mine was.
(Edit: Note that Chartbooks changed file format around v2094, so a test version prior to that would need to use the backup chartbooks made by the SC upgrade "Chartbooks saved in [2104]version are not compatible with version 2092 and earlier, however a backup of the version of your Chartbooks before this file format change is made. 'Backup2092' ")

When SC "improved" recalculation around Version V2010-V2012, my previously great-working 47-chart system-- quit working. Like yours, it went into constant massive recalculation.

Since many of my charts flow down through 4 or 5 charts, that ruined about 2 years of my work and I am stuck on V1992. I can't upgrade because there's no way for me to find, change or correct what worked fine before... and has no #CircRef errors, and had none prior where it did brief recalculations only one-time on a few and then ran fast on V1992.

For near 3-months I still wait for my polite logical rebuttal points to be addressed.
There should be a choice of recalc routines (pre or post-V2012), and a way to simply turn off recalculation; I looked and there are no #CircRef logic errors in any related spreadsheet columns.

Now SC is taking away the main reasons AMP used to sell us on Sierra. See the top 3 Platforms still say "Free" and was recommended by AMP: https://www.ampfutures.com/platforms/
Date Time Of Last Edit: 2021-03-14 17:39:12
[2021-03-15 16:14:35]
User92573 - Posts: 477
Hi, I'm using V2229.

I have a number of chartbooks open, each comprises 80 charts and includes a number of years data in each chart. Despite this, I have only one instance of Sierra running. As with your setup my studies also drill down through a number of charts to derive what I want to see/present.

Initially, I had a lot of recalculation issues 'and crashing' that were literally making me climb the walls with frustration. However, after re-evaluating and reprogramming all of my studies to be more efficient, or for that matter just efficient full stop - I finally resolved all the issues. To be honest it was almost entirely due to poor programming on my part and to some degree possibly hardware.

In summary, Sierra really is a very powerful platform and over more than 20 years and several platforms including Signal Writer, Omega 2000i, TradeStation, FT, eSignal, NT and others I've found nothing as flexible or fast.

I do have a moan at Sierra Support/Engineering from time to time but to be honest they 'almost' always reply and the issues are either resolved in a few versions, or they point out it's most likely the result of my programming. Of course, like many, I always tend to point my finger elsewhere right up until I realise it is me and not Sierra after all. :-) There are not many platforms where the developers even bother to come back to you - irrespective of cost.

I can appreciate your frustration especially as some of the custom studies which set out to provide what I think you are trying to achieve are not especially efficient. Only my thoughts of course.

With the benefit of hindsight, if it was me in your position I'd update to the latest version, re-evaluate all of my study code and recompile to 64 Bit. Finally, I time everything that I change so that the changes can be evaluated and SC V2229 loads my studies, charts and data, significantly faster than any previous versions - i.e. those I had always considered to be more efficient as a result of being less complex.

I hope the fact I am loading more charts, multiple chartbooks and some fairly complex chart overlays helps with your dilemma.

Good luck!
Date Time Of Last Edit: 2021-03-15 16:15:27
[2021-03-16 01:56:39]
User791263 - Posts: 151
My setup is likely different; You don't have mostly 2 to 4-second and longer charts with complex spreadsheet formulas in 12 spreadsheets, each with multiple charts? I owned TradeStation too; No, it can't do what SC does.

No recalculation is needed or wanted when charts are set 200 to 450 msec in fast 1-second intraday feed. I tuned and staggered each chart's time to avoid recalcs, then v2011 blew it away.

Opposite your blame of "custom studies", I mostly use canned studies. My only small custom one is based mostly on a canned study, little different but works better. When I use that instead of the canned "Study Overlay", I don't get recalculation from that study.

I think this happens because the charts are often on the same spreadsheets.

Grant me 4 things:
- No unneeded improvement should cause what worked great-- to quit; resources waste soared.
- My clear rebuttals including that point.. are due being briefly addressed in a point-by-point "responsive" reply.
- SC effort on making SC work in more-demanding/complex set-ups like ours is a benefit to SC and all users, as tests and benchmarks.
- Users should get an option to shut off recalculation or choose a prior routine that worked; Recalculating 12 charts of 300msec 5 times per second is a total waste of resources/ counterproductive. (thanks User92573)
Date Time Of Last Edit: 2021-03-16 01:56:56
[2021-03-17 10:46:07]
User92573 - Posts: 477
I don't disagree with any of your points. I would add however that I moved a lot of my work, or least whatever was possible into ACSIL studies as opposed to either the old/new spreadsheets. The result and change in performance was huge. In fact, the workload was too much, or too intensive for the spreadsheet solution which either locked or slowed to the point of being little, or no use. No disrespect to SC I was just asking too much - but much like you earlier versions did seem for whatever reason to be more capable?

I'm not sure on reflection how engineering would deal with preventing recalculation when when one chart references one or more, other charts and timeframes? It must be a real headache for you especially as your charts are refreshing much faster than mine and not least as it was working in earlier versions. I wish I could help more. My solution was in moving to studies as opposed to 'all' spreadsheets' and refining my code.

Good luck!

To post a message in this thread, you need to log in with your Sierra Chart account:

Login

Login Page - Create Account