Using Expertremove() now. Spits out all the results but at least avoids the testerstop endless loop issue.
Changing an double before expertremove and using custom max Ontester to indicate which result ended due to expertremove is helpful. Hope it helps someone else.

You are missing trading opportunities:
- Free trading apps
- Over 8,000 signals for copying
- Economic news for exploring financial markets
Registration
Log in
You agree to website policy and terms of use
If you do not have an account, please register
Hi,
Can anyone give me more information on the Testerstop() function? It does what is says in the documentation and allows successful optimisation results through.
However when I use it during optimisation, it slows down or never stops optimising and printing "genetic pass...tested with error "expert stopped"