Materials System
The material system is the primary mechanism for defining spatially varying properties. The system allows properties to be defined in a single object (a Material
) and shared among the many other systems such as the Kernel or BoundaryCondition systems. Material objects are designed to directly couple to solution variables as well as other materials and therefore allow for capturing the true nonlinear behavior of the equations.
The material system relies on a producer/consumer relationship: Material
objects produce properties and other objects (including materials) consume these properties.
The properties are produced on demand, thus the computed values are always up to date. For example, a property that relies on a solution variable (e.g., thermal conductivity as function of temperature) will be computed with the current temperature during the solve iterations, so the properties are tightly coupled.
The material system supports the use of automatic differentiation for property calculations, as such there are two approaches for producing and consuming properties: with and without automatic differentiation. The following sections detail the producing and consuming properties using the two approaches. To further understand automatic differentiation, please refer to the Automatic Differentiation page for more information.
The proceeding sections briefly describe the different aspects of a Material
object for producing and computing the properties as well as how other objects consume the properties. For an example of how a Material
object is created and used please refer to ex08_materials.md.
Producing/Computing Properties
Properties must be produced by a Material
object by declaring the property with one of two methods:
declareProperty<TYPE>("property_name")
declares a property with a name "property_name" to be computed by theMaterial
object.declareADProperty<TYPE>
declares a property with a name "property_name" to be computed by theMaterial
object that will include automatic differentiation.
The TYPE
is any valid C++ type such an int
or Real
or std::vector<Real>
. The properties must then be computed within the computeQpProperties
method defined within the object.
The property name is an arbitrary name of the property, this name should be set such that it corresponds to the value be computed (e.g., "diffusivity"). The name provided here is the same name that will be used for consuming the property. More information on names is provided in Property Names section below.
For example, consider a simulation that requires a diffusivity term. In the Material
object header a property is declared (in the C++ since) as follows.
MaterialProperty<Real> & _diffusivity;
(moose/examples/ex08_materials/include/materials/ExampleMaterial.h)All properties will either be a MaterialProperty<TYPE>
or ADMaterialProperty<TYPE>
and must be a non-const reference. Again, the TYPE
can be any C++ type. In this example, a scalar Real
number is being used.
In the source file the reference is initialized in the initialization list using the aforementioned declare functions as follows. This declares the property (in the material property sense) to be computed.
_diffusivity(declareProperty<Real>("diffusivity")),
(moose/examples/ex08_materials/src/materials/ExampleMaterial.C)The final step for producing a property is to compute the value. The computation occurs within a Material
object computeQpProperties
method. As the method name suggests, the purpose of the method is to compute the values of properties at a quadrature point. This method is a virtual method that must be overridden. To do this, in the header the virtual method is declared (again in the C++ sense).
virtual void computeQpProperties() override;
(moose/examples/ex08_materials/include/materials/ExampleMaterial.h)In the source file the method is defined. For the current example this definition computes the "diffusivity" as well another term, refer to ex08_materials.md.
ExampleMaterial::computeQpProperties()
{
// Diffusivity is the value of the interpolated piece-wise function described by the user
_diffusivity[_qp] = _piecewise_func.sample(_q_point[_qp](2));
// Convection velocity is set equal to the gradient of the variable set by the user.
_convection_velocity[_qp] = _diffusion_gradient[_qp];
}
(moose/examples/ex08_materials/src/materials/ExampleMaterial.C)The purpose of the content of this method is to assign values for the properties at a quadrature point. Recall that "_diffusivity" is a reference to a MaterialProperty
type. The MaterialProperty
type is a container that stores the values of a property for each quadrature point. Therefore, this container must be indexed by _qp
to compute the value for a specific quadrature point.
ExampleMaterial
can call isPropertyActive(_diffusivity.id())
in its computeQpProperties
to check whether this property is consumed during the run-time. This function provides a capability of skipping evaluations of certain material properties within a material when such evaluations are costly for performance optimization. MOOSE calls materials to do the evaluations when needed. This isPropertyActive
routine gives code developers a finer control on the material property evaluation.
Consuming Properties
Objects that require material properties consume them using one of two functions
getMaterialProperty<TYPE>("property_name")
retrieves a property with a name "property_name" to be consumed by the object.getADMaterialProperty<TYPE>("property_name")
retrieves a property with a name "property_name" to be consumed by the object that will include automatic differentiation.
For an object to consume a property the same basic procedure is followed. First in the consuming objects header file a MaterialProperty
with the correct type (e.g., Real
for the diffusivity example) is declared (in the C++ sense) as follows. Notice, that the member variable is a const reference. The const is important. Consuming objects cannot modify a property, it only uses the property so it is marked to be constant.
const MaterialProperty<Real> & _diffusivity;
(moose/examples/ex08_materials/include/kernels/ExampleDiffusion.h)In the source file the reference is initialized in the initialization list using the aforementioned get methods. This method initializes the _diffusivity
member variable to reference the desired value of the property as computed by the material object.
: Diffusion(parameters), _diffusivity(getMaterialProperty<Real>("diffusivity"))
(moose/examples/ex08_materials/src/kernels/ExampleDiffusion.C)The name used in the get method, "diffusivity", in this case is not arbitrary. This name corresponds with the name used to declare the property in the material object.
If a material property is declared for automatic differentiation (AD) using declareADProperty
then it must be consumed with the getADMaterialProperty
. The same is true for non-automatic differentiation; properties declared with declareProperty
must be consumed with the getMaterialProperty
method.
Optional Properties
Objects can weakly couple to material properties that may or may not exist.
getOptionalMaterialProperty<TYPE>("property_name")
retrieves an optional property with a name "property_name" to be consumed by the object.getOptionalADMaterialProperty<TYPE>("property_name")
retrieves an optional property with a name "property_name" to be consumed by the object that will include automatic differentiation.
This API returns a reference to an optional material property (OptionalMaterialProperty
or OptionalADMaterialProperty
). If the requested property is not provided by any material this reference will evaluate to false
. It is the consuming object's responsibility to check for this before accessing the material property data. Note that the state of the returned reference is only finalized _after_ all materials have been constructed, so a validity check must _not_ be made in the constructor of a material class but either at time of first use in computeQpProperties
or in initialSetup
.
Property Names
When creating a Material object and declaring the properties that shall be computed, it is often desirable to allow for the property name to be changed via the input file. This may be accomplished by adding an input parameter for assigning the name. For example, considering the example above the following code snippet adds an input parameter, "diffusivity_name", that allows the input file to set the name of the diffusivity property, but by default the name remains "diffusivity".
params.addParam<MaterialPropertyName>("diffusivity_name", "diffusivity",
"The name of the diffusivity material property.");
In the material object, the declare function is simply changed to use the parameter name rather than string by itself. By default a property will be declared with the name "diffusivity".
_diffusivity_name(declareProperty<Real>("diffusivity_name")),
(moose/examples/ex08_materials/src/materials/ExampleMaterial.C)However, if the user wants to alter this name to something else, such as "not_diffusivity" then the input parameter "diffusivity_name" is simply added to the input file block for the material.
[Materials]
[example]
type = ExampleMaterial
diffusivity_name = not_diffusivity
[]
[]
On the consumer side, the get method will now be required to use the name "not_diffusivity" to retrieve the property. Consuming objects can also use the same procedure to allow for custom property names by adding a parameter and using the parameter name in the get method in the same fashion.
Default Material Properties
The MaterialPropertyName
input parameter also provides the ability to set default values for scalar (Real
) properties. In the above example, the input file can use number or parsed function (see ParsedFunction) to define a the property value. For example, the input snippet above could set a constant value.
[Materials]
[example]
type = ExampleMaterial
diffusivity_name = 12345
[]
[]
Stateful Material Properties
In general properties are computed on demand and not stored. However, in some cases values of material properties from a previous timestep may be required. To access properties two methods exist:
getMaterialPropertyOld<TYPE>
returns a reference to the property from the previous timestep.getMaterialPropertyOlder<TYPE>
returns a reference to the property from two timesteps before the current.
This is often referred to as a "state" variable, in MOOSE we refer to them as "stateful material properties." As stated, material properties are usually computed on demand.
When a stateful property is requested through one of the above methods this is no longer the case. When it is computed the value is also stored for every quadrature point on every element. As such, stateful properties can become memory intensive, especially if the property being stored is a vector or tensor value.
Material Property Output
Output of Material
properties is enabled by setting the "outputs" parameter. The following example creates two additional variables called "mat1" and "mat2" that will show up in the output file.
[Materials]
[block_1]
type = OutputTestMaterial
block = 1
output_properties = 'real_property tensor_property'
outputs = exodus
variable = u
[]
[block_2]
type = OutputTestMaterial
block = 2
output_properties = 'vector_property tensor_property'
outputs = exodus
variable = u
[]
[]
[Outputs]
exodus = true
[]
(moose/test/tests/materials/output/output_block.i)Material
properties can be of arbitrary (C++) type, but not all types can be output. The following table lists the types of properties that are available for automatic output.
Type | AuxKernel | Variable Name(s) |
---|---|---|
Real | MaterialRealAux | prop |
RealVectorValue | MaterialRealVectorValueAux | prop_1, prop_2, and prop_3 |
RealTensorValue | MaterialRealTensorValueAux | prop_11, prop_12, prop_13, prop_21, etc. |
Material sorting
Materials are sorted such that one material may consume a property produced by another material and know that the consumed property will be up-to-date, e.g. the producer material will execute before the consumer material. If a cyclic dependency is detected between two materials, then MOOSE will produce an error.
Functor Material Properties
Functor materials are a special kind of materials used for on-the-fly material property evaluation. Please refer to the syntax page for FunctorMaterials for more information.
Advanced Topics
Evaluation of Material Properties on Element Faces
MOOSE creates three copies of a non-boundary restricted material for evaluations on quadrature points of elements, element faces on both the current element side and the neighboring element side. The name of the element interior material is the material name from the input file, while the name of the element face material is the material name appended with _face
and the name of the neighbor face material is the material name appended with _neighbor
. The element material can be identified in a material with its member variable _bnd=false
. The other two copies have _bnd=true
. The element face material and neighbor face material differentiate with each other by the value of another member variable _neighbor
. If a material declares multiple material properties and some of them are not needed on element faces, users can switch off their declaration and evaluation based on member variable _bnd
.
Interface Material Objects
MOOSE allows a material to be defined on an internal boundary of a mesh with a specific material type InterfaceMaterial
. Material properties declared in interface materials are available on both sides of the boundary. Interface materials allows users to evaluate the properties on element faces based on quantities on both sides of the element face. Interface materials are often used along with InterfaceKernel.
Discrete Material Objects
A "Discrete" Material
is an object that may be detached from MOOSE and computed explicitly from other objects. An object inheriting from MaterialPropertyInterface may explicitly call the compute methods of a Material
object via the getMaterial
method.
The following should be considered when computing Material
properties explicitly.
It is possible to disable the automatic computation of a
Material
object by MOOSE by setting thecompute=false
parameter.When
compute=false
is set the compute method (computeQpProperties
) is not called by MOOSE, instead it must be called explicitly in your application using thecomputeProperties
method that accepts a quadrature point index.When
compute=false
an additional method should be defined,resetQpProperties
, which sets the properties to a safe value (e.g., 0) for later calls to the compute method. Not doing this can lead to erroneous material properties values.
The original intent for this functionality was to enable to ability for material properties to be computed via iteration by another object, as in the following example. First, consider define a material (RecomputeMaterial
) that computes the value of a function and its derivative.
and
where v is known value and not a function of p. The following is the compute portion of this object.
void
RecomputeMaterial::computeQpProperties()
{
Real x = _p[_qp];
_f[_qp] = x * x - _constant;
_f_prime[_qp] = 2 * x;
}
(moose/test/src/materials/RecomputeMaterial.C)Second, define another material (NewtonMaterial
) that computes the value of using Newton iterations. This material declares a material property (_p
) which is what is solved for by iterating on the material properties containing f
and f'
from RecomputeMaterial
. The _discrete
member is a reference to a Material
object retrieved with getMaterial
.
void
NewtonMaterial::computeQpProperties()
{
_p[_qp] = 0.5; // initial guess
// Only attempt to solve if iterations are to be taken. This is usually not required, but needed
// here to retain the old test behavior that would not trigger a discrete material evaluation. The
// NestedSolve class will always evaluate the residual for the initial guess (and will return a
// success state if the initial guess was exact).
if (getParam<unsigned int>("max_iterations") > 0)
_nested_solve.nonlinear(
_p[_qp],
// Lambda function to compute residual and jacobian. The initial guess is not
// used here as it (_p) is directly coupled in the discrete material.
[&](const Real & /*guess*/, Real & r, Real & j)
{
_discrete->computePropertiesAtQp(_qp);
r = _f[_qp];
j = _f_prime[_qp];
});
}
(moose/test/src/materials/NewtonMaterial.C)To create and use a "Discrete" Material
use the following to guide the process.
Create a
Material
object by, in typical MOOSE fashion, inheriting from theMaterial
object in your own application.In your input file, set
compute=false
for this new object.From within another object (e.g., another Material) that inherits from
MaterialPropertyInterface
call thegetMaterial
method. Note, this method returns a reference to aMaterial
object, be sure to include&
when calling or declaring the variable.When needed, call the
computeProperties
method of theMaterial
being sure to provide the current quadrature point index to the method (_qp
in most cases).
Available Objects
- Moose App
- ADCoupledValueFunctionMaterialCompute a function value from coupled variables
- ADDerivativeParsedMaterialParsed Function Material with automatic derivatives.
- ADDerivativeSumMaterialMeta-material to sum up multiple derivative materials
- ADGenericConstantMaterialDeclares material properties based on names and values prescribed by input parameters.
- ADGenericConstantRankTwoTensorObject for declaring a constant rank two tensor as a material property.
- ADGenericConstantSymmetricRankTwoTensorObject for declaring a constant symmetric rank two tensor as a material property.
- ADGenericConstantVectorMaterialDeclares material properties based on names and vector values prescribed by input parameters.
- ADGenericFunctionMaterialMaterial object for declaring properties that are populated by evaluation of Function object.
- ADGenericFunctionRankTwoTensorMaterial object for defining rank two tensor properties using functions.
- ADGenericFunctionVectorMaterialMaterial object for declaring vector properties that are populated by evaluation of Function objects.
- ADParsedMaterialParsed expression Material.
- ADPiecewiseConstantByBlockMaterialComputes a property value on a per-subdomain basis
- ADPiecewiseLinearInterpolationMaterialCompute a property using a piecewise linear interpolation to define its dependence on a variable
- ADVectorFromComponentVariablesMaterialComputes a vector material property from coupled variables
- CoupledValueFunctionMaterialCompute a function value from coupled variables
- DerivativeParsedMaterialParsed Function Material with automatic derivatives.
- DerivativeSumMaterialMeta-material to sum up multiple derivative materials
- GenericConstant2DArrayA material evaluating one material property in type of RealEigenMatrix
- GenericConstantArrayA material evaluating one material property in type of RealEigenVector
- GenericConstantMaterialDeclares material properties based on names and values prescribed by input parameters.
- GenericConstantRankTwoTensorObject for declaring a constant rank two tensor as a material property.
- GenericConstantSymmetricRankTwoTensorObject for declaring a constant symmetric rank two tensor as a material property.
- GenericConstantVectorMaterialDeclares material properties based on names and vector values prescribed by input parameters.
- GenericFunctionMaterialMaterial object for declaring properties that are populated by evaluation of Function object.
- GenericFunctionRankTwoTensorMaterial object for defining rank two tensor properties using functions.
- GenericFunctionVectorMaterialMaterial object for declaring vector properties that are populated by evaluation of Function objects.
- InterpolatedStatefulMaterialRankFourTensorAccess old state from projected data.
- InterpolatedStatefulMaterialRankTwoTensorAccess old state from projected data.
- InterpolatedStatefulMaterialRealAccess old state from projected data.
- InterpolatedStatefulMaterialRealVectorValueAccess old state from projected data.
- MaterialADConverterConverts regular material properties to AD properties and vice versa
- MaterialConverterConverts regular material properties to AD properties and vice versa
- MaterialFunctorConverterConverts functor to non-AD and AD regular material properties
- ParsedMaterialParsed expression Material.
- PiecewiseConstantByBlockMaterialComputes a property value on a per-subdomain basis
- PiecewiseLinearInterpolationMaterialCompute a property using a piecewise linear interpolation to define its dependence on a variable
- RankFourTensorMaterialADConverterConverts regular material properties to AD properties and vice versa
- RankFourTensorMaterialConverterConverts regular material properties to AD properties and vice versa
- RankTwoTensorMaterialADConverterConverts regular material properties to AD properties and vice versa
- RankTwoTensorMaterialConverterConverts regular material properties to AD properties and vice versa
- VectorFromComponentVariablesMaterialComputes a vector material property from coupled variables
- VectorMaterialFunctorConverterConverts functor to non-AD and AD regular material properties
- Crane App
- ADEEDFRateConstantTownsendAdds townsend coefficient for a reaction as a material property. Note that this material is only intended to be used with the plasma transport software, Zapdos. For any other MOOSE application (or when using Crane by itself) it is recommended to use rate coefficient formulation rather than the townsend coefficients, which may be done with the (AD)EEDFRateConstant material.
- ADGenericRateConstant
- ADZapdosEEDFRateConstant
- DiffusionRateTemp
- EEDFRateConstant
- EEDFRateConstantTownsend
- ElectricField
- GenericRateConstant
- HeatCapacityRatio
- InterpolatedCoefficientLinearAdds townsend coefficient for a reaction as a material property. Note that this material is only intended to be used with the plasma transport software, Zapdos. For any other MOOSE application (or when using Crane by itself) it is recommended to use rate coefficient formulation rather than the townsend coefficients, which may be done with the (AD)EEDFRateConstant material.
- InterpolatedCoefficientSplineAdds townsend coefficient for a reaction as a material property. Note that this material is only intended to be used with the plasma transport software, Zapdos. For any other MOOSE application (or when using Crane by itself) it is recommended to use rate coefficient formulation rather than the townsend coefficients, which may be done with the (AD)EEDFRateConstant material.
- SpeciesSum
- SuperelasticReactionRate
- ZapdosEEDFRateConstant
- Zapdos App
- ADGasElectronMomentsMaterial properties of electrons(Defines reaction properties with rate coefficients)
- ADHeavySpecies
- ADSurfaceChargeAdds a surface charge material property based on the rate of change of the total charged flux to a boundary. (NOTE: this material is meant to be boundary-restricted.)
- GasMaterial properties of electron and ions for argon gas(Defines reaction properties with Townsend coefficients)
- GasBaseMaterial properties of electrons(Defines reaction properties with Townsend coefficients)
- GasElectronMomentsMaterial properties of electrons(Defines reaction properties with rate coefficients)
- HeavySpecies
- WaterMaterial properties of water species
Available Actions
- Moose App
- AddMaterialActionAdd a Material object to the simulation.