Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • gmsh gmsh
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 304
    • Issues 304
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • 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
  • gmsh
  • gmshgmsh
  • Issues
  • #1468
Closed
Open
Created Jul 12, 2021 by Paul le Roux@pleroux

Issues when incrementally meshing OpenCascade shapes

Hi

We are trying to mesh a complicated structure incrementally. It is not feasible for us to mesh everything at once since we use the intermediate mesh results to calculate a new mesh size field for the next part. I've constructed a simplified example that showcases our problem.

The code is included in the attached cpp file, GmshBug001.cpp. The console output is included in the attached log file, GmshBug001.log.

The wireframe for the geometry is shown in the following image.

image

The center cube is not part of the computational domain. Only the left cube, right cube and the surrounding volume inside the bounding box. Generated by the program is the brep file, which I've also attached for convenience, gmsh_bug_001.brep.

There are two issues in this example.

  1. The already meshed surfaces (1, 2, 3, 4) are re-meshed even though their geometry hasn't changed. The curves do not seem to have this issue and are correctly skipped when meshing subsequent parts.

  2. The crash when trying to mesh the right cube. If the mesh is generated all at once, then no crash occurs.

Any guidance and/or assistance will be greatly appreciated.

Assignee
Assign to
Time tracking