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 96
    • Issues 96
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 99
    • Merge requests 99
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & 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-repositories
  • dumuxdumux
  • Issues
  • #566
Closed
Open
Created Aug 28, 2018 by Timo Koch@timokOwner

MPNC "MaterialLaw API" creates unnecessary dependencies

The concept used by the "TwoPAdapter" seems to be something that belongs in the volume variables only. Currently the spatial params need to know about the fluid system. However that knowledge is available in the volume variables and computing pressure as the MPNC API seems to do is also the task of the volume variables.

Can we move the code somehow to the volume variables and design the interface in a way that knowledge of the fluid system and fluid state is not needed in the spatial params?

Edited Aug 29, 2018 by Timo Koch
Assignee
Assign to
Time tracking