View Issue Details

IDProjectCategoryView StatusLast Update
0027798CommunityOCCT:Meshpublic2019-02-11 10:37
ReporterVico Liang Assigned Tobugmaster  
Status closedResolutionno change required 
PlatformWindowsOSVC++ 2013 
Target Version7.4.0 
Summary0027798: Bad or degenerated triangles should be avoided (e.g for Cone meshing)
DescriptionOCCT 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.
TagsNo tags attached.
Test case number


duplicate of 0025042 closedbugmaster Community Cone Meshing: Missing two connecting edges. 



2018-11-07 17:00

developer   ~0080853

Implemented in context of #28379.

Test case not needed.


2018-11-07 17:18

developer   ~0080859

The fix for #28379 splits the seam edge of the conical face. It does not deel with degenerated triangles.


2018-11-07 17:19

developer   ~0080863

Dear Vico, please check the new behavior and tell if it is OK for you now.


2018-12-24 11:20

developer   ~0081603

Last edited: 2018-12-24 11:21

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.

Vico Liang

2018-12-24 12:24

developer   ~0081604

sorry that I don't get time to check this. please go ahead to close this issue.


2018-12-25 12:25

developer   ~0081617

Dear bugmaster,

please manage the issue.

Issue History

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 abv 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 abv 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 msv Note Added: 0080859
2018-11-07 17:19 msv Note Added: 0080863
2018-11-07 17:19 msv 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