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 91
    • Merge requests 91
  • 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
  • #782
Closed
Open
Issue created Oct 22, 2019 by Powei Huang@pwhuangDeveloper

The velocity output from the 1p tracer example is halved on the top and bottom boundaries.

Bug report The velocity output from the 1p tracer example is halved on the top and bottom boundaries.

What happened / Problem description: This problem occurred when I ran the tracer problems. They are located in

dumux/examples/1ptracer

dumux/test/porousmediumflow/tracer/1ptracer

The velocity output using the vtk output module will result in a halved velocity on the top and bottom boundaries. The file name is tracer.pvd. This issue can be seen easily when setting a constant permeability throughout the domain.

What you expected to happen: When the problem has top and bottom Dirichlet boundary conditions for pressure and constant permeability, the velocity field should be constant in space.

Assignee
Assign to
Time tracking