Strategy Analyzer/Optimizer Won't Run On Mac/Parallels

[x703jko]

I'm trying to use the NT8 strategy analyzer optimizer on my MacBook Pro using parallels. I have Parallels set up to use all eight intel i9 (2.4 GHz) cores in the Mac along with all 32 GB of memory. However, the optimizer chokes on even a simple optimization problem. After I click run it starts optimizing but just gives up after two seconds with NO error message at all. And, there's nothing in the log.

Can anyone shed light on what's happening or have any advice?

Thanks for reading.

Jeff

[x703jko]

Wait! I was looking in the wrong log file.

Here's what the optimizer gave as an error:

"Strategy 'My Strategy': Error on calling 'OnStateChange' method: Object reference not set to an instance of an object."

Any advice?

Thanks

[NinjaTrader_Jim]

Hello Jeff,

Thanks for your message.

Object reference not set to an instance of an object means there is an object in your code that is null when it is being accessed.

You can use debugging prints to identify the specific line that throws the error.

Debugging Tips - https://ninjatrader.com/support/help...script_cod.htm

Additional information on checking for null references can be found here - https://ninjatrader.com/support/help...references.htm

Optimizations are inherently very resource intensive. This is by design. If your computer has all memory consumed, you will hit stalls for memory to be cleared. I have included some information that explains memory utilization in optimizations, as well as tips for running efficient optimizations below.

Understanding Optimization Memory Utilization

I have created a video demonstrating how the SampleMACrossover strategy, a simple strategy that utilizes IsInStantiatedOnEachOptimizationIteration=false for efficiency, can still quickly utilize memory resources.

Demo — https://drive.google.com/file/d/15pz...w?usp=drivesdk

We should consider the following for memory consumption:

Data * Strategy resources * Number of optimization iterations * Number of trades * Keep best # of results.

As we can see there are a number of factors that are involved and memory utilization can climb very quickly depending on a few of these factors. Once memory gets maxed out, we can experience short freezes where memory is decommitted, stored to disk, and then new resources are committed before the backtest is resumed.

We can easily control the number of iterations involved and we can also consider writing our strategies to use IsInstantiatedOnEachOptimizationIteration = false; (Which requires that we reset class level variables in State.DataLoaded.)

IsInstantiatedOnEachOptimizationIteration — https://ninjatrader.com/support/help...niteration.htm

Optimization Tips — https://ninjatrader.com/support/help...ionPerformance

Walk Forward Optimization — https://ninjatrader.com/support/help...ss_metrics.htm

Genetic Optimization — https://ninjatrader.com/support/help..._algorithm.htm

Please let us know if you have any additional questions.