DiscussionsIssue archiveModeling Data and Algorithms

Archived discussion

Defeaturing class question

Modeling Data and AlgorithmsSat, 04/13/2024 - 20:494 replies

Browse this forum
QuestionAuthor

I've got a pump model (zipped step model attached) that has numerous chamfers and have been using the BRepAlgoAPI_Defeaturing class in an attempt to remove some of these. I am able to successfully remove the chamfer highlighted in blue on the upper side of the top mating surface (topChamfer.png) but have been unsuccessful in removing the chamfer on the lower side (bottomChamfer.png). This selection seems to be ultimately ignored by the algorithm. Does the more complicated topology adjacent to the bottom chamfer render it beyond the scope of the algorithm?

Discussion

4 archived replies

Posts are displayed in their archived order.

01Commenter-1

Hello, yes. You bottom cases has intersection with another edge that leads to some problems. It is difficult to recovery 2 not related edges on the same time. Especially if some edges was splitted. In that case needs to call extension of edges, but that is not a part of current implementation, as I know.

Best regards, Commenter-1.

02Author

Thank you for your response Dmitrii. A follow-on question if you would indulge me.
If I select only the chamfer surfaces near the bolt holes on the bottom plate, the resulting topology on the bottom plate is exactly as expected - an excellent result. However, I see that the topology for two of the bolt holes on the upper plate has also been modified for no apparent reason though it is still valid. Can this be explained? The image 'defeatureTopology1.png' identifies the before and after model edges.

03Commenter-1

The current bug is a result of complex chamfers. Please create a ticket in our bugtracker.

Best regards, Commenter-1.

04Author

Done. Issue 33693.