Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • openfoam openfoam
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 426
    • Issues 426
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 8
    • Merge requests 8
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #348
Closed
Open
Issue created Dec 15, 2016 by Mark OLESEN@markMaintainer

Odd logic for treatment of blockMesh zones to sets

In the blockMesh application (around line 360 or so), the cell zones are written as sets (for ease of processing). Immediately after this, a mesh.removeFiles() is invoked prior to writing the mesh. Since the polyMesh::removeFiles also removes the sets sub-directory, it doesn't look like the sets will survive very long.

Tagged in @Mattijs since he might have an idea.

Assignee
Assign to
Time tracking