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
  • #301
Closed
Open
Created Oct 21, 2015 by Alexander Kissinger@kissingerDeveloper

FS#301 Solution dependent spatial parameters

Metadata

Property Value
Project dumux
Category General
Reported by Alexander Kissinger (alexander.kissinger@iws.uni-stuttgart.de)
Reported at Oct 21, 2015 15:12
Type Feature Request
Version Git
Last edited by Kilian Weishaupt (kilian.weishaupt@iws.uni-stuttgart.de)
Last edited at Jan 22, 2016 09:25

Description

In many applications there is a need to make parameters like porosity, permeability etc. dependent on the solution, e.g. porosity or permeability depending on pressure or chemical species or whatever.

It would be very convenient for these cases to have a function call from the volume variables that passes the current volume variables along as an argument.

This would greatly increase the flexibility for users who would not have to change anything on the model level if they want solution dependent spatial params but could implement all their changes on the application level.

The function calls could be implemented on the common and model level in such a way that the function calls as they are now would still be valid, i.e. no changes needed in existing spatial params on the application level.

I already implemented something like this for the dfm models in dumux-devel.

Assignee
Assign to
Time tracking