pietertal wrote:

The workaround I use now is to use whole numbers in the parameter setting and then divide the whole numbers in the code to get the decimal places I need.

Haha, yes, I saw you doing that. This is why/how I came to the question.
But no, I don’t recognize that and using decimals via the normal Optimization Parameters I am doing all the time (and they work out).
I also recognise the /10000 which I use myself regularly, but this is because the numbers in the Optimization Parameters can’t get small enough. From the top of my head : 4 is the maximum while more normal would be 5 (which is the max for Rounding) and beyond of course. What I mean with this is :

When you iterate from 0.00001 to 0.00010, this all shows the same in the Result List. Still internally it *will* use that 5th decimal but as you can’t see it, it is useless.
Can’t this be your problem ?
It is even hard to recognise for me because when such a thing happens, I start to obtain the iteration as 1-10 and divide by 10000 … I do this regardless. And with Forex this is a nobrainer. In the 1st attachment you can see that the decimals are used all over the place, but these are the Optimization Parameters only (I don’t use CALLable Signals). In the 2nd attachment you see how I wouldn’t run into the problem because of the standard approach for Fx (vs not-Fx).

If you think it is worth the trouble, you could make a Technical Report of it (goes via the Help menu).
And redundancy is never a good thing.

image_2023-06-13_042125299.png image_2023-06-13_042745044.png

pietertal wrote:

there cannot be more than 3 zero’s after the decimal point.

I agree as I’ve had the same experience with < 0.0001