Optimization oddities with uneven numbers
- This topic has 5 replies, 4 voices, and was last updated 2 years ago by .
Viewing 6 posts - 1 through 6 (of 6 total)
Viewing 6 posts - 1 through 6 (of 6 total)
Forums › ProRealTime English forum › ProOrder support › Optimization oddities with uneven numbers
I have noticed it for a while, but never got around to figuring out why or when it happens. Now I finally have.
When you run an optimization let’s say between 1 and 1.2, the values it will use will be 1.0, 1.1 and finally 1.2.
When you run an optimization between 1 and 1.3, the values it will use will be 1.0, 1.1, 1.2, 1.3 and then finally 1.4.
So, it’s when the end value is an uneven decimal. Anyone else with this problem and why does it happen?
Good spot, I can replicate and I don’t think that’s intentional 🙂 I’m reporting it, thanks a lot for your post.
Much appreciated. Thank you.
A followup.
It doesn’t seem to be only uneven numbers, it’s something else.
Just did 0.2 – 0.8 with steps of 0.2. It finished at 1.0.
Too make it more odd. If you do 0.2 – 0.6, it finishes at 0.6.