Trouble changing a circle radius precisely
-
Well, I wasn't able to edit the existing hole to .035", but I was able to create a new hole with that dimensions, so problem solved, even if it's more hassle than it should be. Thanks for trying to help, though.
-
Yeah, but... Was the hole defective or past its sell-by date? That's a weird thing.
-
@dave r said:
That's a weird thing.
I agree. The hole went through a .25" piece of material, so I sealed up the "tunnel" so there was a just a hole in one surface, and it still wouldn't let me change it to .035. Didn't matter whether there was an even or odd number of sides, or if the precision was increased to 0.0000". Go figure.
-
Is it possible it wasn't a circle anymore?
-
I don't see how it could have changed, but, even if it had, would SU allow me to edit its radius if SU didn't recognize it as a circle?
-
Su 8 runs as 32 bit & does not make any difference what version of windows you use. Think su change to 64 bits at 2014. My 2015 with 64 bits reports as expected. The precision you are changing only effects display precision not any thing to do with internal calculation.
There are on line IEE floating point conversion programs you can run . Float cannot convert all the real numbers exactly so guess is you are seeing a rounding error, that is pain you pay for dynamic range vs accuracy.
BTW the task manager will report what processes are running 32 bits. -
If SU couldn't handle the precision, why would it let me create a .035" diameter hole but not let me change the diameter of an existing hole to that value?
-
why ask me when you can go to net do serach on 32 float, look at converter and see what it tells you. The actual precision of 32 bit float is equivalent to about 24 bit when you consider 1 bit sign , 7 bits mantissa. Depending on the mother board you have the actual bus may operate at more than 24 bits and conversion actually happens when the data is stored in memory.
-
@mac1 said:
why ask me when you can go to net do serach on 32 float, look at converter and see what it tells you. The actual precision of 32 bit float is equivalent to about 24 bit when you consider 1 bit sign , 7 bits mantissa. Depending on the mother board you have the actual bus may operate at more than 24 bits and conversion actually happens when the data is stored in memory.
I was sort of following this until now
-
You are correct, terrible job on my part trying to explain;
For 32 float, you have 1 sign bit, 8 mantissa bits and 23 significant bits but because way the sign used significant bits is 24. The decimal equivalent digits for 24 bits is 7.2+ digits. Thus you see the basis of the display I was discussing earlier. Using an online converter 0.35 converts to .3499999994039..... and 0.4 to .40000000596046.... and rounding is done for those to read .35...... and .40......... and has nothing to change the precision use internal to the machine. Why the OP machine changes .35 to .40 I can only guess, but if a generic SU issue that would have many more folks flagging the problem so => probably issue with his machine or its operating system. There is zero info provided for it so no further action can be done except by the op.
Advertisement