- rank_two_tensorThe rank two material tensor name
C++ Type:MaterialPropertyName
Unit:(no unit assumed)
Controllable:No
Description:The rank two material tensor name
- variableThe name of the variable that this object applies to
C++ Type:AuxVariableName
Unit:(no unit assumed)
Controllable:No
Description:The name of the variable that this object applies to
Rank Two Scalar Aux
Compute a scalar property of a RankTwoTensor
Description
This AuxKernel uses a set of functions to compute scalar quantities such as invariants and components in specified directions from rank-2 tensors such as stress or strain. See RankTwoScalarTools for further information.
Example Input File Syntax
[./vonmises]
type = RankTwoScalarAux
rank_two_tensor = stress
variable = vonmises
scalar_type = VonMisesStress
execute_on = timestep_end
[../]
(moose/modules/solid_mechanics/test/tests/material_limit_time_step/elas_plas/nafems_nl1_lim.i)An AuxVariable is required to store the AuxKernel information. Note that the name of the AuxVariable is used as the argument for the variable
input parameter in the RankTwoScalarAux
block.
[./vonmises]
order = CONSTANT
family = MONOMIAL
[../]
(moose/modules/solid_mechanics/test/tests/material_limit_time_step/elas_plas/nafems_nl1_lim.i)As with the RankTwoAux AuxKernel, RankTwoScalarAux
requires the inclusion of an AuxVariable block for each AuxKernel block.
AuxVariable Order
Results will have different quality based on the AuxVariable:
Elemental Constant Monomial Using an AuxVariable with
family = MONOMIAL
andorder = CONSTANT
will give a constant value of the AuxVariable for the entire element, which is computed by taking a volume-weighted average of the integration point quantities. This is the default option using SolidMechanics Action and requires the least computational cost.Elemental Higher-order Monomial Using an AuxVariable with
family = MONOMIAL
andorder = FIRST
or higher will result in fields that vary linearly (or with higher order) within each element. Because the Exodus mesh format does not support higher-order elemental variables, these AuxVariables are output by libMesh as nodal variables for visualization purposes. Using higher order monomial variables in this way can produce smoother visualizations of results for a properly converged simulation.Nodal Lagrange Using an AuxVariable with
family = LAGRANGE
will result in a smooth nodal field of the material property, constructed using nodal patch recovery.patch_polynomial_order
is set to equal the order of the AuxVariable by default. Use this option for the best (smoothest, most accurate) results, but there is some additional computational cost. Furthermore, this method is suitable only for serial simulations at present.
Input Parameters
- blockThe list of blocks (ids or names) that this object will be applied
C++ Type:std::vector<SubdomainName>
Unit:(no unit assumed)
Controllable:No
Description:The list of blocks (ids or names) that this object will be applied
- boundaryThe list of boundaries (ids or names) from the mesh where this object applies
C++ Type:std::vector<BoundaryName>
Unit:(no unit assumed)
Controllable:No
Description:The list of boundaries (ids or names) from the mesh where this object applies
- check_boundary_restrictedTrueWhether to check for multiple element sides on the boundary in the case of a boundary restricted, element aux variable. Setting this to false will allow contribution to a single element's elemental value(s) from multiple boundary sides on the same element (example: when the restricted boundary exists on two or more sides of an element, such as at a corner of a mesh
Default:True
C++ Type:bool
Unit:(no unit assumed)
Controllable:No
Description:Whether to check for multiple element sides on the boundary in the case of a boundary restricted, element aux variable. Setting this to false will allow contribution to a single element's elemental value(s) from multiple boundary sides on the same element (example: when the restricted boundary exists on two or more sides of an element, such as at a corner of a mesh
- direction0 0 1Direction vector
Default:0 0 1
C++ Type:libMesh::Point
Unit:(no unit assumed)
Controllable:No
Description:Direction vector
- execute_onLINEAR TIMESTEP_ENDThe list of flag(s) indicating when this object should be executed. For a description of each flag, see https://mooseframework.inl.gov/source/interfaces/SetupInterface.html.
Default:LINEAR TIMESTEP_END
C++ Type:ExecFlagEnum
Unit:(no unit assumed)
Controllable:No
Description:The list of flag(s) indicating when this object should be executed. For a description of each flag, see https://mooseframework.inl.gov/source/interfaces/SetupInterface.html.
- point10 0 0Start point for axis used to calculate some cylindrical material tensor quantities
Default:0 0 0
C++ Type:libMesh::Point
Unit:(no unit assumed)
Controllable:No
Description:Start point for axis used to calculate some cylindrical material tensor quantities
- point20 1 0End point for axis used to calculate some material tensor quantities
Default:0 1 0
C++ Type:libMesh::Point
Unit:(no unit assumed)
Controllable:No
Description:End point for axis used to calculate some material tensor quantities
- prop_getter_suffixAn optional suffix parameter that can be appended to any attempt to retrieve/get material properties. The suffix will be prepended with a '_' character.
C++ Type:MaterialPropertyName
Unit:(no unit assumed)
Controllable:No
Description:An optional suffix parameter that can be appended to any attempt to retrieve/get material properties. The suffix will be prepended with a '_' character.
- scalar_typeType of scalar output
C++ Type:MooseEnum
Unit:(no unit assumed)
Controllable:No
Description:Type of scalar output
- use_interpolated_stateFalseFor the old and older state use projected material properties interpolated at the quadrature points. To set up projection use the ProjectedStatefulMaterialStorageAction.
Default:False
C++ Type:bool
Unit:(no unit assumed)
Controllable:No
Description:For the old and older state use projected material properties interpolated at the quadrature points. To set up projection use the ProjectedStatefulMaterialStorageAction.
Optional Parameters
- control_tagsAdds user-defined labels for accessing object parameters via control logic.
C++ Type:std::vector<std::string>
Unit:(no unit assumed)
Controllable:No
Description:Adds user-defined labels for accessing object parameters via control logic.
- enableTrueSet the enabled status of the MooseObject.
Default:True
C++ Type:bool
Unit:(no unit assumed)
Controllable:Yes
Description:Set the enabled status of the MooseObject.
- patch_polynomial_orderPolynomial order used in least squares fitting of material property over the local patch of elements connected to a given node
C++ Type:MooseEnum
Unit:(no unit assumed)
Controllable:No
Description:Polynomial order used in least squares fitting of material property over the local patch of elements connected to a given node
- seed0The seed for the master random number generator
Default:0
C++ Type:unsigned int
Unit:(no unit assumed)
Controllable:No
Description:The seed for the master random number generator
- selected_qpEvaluate the tensor at this quadpoint. This option only needs to be used if you are interested in a particular quadpoint in each element: otherwise do not include this parameter in your input file
C++ Type:unsigned int
Unit:(no unit assumed)
Controllable:No
Description:Evaluate the tensor at this quadpoint. This option only needs to be used if you are interested in a particular quadpoint in each element: otherwise do not include this parameter in your input file
- use_displaced_meshFalseWhether or not this object should use the displaced mesh for computation. Note that in the case this is true but no displacements are provided in the Mesh block the undisplaced mesh will still be used.
Default:False
C++ Type:bool
Unit:(no unit assumed)
Controllable:No
Description:Whether or not this object should use the displaced mesh for computation. Note that in the case this is true but no displacements are provided in the Mesh block the undisplaced mesh will still be used.