Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • dumux dumux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 104
    • Issues 104
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 88
    • Merge requests 88
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • dumux-repositoriesdumux-repositories
  • dumuxdumux
  • Issues
  • #1141
Closed
Open
Issue created Apr 17, 2022 by Timo Koch@timokOwner

Repartition interface with PTScotch

The graph partitioning interface added in !3005 (merged) assumes that the initial graph is on rank 0. This is useful to distribute a grid read on rank 0 e.g. with the gmsh reader. However, for dynamic load balancing, we need a repartition interface that works if the graph is distributed. PTScotch provides dgraph (distributed graph) for this purpose. Distributed graphs have a more complex interface but include also the current case where the entire graph is on rank 0 (all other ranks then have 0 graph nodes).

Edited Apr 17, 2022 by Timo Koch
Assignee
Assign to
Time tracking