I think that according to the interval it makes a division and par on an unrounded step. And stops with a result that is as close as possible but not fair.
EDIT: the 1st calculation is exercised like this, it takes half between the min and max interval, hence the answer 10 for a min of 5mm with a max of 15mm.
So for min 5mm and max 12mm he takes half and looks at the value (here 8.5mm) then redoes a calculation with a ^not calculated I don't know how and comes up with a value close to 9.8125mm.
It smells like a dichotomy that is not really optimized or that doesn't go far enough. I just did a test, that's 5 "scenarios" (which I'll call iterations). I didn't see a difference between "fast results" and "high quality" (same result). I tried to increase the interval (8-25), I have the same result, with 1-25, the value found is 11!
If you have access to support, I'll be curious to have their answer.
Yes, I think like you @sbadenis, we have something close in terms of the way we calculate. So the choice of intervals directly influences the accuracy of the results.
It's strange I just did a test on SLD 2015 Sp5 and it works well, in fact, my interval corresponds to a number of scenarios with one step, it calculates all the widths between 5 and 120 mm long in steps of 5 in order to always have a volume of 1000mm3. On the other hand I don't have the "iteration" boxes
Cdt
edit: As for me, I have the same problem, at the beginning I had put interval with step, but when switching to interval, well I have the same problem.
By moving the cursor, we can see how much the iteration is done; In the example below, it's 0.12 so I can't get the exact value according to the minimum and the maximum chosen
The optimum is not 100% guaranteed, and I don't see how to reduce the iteration to refine the calculation.
Indeed, the optimization option has never really convinced me. The notion of steps should not exist since SW is expected to find the solution!! SW should determine on its own by convergence with an increasingly tight interval by minimizing the gap between the result and the target. When I was at school, I made a lot of algorithms for that.
I have turned your example in all directions and have found no better results than you.
Personally I use the "imposed limits" with the "is between between" option, and I refine the step manually. In the cases I have had to deal with so far, it was enough. I recently modeled a cup and I needed to know the level for a capacity of 250 ml at 1%. I did the iterations by hand by tightening the pace, it took me 5 minutes.
Finds the optimal solution from a large number of iterations ( Box-Behnken design) and displays the initial scenario, the optimal scenario, and all iterations.