Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • gmsh gmsh
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 340
    • Issues 340
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gmshgmsh
  • gmshgmsh
  • Issues
  • #1315
Closed
Open
Issue created Apr 14, 2021 by Maxence Reberol@mxncrMaintainer

Duplicates in BRep connectivity with cad + msh4 import

There are duplicates in the Gmsh Brep internal connectivity storage when loading a CAD model and a mesh separately, with the msh4 format. For example:

gmsh model.step -o model.msh
gmsh model.step model.msh

The sub-entities are duplicated (e.g. same face multiple times in gr->faces()). But there is no issue when using "-format msh2" in the first mesh export (because BRep not stored in the mesh file I guess?).

To reproduce, there is a simple example attached (square.geo + test.py).

./gmsh square.geo -2 -o square.msh -format msh4

python test.py square.geo
> faces: [(2, 1)]
> (2, 1) - bdr: [(1, 1), (1, 2), (1, 3), (1, 4)]
(normal)

python test.py square.msh
> faces: [(2, 1)]
> (2, 1) - bdr: [(1, 1), (1, 2), (1, 3), (1, 4)]
(normal)

python test.py square.geo square.msh
> faces: [(2, 1)]
> (2, 1) - bdr: [(1, 1), (1, 2), (1, 3), (1, 4), (1, 1), (1, 2), (1, 3), (1, 4)]
(not normal, but result ok when using -format msh2)

square.geo test.py

Assignee
Assign to
Time tracking