| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] |
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0029858 | Community | [OCCT] OCCT:Modeling Data | public | 2018-06-11 16:41 | 2018-06-13 16:03 |
|
| Reporter | martinsiggel | |
| Assigned To | msv | |
| Priority | normal | Severity | major | |
| Status | new | Resolution | open | |
| Platform | | OS | | OS Version | |
| Product Version | [OCCT] 7.2.0 | |
| Target Version | [OCCT] 7.4.0* | Fixed in Version | | |
|
| Summary | 0029858: Regression in GeomAPI_ExtremaCurveCurve |
| Description | Commit http://git.dev.opencascade.org/gitweb/?p=occt.git;a=commit;h=246c7a7554dd24047ada720fbfce42e9c10b4657 [^] introduced a regression, computing the wrong intersection / extrema results.
The regression either computes the wrong result or the wrong number of extremas.
|
| Steps To Reproduce | I have attached 4 examples, that all fail to compute the correct results. Until this commit, all four cases did work correctly.
Example 1: Does not find the correct extremum / intersection.
Example 2: Wrong results on both curves
Example 3: Wrong intersection result
Example 4: Wrong number of intersections (should be at begin AND end of the curve!) |
| Tags | No tags attached. |
|
| Test case number | |
|
| Attached Files |  geomapi_extremacurvecurve_regression.tar.gz (17,545 bytes) 2018-06-11 16:41 |
|
Relationships 
Relationships 