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 100
    • Issues 100
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 89
    • Merge requests 89
  • 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
  • Merge requests
  • !3190

[fix] Staggered velocity output

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Martin Schneider requested to merge fix/staggered-velocity-output into master Jul 11, 2022
  • Overview 2
  • Commits 1
  • Pipelines 4
  • Changes 1

It seems that in the lambda function the wrong fvGeometry has been used. It seems that this actually doesn't make any difference in the solution because the lambda is always called with the fvGeometry passed to the calculateVelocityForStaggeredGrid_.

Maybe we could also think about deleting the fvGeometry argument when calling getFaceVelocity. I current don't really see why one would need a different fvGeometry.

Edited Jul 11, 2022 by Martin Schneider
Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: fix/staggered-velocity-output