bury1992
13 Jun 2020, 17:51

RE:

PanagiotisCharalampous said:

Hi Wojtek,

No there is no fix yet.

Best Regards,

Panagiotis 

Join us on Telegram

 

I did some small research and i've noticed that, although some values in my bot are used only in thread-safe mode (using Interlocked.* methods), they dont behave like they should in optimization mode, but they do in backtesting. Going even further, I can't reproduce the error if bot will not update properties that are shared between threads. Is there a way to fix the thread pool size for one optimization run? It would help me in my debugging.

Regards,

Wojtek

bury1992
25 May 2020, 20:11

RE:

PanagiotisCharalampous said:

Hi elpmie,

No there is no fix for this issue yet.

Best Regards,

Panagiotis

Hi,

Is there something new about the fix? Because it seems like my bot returns different values each time I run the backtesting, even though I've fixed everything i could (dataset, spread, time).

Best regards,

Wojtek