- displacementsThe displacements appropriate for the simulation geometry and coordinate system
C++ Type:std::vector<VariableName>
Unit:(no unit assumed)
Controllable:No
Description:The displacements appropriate for the simulation geometry and coordinate system
ComputeAxisymmetric1DIncrementalStrain / ADComputeAxisymmetric1DIncrementalStrain
Compute strain increment for small strains in an axisymmetric 1D problem
Description
ComputeAxisymmetric1DIncrementalStrain computes the small strain increment for a 1D axisymmetric generalized plane strain model. When the solid mechanics action is used with use_automatic_differentiation = true, the action selects ADComputeAxisymmetric1DIncrementalStrain for the same strain formulation.
This material assumes symmetry about the axis and must be used on blocks with COORD_TYPE = RZ. The radial coordinate is the physical coordinate. In the 1D strain tensor, MOOSE maps the radial strain to the rr or xx component, the generalized plane strain to the axial yy component, and the hoop strain to the zz component. The stress divergence is handled by the axisymmetric RZ kernels, such as StressDivergenceRZTensors.
The out-of-plane strain can be supplied by either "scalar_out_of_plane_strain" or "out_of_plane_strain", but not both. Scalar out-of-plane strain values are commonly used by Generalized Plane Strain models. If multiple scalar components are coupled, "subblock_index_provider" selects which scalar component applies to the current element; without that user object, component 0 is used.
For the AD object, current displacement and out-of-plane strain values are AD values. Old state values used to form the strain increment remain regular values.
1D Axisymmetric Strain Formulation
The axisymmetric model uses the cylindrical coordinates, , , and , where the line in the direction is rotated about the axis in the direction. The small strain increment is (1) where and are the current and old displacement-gradient tensors, (2) The old displacement-gradient tensor uses strain-expression values from the previous time step. The tensor components are (3) where is the supplied out-of-plane strain. In the MOOSE tensor storage for this 1D formulation, the generalized plane strain component is stored in yy and the hoop component is stored in zz.
Example Input File Syntax
The following generalized plane strain test uses the scalar out-of-plane strain option with ComputeAxisymmetric1DIncrementalStrain.
[./strain]
type = ComputeAxisymmetric1DIncrementalStrain
eigenstrain_names = eigenstrain
scalar_out_of_plane_strain = scalar_strain_yy
[../](modules/solid_mechanics/test/tests/1D_axisymmetric/axisymm_gps_incremental.i)The coupled scalar variable is defined in the same input file.
[./scalar_strain_yy]
order = FIRST
family = SCALAR
[../](modules/solid_mechanics/test/tests/1D_axisymmetric/axisymm_gps_incremental.i)Input Parameters
- base_nameOptional parameter that allows the user to define multiple mechanics material systems on the same block, i.e. for multiple phases
C++ Type:std::string
Controllable:No
Description:Optional parameter that allows the user to define multiple mechanics material systems on the same block, i.e. for multiple phases
- blockThe list of blocks (ids or names) that this object will be applied
C++ Type:std::vector<SubdomainName>
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>
Controllable:No
Description:The list of boundaries (ids or names) from the mesh where this object applies
- computeTrueWhen false, MOOSE will not call compute methods on this material. The user must call computeProperties() after retrieving the MaterialBase via MaterialBasePropertyInterface::getMaterialBase(). Non-computed MaterialBases are not sorted for dependencies.
Default:True
C++ Type:bool
Controllable:No
Description:When false, MOOSE will not call compute methods on this material. The user must call computeProperties() after retrieving the MaterialBase via MaterialBasePropertyInterface::getMaterialBase(). Non-computed MaterialBases are not sorted for dependencies.
- constant_onNONEWhen ELEMENT, MOOSE will only call computeQpProperties() for the 0th quadrature point, and then copy that value to the other qps.When SUBDOMAIN, MOOSE will only call computeQpProperties() for the 0th quadrature point, and then copy that value to the other qps. Evaluations on element qps will be skipped
Default:NONE
C++ Type:MooseEnum
Controllable:No
Description:When ELEMENT, MOOSE will only call computeQpProperties() for the 0th quadrature point, and then copy that value to the other qps.When SUBDOMAIN, MOOSE will only call computeQpProperties() for the 0th quadrature point, and then copy that value to the other qps. Evaluations on element qps will be skipped
- declare_suffixAn optional suffix parameter that can be appended to any declared 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 declared properties. The suffix will be prepended with a '_' character.
- eigenstrain_namesList of eigenstrains to be applied in this strain calculation
C++ Type:std::vector<MaterialPropertyName>
Unit:(no unit assumed)
Controllable:No
Description:List of eigenstrains to be applied in this strain calculation
- global_strainOptional material property holding a global strain tensor applied to the mesh as a whole
C++ Type:MaterialPropertyName
Unit:(no unit assumed)
Controllable:No
Description:Optional material property holding a global strain tensor applied to the mesh as a whole
- out_of_plane_strainNonlinear variable for axisymmetric 1D problem
C++ Type:std::vector<VariableName>
Unit:(no unit assumed)
Controllable:No
Description:Nonlinear variable for axisymmetric 1D problem
- scalar_out_of_plane_strainScalar variable for axisymmetric 1D problem
C++ Type:std::vector<VariableName>
Unit:(no unit assumed)
Controllable:No
Description:Scalar variable for axisymmetric 1D problem
- subblock_index_providerSubblockIndexProvider user object name
C++ Type:UserObjectName
Controllable:No
Description:SubblockIndexProvider user object name
- volumetric_locking_correctionFalseFlag to correct volumetric locking
Default:False
C++ Type:bool
Controllable:No
Description:Flag to correct volumetric locking
Optional Parameters
- control_tagsAdds user-defined labels for accessing object parameters via control logic.
C++ Type:std::vector<std::string>
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
Controllable:Yes
Description:Set the enabled status of the MooseObject.
- implicitTrueDetermines whether this object is calculated using an implicit or explicit form
Default:True
C++ Type:bool
Controllable:No
Description:Determines whether this object is calculated using an implicit or explicit form
- search_methodnearest_node_connected_sidesChoice of search algorithm. All options begin by finding the nearest node in the primary boundary to a query point in the secondary boundary. In the default nearest_node_connected_sides algorithm, primary boundary elements are searched iff that nearest node is one of their nodes. This is fast to determine via a pregenerated node-to-elem map and is robust on conforming meshes. In the optional all_proximate_sides algorithm, primary boundary elements are searched iff they touch that nearest node, even if they are not topologically connected to it. This is more CPU-intensive but is necessary for robustness on any boundary surfaces which has disconnections (such as Flex IGA meshes) or non-conformity (such as hanging nodes in adaptively h-refined meshes).
Default:nearest_node_connected_sides
C++ Type:MooseEnum
Controllable:No
Description:Choice of search algorithm. All options begin by finding the nearest node in the primary boundary to a query point in the secondary boundary. In the default nearest_node_connected_sides algorithm, primary boundary elements are searched iff that nearest node is one of their nodes. This is fast to determine via a pregenerated node-to-elem map and is robust on conforming meshes. In the optional all_proximate_sides algorithm, primary boundary elements are searched iff they touch that nearest node, even if they are not topologically connected to it. This is more CPU-intensive but is necessary for robustness on any boundary surfaces which has disconnections (such as Flex IGA meshes) or non-conformity (such as hanging nodes in adaptively h-refined meshes).
- seed0The seed for the master random number generator
Default:0
C++ Type:unsigned int
Controllable:No
Description:The seed for the master random number generator
Advanced Parameters
- output_propertiesList of material properties, from this material, to output (outputs must also be defined to an output type)
C++ Type:std::vector<std::string>
Controllable:No
Description:List of material properties, from this material, to output (outputs must also be defined to an output type)
- outputsnone Vector of output names where you would like to restrict the output of variables(s) associated with this object
Default:none
C++ Type:std::vector<OutputName>
Controllable:No
Description:Vector of output names where you would like to restrict the output of variables(s) associated with this object
Outputs Parameters
- 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.
- 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
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.