FS#200 Decouple Newton method / controller from problems / models
Metadata
Property | Value |
---|---|
Project | dumux |
Category | Discussion |
Reported by | Martin Schneider (martin.schneider@iws.uni-stuttgart.de) |
Reported at | Jul 19, 2013 09:17 |
Type | Feature Request |
Version | Git |
Last edited by | Bernd Flemisch (bernd@iws.uni-stuttgart.de) |
Last edited at | Nov 4, 2013 09:58 |
Closed by | Bernd Flemisch (bernd@iws.uni-stuttgart.de) |
Closed at | Nov 4, 2013 09:58 |
Closed in version | unknown (Id=0) |
Resolution | Implemented |
Description
The implemented Newton method needs properties like \\\"PrimaryVariables\\\" or \\\"SolutionVector\\\" from the considered problem/model. For example in the case of a two-phase problem the property \\\"PrimaryVariables\\\" is a FieldVector of two entries and the \\\"SolutionVector\\\" is a BlockVector of nDof-PrimaryVariables. Because of these properties, the Newton method assumes that all equations will be solved implicitly. But for example if we regard a decoupled model with a pressure equation and a transport equation, we are not able to solve only one of these equations with the Newton solver without major expense.
This problem could be solved by implementing new properties for the Newton method (like \\\"NewtonPrimaryVariables\\\", \\\"NewtonSolutionVector\\\" ...). So in the case where we only want to solve a transport equation, we can set the NewtonSolutionVector as the TransportSolutionType. Such additional properties would decouple the newton solver from the different models.