Archived issue #0027666
Wrong min distance result
Description
BRepExtrema_DistShapeShape computes non-zero distance on the two attached shapes. However, there is an intersection. For example BOP common gives non-empty result.
Steps to reproduce
restore solids138.brep s1
restore solids147.brep s2
dist s1 s2
# this results in: distance : 3.1251829616557059
# to check that result is non empty:
# bop s1 s2
# bcommon r
# nbshapes r
restore solids147.brep s2
dist s1 s2
# this results in: distance : 3.1251829616557059
# to check that result is non empty:
# bop s1 s2
# bcommon r
# nbshapes r
Public activity
3 archived notes
Participants are labeled by their role within this record.
The command 'dist' call the method BRepExtrema_Poly::Distance, but not BRepExtrema_DistShapeShape.
The correct command is 'distmini', and it gives zero distance:
The correct command is 'distmini', and it gives zero distance:
Draw[3]> distmini d s1 s2 "distmini" command returns: d_val d Output is complete. Draw[4]> dval d_val 0
Thanks a lot. You're right, I've confused by difference with these two commands.
In fact, distmini command gives wrong result in OCCT 6.9.1, while it is OK in OCCT 7.0. So, we can consider that the problem was fixed in OCCT 7.0.
In fact, distmini command gives wrong result in OCCT 6.9.1, while it is OK in OCCT 7.0. So, we can consider that the problem was fixed in OCCT 7.0.
Dear Commenter 1, please close this issue.