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 9
    • Merge requests 9
  • Deployments
    • Deployments
    • Releases
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Development
  • openfoamopenfoam
  • Issues
  • #874
Closed
Open
Issue created Jun 14, 2018 by Mattijs Janssens@MattijsMaintainer

isoSurface on processor case (so not parallel) crashes since asks for patchNeighbourField

If not running parallel should just use patchInternalField? Problem is that it also uses this routine to generate coordinates which then would be on top of each other.

See isoSurface::adaptPatchFields in sampling/surface/isoSurface/isoSurfaceTemplates.C

Edited Jul 06, 2021 by Kutalmış Berçin
Assignee
Assign to
Time tracking