Skip to content

GitLab

  • Menu
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 84
    • Issues 84
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 80
    • Merge requests 80
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • dumux-repositories
  • dumuxdumux
  • Issues
  • #976

Closed
Open
Created Dec 09, 2020 by Timo Koch@timokOwner

Discussion: naming of boundary condition functions / conditions

Problem currently need to implement dirichlet and neumann functions and we have the corresponding boundary conditions dirichlet and neumann. However we use neumann much more general than in there original meaning I believe. For example Robin/Cauchy boundary conditions can be realized in the neumann function.

Essentially neumann corresponds to the integrand of all boundary integrals in the equations. It's always a weakly enforced boundary condition. dirichlet corresponds to setting a fixed value and is strongly or weakly enforced depending on the discretization scheme.

Alternative naming schemes could be

  • boundaryFluxes (for neumann) and BC type flux
  • boundaryValues (for dirichlet) and BC type value/fixed

or only changing neumann

  • boundaryFluxes (for neumann) and BC type flux
  • dirichlet and BC type dirichlet

Other ideas and opinions?

Assignee
Assign to
Time tracking