I talked about it in another thread, and I just made some tests.
I believe that this bug had been fixed long time ago, I can't remember which version it was...
When you construct a max_inscribed or a min circunscribed cylinder from a LS one, there's no reason that they have the same vector.
If you look at the form (dimension, not the circularity), you can see that only 2 (or 3, it depends) values are zero. There should have a mini of 5 (I think).
This seems to be an important problem if you use a cylinder as a primary datum, because the vector is wrong.
For a secondary, it's less important because you can project the hits on the primary, then construct a max inscr / min circ circle which correspond exactly to the definition of the datum.
I think it's also a problem for "envelop" requirement, because the diameter could be wrong (if the form is wrong, how the diameter can be right ?)
I tested this with 2018R2 SP3 and 2014 release.
Rob Jensen , Don Ruggieri : something to do ?
I believe that this bug had been fixed long time ago, I can't remember which version it was...
When you construct a max_inscribed or a min circunscribed cylinder from a LS one, there's no reason that they have the same vector.
If you look at the form (dimension, not the circularity), you can see that only 2 (or 3, it depends) values are zero. There should have a mini of 5 (I think).
This seems to be an important problem if you use a cylinder as a primary datum, because the vector is wrong.
For a secondary, it's less important because you can project the hits on the primary, then construct a max inscr / min circ circle which correspond exactly to the definition of the datum.
I think it's also a problem for "envelop" requirement, because the diameter could be wrong (if the form is wrong, how the diameter can be right ?)
I tested this with 2018R2 SP3 and 2014 release.
Rob Jensen , Don Ruggieri : something to do ?
Comment