WL7-freezes-with-a-12-hour-optimization

You can try to print to log, out of BacktestComplete() or something - this will be per run prints. At least you'll understand more about whether it's after of while.

Hi Replikant_m

Thanks. I will try out.

Hi mrsic,

it's better use

WLHost.Instance.AddLogItem("My Log Viewer Item", "This is what I want to say", Color.Red);

for this.

Hi Replikant_m,

thanks again.

I am not a pro programmer. I am glad that my stuff works with the grateful help in this forum.

BacktestComplete() is method. But this stuff tells me nothing WLHost.Instance...
I think I don't know how to implement in a strategy.

I am now using the finantic.optimizer and it does not freeze there so far and it also works faster.

BacktestComplete() - is "where".

You need to add something like this to your strategy:

CODE:
public override void BacktestComplete()
{
    WLHost.Instance.AddLogItem("My Log Viewer Item", "This is what I want to say", Color.Red);
}

Good news, Build 30 will auto save optimization runs once a minute, allow you to open saved or canceled optimizations, and resume them!

Thanks Replikant_m. I will try this out.

Thanks Glitch. This are good news.

By the way, I like after the Optimization Complete the tab "Tabular" "Run a Backtest with these Parameter Values." That is great for a quick overview for me.

QUOTE:
Good news, Build 30 will auto save optimization runs once a minute, allow you to open saved or canceled optimizations, and resume them!

For the finantic optimizers also?

Of course.

:) I should never have doubted it!