Has anyone got their code to have the 2 different settings of CalculateOnBarClose working on some part of their indicator?

I have a code that HAS to have CalculateOnBarClase = true.

I now have decided to add to the code.

However, the new additions to code, would need it to run CalculateOnBarClose = false, while the rest of the code needs to
run CalculateOnBarClose = true.

How do I get to have only a certain section of code to run on CalculateOnBarClose = false, while the other is on CalculateOnBarClose = true?

victorg20013 

Has anyone got their code to have the 2 different settings of CalculateOnBarClose working on some part of their indicator? I have a code that HAS to have CalculateOnBarClase = true. I now have decided to add to the code. However, the new additions to code, would need it to run CalculateOnBarClose = false, while the rest of the code needs to run CalculateOnBarClose = true. How do I get to have only a certain section of code to run on CalculateOnBarClose = false, while the other is on CalculateOnBarClose = true?

Use the 'FirstTickOfBar' variable (NT7). ('IsFirstTickOfBar' in NT8)

When it's true you then know that the previous bar just closed and the new bar is just opening (i.e effectively the same as running code with CalculateOnBarClose = true), otherwise it's any old tick in a forming bar. But do also check that the barsAgo subscript [e.g. 0/1] is then appropriate depending on what you want to do, (i.e. [0] for the new bar, [1] for the just closed bar.)

[and use CalculateOnBarClose = false so you then have the choice, and NB this is no use in backtesting, which always runs on COBC = true anyway]

Cheers

victorg20013 

Has anyone got their code to have the 2 different settings of CalculateOnBarClose working on some part of their indicator? I have a code that HAS to have CalculateOnBarClase = true. I now have decided to add to the code. However, the new additions to code, would need it to run CalculateOnBarClose = false, while the rest of the code needs to run CalculateOnBarClose = true. How do I get to have only a certain section of code to run on CalculateOnBarClose = false, while the other is on CalculateOnBarClose = true?

It has to be True or False but not both.
Hard to say more with more details but you may have a logic error somewhere.

ratfink 

Use the 'FirstTickOfBar' variable (NT7). ('IsFirstTickOfBar' in NT8) When it's true you then know that the previous bar just closed and the new bar is just opening (i.e effectively the same as running code with CalculateOnBarClose = true), otherwise it's any old tick in a forming bar. But do also check that the barsAgo subscript [e.g. 0/1] is then appropriate depending on what you want to do, (i.e. [0] for the new bar, [1] for the just closed bar.) [and use CalculateOnBarClose = false so you then have the choice, and NB this is no use in backtesting, which always runs on COBC = true anyway] Cheers

I tried the firsttickofbar bool and I get logic errors.
Thanks tho.

I wonder if anyone has ever been able to effectively do it.

victorg20013 

I tried the firsttickofbar bool and I get logic errors. Thanks tho. I wonder if anyone has ever been able to effectively do it.

Saying 'logic errors' doesn't help much, it's used often and works fine, e.g with CalculateOnBarClose set to false, then in OnBarUpdate:

 

Code

if (FirstTickOfBar) { // here we get only the first tick of every bar // so process e.g. Close[1] or whatever you want from the previous closed bar } else { // here we get all other remaining ticks in each bar // so process Close[0] or whatever you want to do in the still forming bar } // here we get every tick in the bar, first and subsequent

However, like I said, it's no use in backtesting, and of course you can get logic errors from a gazillion things, it's usually us that puts them in. It is worth spending time learning C#, using the NT help guide and looking at running code in the download section or on the Ninja support forum, remember NT7 v NT8 differences if appropriate.

Don't ever underestimate the value of a simple 'Print' statement either. Very little software can't have a bug shown up with one of those.


Cheers