Skip to content
GitLab
Projects Groups 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
    • Contributors
    • Graph
    • Compare
  • Issues 327
    • Issues 327
    • 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
  • #2153
Closed
Open
Issue created Oct 19, 2022 by Jonathan Lambrechts@jonathanMaintainer

periodic + mesh.set_order fails on this example

On this geo file 4grains.geo the following python script

gmsh.initialize()
gmsh.open("4grains.geo")
gmsh.model.mesh.generate(3)
gmsh.model.mesh.set_order(2)
gmsh.write("4grains.msh")

fails with the error

Cannot find periodic counterpart of node 33 of surface 50 on surface 54.

But this (from the user point of view, equivalent) script runs without error and produces a 2nd order mesh.

gmsh.initialize()
gmsh.open("4grains.geo")
gmsh.option.set_number("Mesh.ElementOrder", 2)
gmsh.model.mesh.generate(3)
gmsh.write("4grains.msh")
Assignee
Assign to
Time tracking