Skip to content
GitLab
Projects Groups Topics 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
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 100
    • Issues 100
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 92
    • Merge requests 92
  • 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
  • #453
Closed
Open
Issue created Feb 28, 2018 by Kilian Weishaupt@kweisMaintainer

Introduce SolidSystem and SolidComponents

The SolidSystem calculates quantities like solidHeatCapacity, solidDensity and solidHeatConductivity based on the compositions of individual solid components such as Granite or Sand.

The concept uses the components' volume fractions which are either solution dependent or fixed via the spatialParameters.

For simple cases, where there is only one non-reactive solid component, the base spatialParams implement a volumeFractions() method that calls the spatialParams implementation's porosity() method and returns 1-porosity.

For other cases, this method throws an error and therefore forces the user to implement an own volumeFaction() in the spatialParams.

The solidSystem has an interface function porosity() depending on the solid composition, i.e. a SolidState.

This may be realized using some template meta programing magic.

Related to #452 (closed) #433 (closed) #450 (closed), fixes #409 (closed).

Edited Mar 03, 2018 by Timo Koch
Assignee
Assign to
Time tracking