View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0027798 | Community | OCCT:Mesh | public | 2016-08-22 07:32 | 2019-02-11 10:37 |
Reporter | Vico Liang | Assigned To | bugmaster | ||
Priority | normal | Severity | minor | ||
Status | closed | Resolution | no change required | ||
Platform | Windows | OS | VC++ 2013 | ||
Target Version | 7.4.0 | ||||
Summary | 0027798: Bad or degenerated triangles should be avoided (e.g for Cone meshing) | ||||
Description | OCCT meshing algorithm generates good mesh for most cases. But there are some speical cases which will generate bad triangle with angle near 180 degree or degenerated triangle with two coincident nodes. It can be reproduced with Cone Shape. It will be a big issue if these bad or degenerated triangles serve as input of remesher algorithm or simulation solver. The root cause might be about edge meshing of cone generatrix. The straight edge of cone generatrix will never be divided whatever how long it is. If the straight long edge can be divided as necessary, the bad triange might be avoided. | ||||
Tags | No tags attached. | ||||
Test case number | |||||
|
Implemented in context of #28379. Test case not needed. |
|
The fix for #28379 splits the seam edge of the conical face. It does not deel with degenerated triangles. |
|
Dear Vico, please check the new behavior and tell if it is OK for you now. |
|
Please note that BRepMesh algorithm is not supposed for use in solvers, but only for visualization needs. Another point is that, it will always provide at least one degenerative triangle near the apex of the cone and e.g. pole of the sphere as far as it tries to produce connected mesh in 3d/2d space and without such triangles mesh will contain a hole. In case of necessity to avoid degenerative triangles, please skip them manually before feeding triangulation to any solver. As for general issue, division of seam edge has already been implemented in context of #28379 and integrated to master branch. I propose to close this issue. |
|
sorry that I don't get time to check this. please go ahead to close this issue. |
|
Dear bugmaster, please manage the issue. |
Date Modified | Username | Field | Change |
---|---|---|---|
2016-08-22 07:32 | Vico Liang | New Issue | |
2016-08-22 07:32 | Vico Liang | Assigned To | => oan |
2016-08-22 07:34 | Vico Liang | Description Updated | |
2016-08-22 11:07 | oan | Relationship added | duplicate of 0025042 |
2016-11-03 17:38 |
|
Target Version | 7.1.0 => 7.2.0 |
2017-07-20 12:43 | oan | Target Version | 7.2.0 => 7.3.0 |
2018-02-25 21:09 |
|
Target Version | 7.3.0 => 7.4.0 |
2018-11-07 17:00 | oan | Note Added: 0080853 | |
2018-11-07 17:00 | oan | Assigned To | oan => msv |
2018-11-07 17:00 | oan | Status | new => feedback |
2018-11-07 17:18 |
|
Note Added: 0080859 | |
2018-11-07 17:19 |
|
Note Added: 0080863 | |
2018-11-07 17:19 |
|
Assigned To | msv => Vico Liang |
2018-12-24 11:20 | oan | Note Added: 0081603 | |
2018-12-24 11:21 | oan | Note Edited: 0081603 | |
2018-12-24 12:24 | Vico Liang | Note Added: 0081604 | |
2018-12-24 12:26 | Vico Liang | Assigned To | Vico Liang => oan |
2018-12-24 12:26 | Vico Liang | Status | feedback => assigned |
2018-12-25 12:25 | oan | Note Added: 0081617 | |
2018-12-25 12:25 | oan | Assigned To | oan => bugmaster |
2018-12-25 12:25 | oan | Status | assigned => feedback |
2018-12-28 14:10 | oan | Status | feedback => assigned |
2019-02-11 10:37 | bugmaster | Status | assigned => closed |
2019-02-11 10:37 | bugmaster | Resolution | open => no change required |