Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • dumux dumux
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 91
    • Issues 91
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 80
    • Merge requests 80
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • dumux-repositories
  • dumuxdumux
  • Issues
  • #261
Closed
Open
Created Apr 15, 2015 by Bernd Flemisch@berndOwner

FS#261 Misnomer evalPhaseStorage in couplinglocalresiduals

Metadata

Property Value
Project dumux
Category General
Reported by Bernd Flemisch (bernd@iws.uni-stuttgart.de)
Reported at Apr 15, 2015 08:54
Type Bug Report
Version Git
Last edited by Bernd Flemisch (bernd@iws.uni-stuttgart.de)
Last edited at May 28, 2015 10:41
Closed by Bernd Flemisch (bernd@iws.uni-stuttgart.de)
Closed at May 28, 2015 10:41
Closed in version 2.8
Resolution Implemented

Description

The 2p2c(ni) couplinglocalresiduals have a member function named "evalPhaseStorage". However, not the storage "S" is calculated there, but its time derivative "(S_new - S_old) / dt". This is not only a misnomer, but also inconsistent with the uncoupled 2p2c localresidual that offers a function with the same name that really calculates "S".

I would propose to rename the function to "evalPhaseStorageDerivative".

Assignee
Assign to
Time tracking