- May 10, 2018
-
-
Dennis Gläser authored
-
Dennis Gläser authored
-
Dennis Gläser authored
Some of the interfaces were designed such that they are in agreement with the porous medium flow framework where we make them work for both cell-centered as well as the box scheme. In the geomechanics framework we now make use of the fact that cell-centered schemes are not considered and use more FEM-like interfaces for the parameters required for stress evaluations. This might enable us to rename/redefine these interfaces to work with both FEM as well as Box. However, if cell-centered schemes for geomechanics are to be implemented one day, the whole structure would have to be overthought.
-
Dennis Gläser authored
-
Dennis Gläser authored
-
- May 09, 2018
-
-
Martin Schneider authored
[newton] Add report function for statitics output See merge request !975
-
Martin Schneider authored
-
Dennis Gläser authored
Cleanup/indentations See merge request !977
-
Dennis Gläser authored
-
Dennis Gläser authored
-
Dennis Gläser authored
-
Dennis Gläser authored
-
Dennis Gläser authored
-
Dennis Gläser authored
-
Dennis Gläser authored
-
Dennis Gläser authored
Feature/box elastic See merge request !973
-
Dennis Gläser authored
-
Dennis Gläser authored
-
Dennis Gläser authored
This way we can reuse code more easily for geomechanics
-
Dennis Gläser authored
This commit will enable the geomechanics framework to not have to state the number of phases in geomechanical model traits. Also, when velocity output for the geomechanical models is implemented, we will have to distinguish in the vtk output module anyway, as then we would have to call numSolidPhases(). Outsourcing it directly to the velocity output seems like an elegant solution.
-
Dennis Gläser authored
Geomechanical models will not be able to reuse the vtk output module otherwise.
-
- May 08, 2018
-
-
Timo Koch authored
-
Timo Koch authored
-
Timo Koch authored
[solidsystem][spatialparams] Improve interface functions and adapt and clean all spatialparams/problems
-
Timo Koch authored
-
Timo Koch authored
-
[cleanup] use temperatureFluid to make it more obvious which temperature is meant for thermal nonequilibrium
-
-
-
-
-
[references][2pncminbox] update reference solution for saltflushbox after introduction of solidsystem
-
The volumevariables derive now from the energyvolumevariables which set the solid propererties needed for nonisothermal models in the new solidstate Each model now also includes a solidstate (inert or compositional) and each problem a solidsystem. For nonreactive models the default is set to constant component where properties can be specified in the input file. The fluidsystems now do not have solid properties anymore. Each solid component now has all thermal properties which might depend on temperature.
-
The energyvolumevariables are able to deal with thermal nonequilibrium, setting each temperature in the fluidstate or solidstate respectively
-
-
-
-
-