Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
D
dorie
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 31
    • Issues 31
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • dorie
  • dorie
  • Issues
  • #172

Closed
Open
Opened Dec 17, 2019 by Lukas Riedel@lriedelOwner

CFL condition is based on water flux

The CFL condition currently estimates the maximum time step based on the water flux j_w

Summary

The water flux \mathbf{j}_w = \theta_w \mathbf{v} is not the velocity of the solute. Instead, the water flux has to be divided by the water content to yield the water velocity \mathbf{v} = \mathbf{j}_w / \theta_w .

What is the current bug behaviour?

CFL condition is based on water flux.

What is the expected correct behaviour?

CFL condition is based on convective velocity.

Ideas how to fix this?

Pass the water content grid function to the CFL condition function and divide the local water flux by the local water content to receive the local velocity.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dorie/dorie#172