MantisBT
Mantis Bug Tracker Workflow

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0031641Community[OCCT] OCCT:Modeling Algorithmspublic2020-06-29 11:222020-09-15 09:56
Reportermat127 
Assigned Toakulagin 
PrioritynormalSeveritymajor 
StatusnewResolutionopen 
PlatformLinux 64bitOSFedora CoreOS Version31
Product Version[OCCT] 7.3.0 
Target VersionFixed in Version 
Summary0031641: IntCurvesFace_ShapeIntersector incorrect result
DescriptionThere is a shape stored in the attached shape.brep file. IntCurvesFace_ShapeIntersector gives an icorrect results for checking intersections of this shape with lines parallel to the Z axis at particular (x,y) directions.

The application oputput is:

[(0.839, -4.675, -1.555), (0, 0, 1)]
  (0.839, -4.675, 0): out
  (0.839, -4.675, 0): in
  (0.839, -4.675, 1.5): out
[(2.304, -3.40779, -1.555), (0, 0, 1)]
  (2.304, -3.40779, 0): out

Line definition [(location),(direction)] is followed by an intended list of intersection points and their transitions in the form (intersection location): transition.

In both cases the first intersection point having the transition 'out' is errorneous. It means that the line for z < 0 is inside the shape which is not true.
Steps To ReproduceCompile and run the attached .cxx file and check the output according to the description. Note that the application needs the provided shape.brep file being placed in the same directory as the application binary.
TagsNo tags attached.
Test case number
Attached Filescxx file icon intersector.cxx (2,622 bytes) 2020-06-29 11:22
? file icon shape.brep (590,377 bytes) 2020-06-29 11:23
cxx file icon intersector2.cxx (2,389 bytes) 2020-09-10 16:55
? file icon shape2.brep (1,819,036 bytes) 2020-09-10 16:55
cxx file icon intersector3.cxx (2,402 bytes) 2020-09-10 17:01

- Relationships

-  Notes
(0094389)
mat127 (reporter)
2020-09-10 17:05

Similar issue observed for the shape2.brep shape. Compile and run the intersector3.cxx (please ignore intersector2.cxx) and check the output:

[(0.801494, -3.855, 1.88088), (0, 1, 0)]
  (0.801494, -3.855, 1.88088): in
  (0.801494, 3.855, 1.88088): out

This looks like a valid output signaling that the line is inside the shape for -3.855 < y < 3.855. But it is not true. The line just touches the shape at both intersection points.

- Issue History
Date Modified Username Field Change
2020-06-29 11:22 mat127 New Issue
2020-06-29 11:22 mat127 Assigned To => msv
2020-06-29 11:22 mat127 File Added: intersector.cxx
2020-06-29 11:23 mat127 File Added: shape.brep
2020-09-10 16:55 mat127 File Added: intersector2.cxx
2020-09-10 16:55 mat127 File Added: shape2.brep
2020-09-10 17:01 mat127 File Added: intersector3.cxx
2020-09-10 17:05 mat127 Note Added: 0094389
2020-09-14 09:52 msv Assigned To msv => ifv
2020-09-15 09:56 ifv Assigned To ifv => akulagin


Copyright © 2000 - 2020 MantisBT Team
Powered by Mantis Bugtracker