Correct handling of reassigned surfaces and lines after fuse operation
Hi,
I have an aircraft defined in several parts (fuselage, wing1, wing2, etc...)
I have difficulties finding a robust way to find, after the fuse operation, which surfaces and lines belonged to which part of the plane. It is even more difficult to identify the new surfaces and lines created between two parts when they are fused. For now, before the merge operation, I store the bounding box of each entity, and after the merge, I tried to reassign the entities with getEntitiesInBoundingBox(). I am kind of looking for the entities since they should stay in the same place after the fuse operation.
The problem is that this method is not robust, sometimes the bounding box technic fails to find some entities (I suspect some kind of truncation errors). I tried to extend the bounding boxes, but then I find unwanted entities from other parts.
I already saw some issues (#1786,#946 (closed),#592) and it seems hard to handle this loss of information induced by some boolean operations,
-
Is there any smart way to handle this knowing that before the fuse operation, I have all the information on each surface's original part?
-
How is it possible with gmsh to automatically assign the surfaces label in the part.step file with the dimTags returned by the importShapes() method in order to form a physical group with the name of the label:
Info : - Label 'Shapes/wing1' (2D)