NT runs Initialize() of ALL Strategies at once

[Lost Trader]

I find it a little weird that, when the Strategies window is opened, NT executes ALL the Initialize() methods of ALL the Strategies, even when they are NOT selected (or added). Specifically, when the window is opened from a chart so a strategy can be added to the chart.

It is somewhat frustrating to see their print stmts show up in the output window when they are NOT being executed.

Is this behavior by design?

[NinjaTrader_RyanM1]

Hello Lost Trader,

Yes, this is by design. When you're choosing a strategy to run it processes Initialize() so that it can load the list.

If you want some items to process only once you can place in the first bar of OnBarUpdate

if (CurrentBar == 0)
{
//startuplogic here
}

NinjaTrader 7 has a new method OnStartup() for this.

[Lost Trader]

No, what I wanted was to stop the strategies which are NOT running from cluttering up my output window! Oh well...

I guess I can individually edit their Initialize() functions so that they are not so noisy!

[NinjaTrader_RyanM1]

I see. Yes, you would want to minimize Print() statements from the Initialize if you're getting too much in the output window.

[Lost Trader]

Hmmm.
If a strategy is actively running on a chart, and I open the Strategies window just to check my settings w/o changing anything, won't NT automatically running Initialize() in the middle of an executing strategy really screw it up?

[NinjaTrader_Bertrand]

LostTrader, calling the Intialize() across strategies will not affect the running Strategy instance adversely.

[Lost Trader]

I am surprised, Bertrand. Because it is CLEARLY calling the Initialize() which resets certain variables and targets. I can see the output & Trace stmts of my active strategy's Initialize() appear in the output window.

I would suggest that y'all only execute the Initialize() if I click on a Strategy in the selection window.... That way there is no doubt & no extra unnecessary processing.

BTW, this is on 6.5

[NinjaTrader_Bertrand]

LostTrader, we advise that sensitive logic should not be placed in the Initialize() method, instead please use the first OnBarUpdate() call (CurrentBar == 0) if you're working with 6.5 and CalculateOnBaClose = true (for false add a check for FirstTickOfBar as well then).