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 87
    • Merge requests 87
  • 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
  • #801
Closed
Open
Issue created Jan 20, 2020 by Martin Schneider@martinsMaintainer

[Box] variable switch at boundary

It seems that there is a bug in the variable switch for box at the boundary. In the initPriVarSwitch_ method, the states of Dirichlet nodes are corrected. This method is called in newtonBegin, which however is called after the initialization of uLastIter.

Therefore, when calling the newtonUpdate method, the corrected states of uCurrentIter are overwritten.

We could fix this by either calling initPriVarSwitch_ before uLastIter is initialized or by setting this vector after newtonBeginStep. So we could simply change

if (numSteps_ > 0)
    uLastIter = uCurrentIter;

to

if (numSteps_ >= 0)
    uLastIter = uCurrentIter;
Edited Jan 20, 2020 by Martin Schneider
Assignee
Assign to
Time tracking