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
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • dorie
  • dorie
  • Issues
  • #151

Closed
Open
Opened Apr 30, 2019 by Lukas Riedel@lriedelOwner

"dirichletMode" parameter is never evaluated

dirichletMode is a new parameter in [solute.boundary], but it's never evaluated.

Summary

dirichletMode is supposed as a switch to determine if the Dirichlet parameter means the solute concentration in the total volue (totalConcentration) c_t or the concentration in the water phase (soluteConcentration) c_w (in which the solution is actually evaluated. This key is never read from the parameter file. By default, the local operator sets the mode to DirichletMode::SoluteConcentration, see local_operator_FV.hh#L122.

I also have to say that I am a bit confused about the code where this mode is queried inside the operator, see local_operator_FV.hh#L377. Why would the water content at any time be lower than zero, and why does the boundary condition then become zero?

Steps to reproduce

Set dirichletMode to totalSolute. Nothing happens.

What is the current bug behaviour?

dirichletMode is not evaluated.

What is the expected correct behaviour?

dirichletMode adjusts the Dirichlet boundary condition as specified.

Relevant logs, screenshots, files...?

Screen_Shot_2019-04-30_at_16.11.32

Ideas how to fix this?

I discovered this when merging master into !121 (merged). I guess I can resolve this in there, as it rebuilds the way boundary conditions are stored and queried. I think it would be useful if one could declare this setting in the BC file, and for every Dirichlet BC separately. This should be possible with the new setup.

Edited Apr 30, 2019 by Lukas Riedel
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#151