Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • dumux dumux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 100
    • Issues 100
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 92
    • Merge requests 92
  • 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
  • #996
Closed
Open
Issue created Mar 01, 2021 by Kilian Weishaupt@kweisMaintainer

[pnm] BoundaryFlux class only works for Dirichlet Boundaries

The BoundaryFlux class for evaluating fluxes entering or leaving the network only works if Dirichlet conditions are set on the relevant boundaries.

This is because the class evaluates the local residual at the respective DOFs. For Dirichlet BCs, the value is not zero but equals the boundary flux.

One could maybe check if a Dirichlet BC is set and proceed as before and just evaluate the source term instead otherwise.

Note: source corresponds to a neumann BC at the boundary. The PNM does not support neumann but requires a source instead because there are no boundary scvfs.

Assignee
Assign to
Time tracking