Here you go Big Mike....thanks

Hi, dose the video show any thing?

sometimes back i have a situation where i used ChartControl.BarsMarginRight in the Plot override in one of my indicator. it resulted in delayed quotes/ ninja freezing (incl dom etc).

remove the indicators and see if the situation still persists. if not then put on the indicators one by one and try to isolate the rouge indicator.

Problems like this can be caused


-> by a corrupted workspace (please close all workspaces and recreate your trading workspace)

-> by custom indicators, which are not coded properly (please remove all non-system indicators from your workspace)

-> by running indicators in mode CalculateOnBarClose = false (please set most of your indicators to CalculateOnBarClose = true)

-> by having selected a display update interval < 0.5 sec for the chart (please set your display update to 0.5 sec)

bukkan 

sometimes back i have a situation where i used ChartControl.BarsMarginRight in the Plot override in one of my indicator. it resulted in delayed quotes/ ninja freezing (incl dom etc). remove the indicators and see if the situation still persists. if not then put on the indicators one by one and try to isolate the rouge indicator.

Yes that was it plain charts and all is well. thanks

Fat Tails 

Problems like this can be caused -> by a corrupted workspace (please close all workspaces and recreate your trading workspace) -> by custom indicators, which are not coded properly (please remove all non-system indicators from your workspace) -> by running indicators in mode CalculateOnBarClose = false (please set most of your indicators to CalculateOnBarClose = true) -> by having selected a display update interval < 0.5 sec for the chart (please set your display update to 0.5 sec)

Thank you, the...... CalculateOnBarClose = true) was the main problem....

samiotis 

Thank you, the...... CalculateOnBarClose = true) was the main problem....

Hahaha, we got you.


Setting indicators to "CalculateOnBarClose = false" means that every single incoming tick triggers a complete recalculation.

If you have an indicator such as the VWAP from the NinjaTrader forum or any other indicator which performs complex calculations, that would kill any piece of software.

Fat Tails 

Hahaha, we got you. Setting indicators to "CalculateOnBarClose = false" means that every single incoming tick triggers a complete recalculation. If you have an indicator such as the VWAP from the NinjaTrader forum or any other indicator which performs complex calculations, that would kill any piece of software.

Yes I repopulated the charts with some of the barowd indicators to bar close=true and walla.............thanks to all of you again......

I have LOTS of indicators calculating on every tick, they load fast, and my charts do not lag.

Generally indicators that perform poorly when COBC is false are poorly coded with horrible programming practices such as:

• Failing to provide error handling.
• Doing things that only need to be done once per bar on every tick, especially calling loops like MIN and MAX.
• Failing to use predefined instances of external indicators, instead creating, destroying, and recreating ad-hoc local instances on every tick.

These bugs apply to many of the out of the box indicators that come with Ninjatrader.

There was a thread on this subject, but oh, how soon we forget. Start at Post #28. Note the input from "Richard" of movethemarkets.com, an expert programmer whose ideas got the whole discussion started.

Anyone have any hints for optimizing C# code? Anyone have any hints for optimizing C# code? Currently using Visual Studio for C#. Want to run some indicators through the process to see if there are any excessive computational issues.

Even now, it is very unusual to find indicators that don't have one or more of the problems mentioned.



In general, having to set COBC to false is a pathetic bandaid attempt to make up for really lousy, mindless programming.

Zondor 

I have LOTS of indicators calculating on every tick, they load fast, and my charts do not lag. Generally indicators that perform poorly when COBC is false are poorly coded with horrible programming practices such as: Failing to provide error handling. Doing things that only need to be done once per bar on every tick, especially calling loops like MIN and MAX. Failing to use predefined instances of external indicators, instead creating, destroying, and recreating ad-hoc local instances on every tick. In general, having to set COBC to false is a pathetic bandaid attempt to make up for really lousy, mindless programming.

Yes, I am guilty to have published some indicators, which are not doing well with CalculateOnBarClose = false, as this setting is not really required for them.

I agree that there are lots of things that still can be improved.