Skip to content
GitLab
Projects Groups 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
    • Contributors
    • Graph
    • Compare
  • Issues 102
    • Issues 102
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 90
    • Merge requests 90
  • 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
  • #487
Closed
Open
Issue created Apr 30, 2018 by Kilian Weishaupt@kweisMaintainer

Boundary conditions for FreeFlow

We should rethink the way boundary conditions for the Navier-Stokes models are handled.

Versteeg and Malalasekera suggest the following boundary conditions:

  • inlet
  • outlet
  • wall
  • prescribed pressure
  • symmetry
  • periodicity (or cyclic boundary condition)

Until now, "outlet" and "prescribed pressure" are somehow combined into the "outflow" BC, which does not always make sense.

Should we adapt to these kind of fixed conditions or provide at least some convenience methods?

What do we need to consider for coupling to other domains?

Assignee
Assign to
Time tracking