Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FiPy cannot partition with Gmsh 4.x #697

Open
1 of 2 tasks
guyer opened this issue Jan 24, 2020 · 0 comments
Open
1 of 2 tasks

FiPy cannot partition with Gmsh 4.x #697

guyer opened this issue Jan 24, 2020 · 0 comments

Comments

@guyer
Copy link
Member

guyer commented Jan 24, 2020

FiPy only understands Gmsh's msh2 format and Gmsh 4.x does not export ghost cells correctly in msh2.

  • This constraint should be documented
  • FiPy should support newer Gmsh formats
guyer added a commit to guyer/fipy that referenced this issue Jan 24, 2020
guyer added a commit to guyer/fipy that referenced this issue Jan 27, 2020
- Limit Gmsh to < 4.0
  Gmsh 4.0 doesn't partition correctly
  Addresses usnistgov#697
- Export ghosts with Gmsh 4.x
  [Ghosts are broken](https://gitlab.onelab.info/gmsh/gmsh/issues/733),
  but export them anyway.
- Change refinement metric
- Limit refinements
  Gmsh refinement seems to stall out
- Don't partition tiny meshes
- Tolerate mangled Gmsh version string

  Assume Gmsh 3.0 if we can't parse the useless nonsense
  that Gmsh stuffs into stderr
- Ensure GmshMesh uses correct communicator

  More than one overlap will "downgrade" to a serial communicator
  because Gmsh doesn't give us more than one layer of ghosts
guyer added a commit to guyer/fipy that referenced this issue Jan 27, 2020
- Limit Gmsh to < 4.0
  Gmsh 4.0 doesn't partition correctly
  Addresses usnistgov#697
- Export ghosts with Gmsh 4.x
  [Ghosts are broken](https://gitlab.onelab.info/gmsh/gmsh/issues/733),
  but export them anyway.
- Change refinement metric
- Limit refinements
  Gmsh refinement seems to stall out
- Don't partition tiny meshes
- Tolerate mangled Gmsh version string

  Assume Gmsh 3.0 if we can't parse the useless nonsense
  that Gmsh stuffs into stderr
- Ensure GmshMesh uses correct communicator

  More than one overlap will "downgrade" to a serial communicator
  because Gmsh doesn't give us more than one layer of ghosts
guyer added a commit that referenced this issue Jan 27, 2020
- Limit Gmsh to < 4.0
  Gmsh 4.0 doesn't partition correctly
  Addresses #697
- Export ghosts with Gmsh 4.x
  [Ghosts are broken](https://gitlab.onelab.info/gmsh/gmsh/issues/733),
  but export them anyway.
- Change refinement metric
- Limit refinements
  Gmsh refinement seems to stall out
- Don't partition tiny meshes
- Tolerate mangled Gmsh version string

  Assume Gmsh 3.0 if we can't parse the useless nonsense
  that Gmsh stuffs into stderr
- Ensure GmshMesh uses correct communicator

  More than one overlap will "downgrade" to a serial communicator
  because Gmsh doesn't give us more than one layer of ghosts
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant