View Issue Details

IDProjectCategoryView StatusLast Update
0027666Open CASCADEOCCT:Modeling Algorithmspublic2016-12-09 16:41
ReportervsrAssigned Tobugmaster  
PrioritynormalSeverityminor 
Status closedResolutionno change required 
Product Version6.9.1 
Target Version7.1.0Fixed in Version7.1.0 
Summary0027666: Wrong min distance result
DescriptionBRepExtrema_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 Reproducerestore 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
TagsNo tags attached.
Test case number

Attached Files

Activities

vsr

2016-07-07 16:58

developer  

files.tgz (302,390 bytes)

msv

2016-07-11 10:55

developer   ~0055791

The command 'dist' call the method BRepExtrema_Poly::Distance, but not BRepExtrema_DistShapeShape.
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

vsr

2016-07-11 12:38

developer   ~0055808

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.

vsr

2016-07-11 12:39

developer   ~0055809

Dear bugmaster, please close this issue.

Issue History

Date Modified Username Field Change
2016-07-07 16:58 vsr New Issue
2016-07-07 16:58 vsr Assigned To => msv
2016-07-07 16:58 vsr File Added: files.tgz
2016-07-11 10:55 msv Note Added: 0055791
2016-07-11 10:55 msv Assigned To msv => vsr
2016-07-11 10:55 msv Status new => feedback
2016-07-11 12:38 vsr Note Added: 0055808
2016-07-11 12:38 vsr Product Version 7.0.0 => 6.9.1
2016-07-11 12:38 vsr Fixed in Version => 7.0.0
2016-07-11 12:39 vsr Note Added: 0055809
2016-07-11 12:39 vsr Assigned To vsr => bugmaster
2016-07-11 12:39 vsr Status feedback => resolved
2016-07-11 12:39 vsr Resolution open => no change required
2016-07-12 09:43 bugmaster Status resolved => closed
2016-12-09 16:41 aiv Fixed in Version 7.0.0 => 7.1.0