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
  • #1796
Closed
Open
Issue created Aug 03, 2020 by Mattijs Janssens@MattijsMaintainer

support for only single patch between processors (e.g. ProcessorTopology::procPatchMap())

Functionality to add/problem to solve

Some functionality only supports a single processor patch. Sometimes there can be more than one patch between processors. E.g. processorCyclic (processor patch with cyclic transformations), overset (introduces additional lduInterfaces to handle the interpolation)

See e.g.

ProcessorTopology::procPatchMap()

which is used to lookup a patch given a remote processor (used in snappyHexMesh/extrudeMesh)

Assignee
Assign to
Time tracking