Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 379
    • Issues 379
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 13
    • Merge requests 13
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #1990

Closed
Open
Created Jan 25, 2021 by Eden Furtak-Cole@furtak

Possible bug in snappyHexMesh for large coordinates

Summary

For large coordinates, snappyHexMesh stops refinement after two levels.

Steps to reproduce

snappyHexMesh stops refinement in directions corresponding to large coordinates. This is a problem when working in geographic coordinates. In the attached casefile, will see that refinement is performed in the x and z directions, but stops after two levels in the y direction. I suspect that this is because the y coordinate is on the order of e+6, while the x direction is e+5, and z is close to zero. I don't know if this is a known issue, I have not found any information about it.

Example case

bad_mesh.tar.xz

I attached a very small casefile. Run blockMesh and snappyHexMesh.

What is the current bug behaviour?

No refinement in the y direction after two levels.

What is the expected correct behavior?

Refinement in all directions, regardless of coordinates.

Relevant logs and/or images

image

Environment information

  • OpenFOAM version : 2006
  • Operating system : CentOS 7
  • Hardware info : Dell Precision 3630
  • Compiler : gcc

Possible fixes

If the case is translated to the origin the problem goes away. This makes me think this is a bug, but I can't point to the part of the code that is causing this. snappyHexMesh finishes without errors.

Assignee
Assign to
Time tracking