# Compute Finite Strain in Cartesian System

Compute a strain increment and rotation increment for finite strains.

## Description

The finite strain mechanics approach used in the MOOSE tensor_mechanics module is the incremental corotational form from Rashid 1993.

In this form, the generic time increment under consideration is such that . The configurations of the material element under consideration at and are denoted by , and , respectively. The incremental motion over the time increment is assumed to be given in the form of the inverse of the deformation gradient of with respect to , which may be written as

(1) where is the incremental displacement field for the time step, and is the position vector of materials points in . Note that is NOT the deformation gradient, but rather the incremental deformation gradient of with respect to . Thus, , where is the total deformation gradient at time .

For this form, we assume (2)

In tensor mechanics, there are two decomposition options to obtain the strain increment and rotation increment: TaylorExpansion and EigenSolution, with the default set to TaylorExpansion. According to Rashid 1993, the stretching rate tensor and rotation matrix can be expressed in terms of 'incremental' deformation gradient as (3) and

(4)

## Taylor Expansion

According to Rashid 1993, the stretching rate tensor and rotation matrix can be approximated using Taylor expansion as: the approximated stretching rate tensor (5) the approximated rotation matrix (6) with (7) The sign of is set by examining the sign of .

## Eigen-Solution

The stretching rate tensor can be calculated by the eigenvalues and eigenvectors of . (8) with being the eigenvalue and matrix being constructed from the corresponding eigenvector. (9) the 'incremental' stretching tensor (10) and thus (11)

## Volumetric Locking Correction

In ComputeFiniteStrain, is calculated in the computeStrain method, including a volumetric locking correction of (12) where is the average value for the entire element. The strain increment and the rotation increment are calculated in computeQpStrain(). Once the strain increment is calculated, it is added to the total strain from . The total strain from must then be rotated using the rotation increment.

## Example Input File Syntax

The finite strain calculator can be activated in the input file through the use of the TensorMechanics Master Action, as shown below.

[./TensorMechanics]
[./Master]
[./all]
strain = FINITE
[../]
[../]
[../]
(moose/modules/tensor_mechanics/test/tests/finite_strain_elastic/finite_strain_elastic_new_test.i)
note:Use of the Tensor Mechanics Master Action Recommended

The TensorMechanics Master Action is designed to automatically determine and set the strain and stress divergence parameters correctly for the selected strain formulation. We recommend that users employ the TensorMechanics Master Action whenever possible to ensure consistency between the test function gradients and the strain formulation selected.

Although not recommended, it is possible to directly use the ComputeFiniteStrain material in the input file.

[./strain]
type = ComputeFiniteStrain
block = 0
displacements = 'disp_x disp_y disp_z'
[../]

## Input Parameters

• displacementsThe displacements appropriate for the simulation geometry and coordinate system

C++ Type:std::vector

Description:The displacements appropriate for the simulation geometry and coordinate system

### Required Parameters

• global_strainOptional material property holding a global strain tensor applied to the mesh as a whole

C++ Type:MaterialPropertyName

Description:Optional material property holding a global strain tensor applied to the mesh as a whole

• decomposition_methodTaylorExpansionMethods to calculate the strain and rotation increments

Default:TaylorExpansion

C++ Type:MooseEnum

Description:Methods to calculate the strain and rotation increments

• computeTrueWhen false, MOOSE will not call compute methods on this material. The user must call computeProperties() after retrieving the Material via MaterialPropertyInterface::getMaterial(). Non-computed Materials are not sorted for dependencies.

Default:True

C++ Type:bool

Description:When false, MOOSE will not call compute methods on this material. The user must call computeProperties() after retrieving the Material via MaterialPropertyInterface::getMaterial(). Non-computed Materials are not sorted for dependencies.

• 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

Description:Optional parameter that allows the user to define multiple mechanics material systems on the same block, i.e. for multiple phases

• eigenstrain_namesList of eigenstrains to be applied in this strain calculation

C++ Type:std::vector

Description:List of eigenstrains to be applied in this strain calculation

• volumetric_locking_correctionFalseFlag to correct volumetric locking

Default:False

C++ Type:bool

Description:Flag to correct volumetric locking

• boundaryThe list of boundary IDs from the mesh where this boundary condition applies

C++ Type:std::vector

Description:The list of boundary IDs from the mesh where this boundary condition applies

• blockThe list of block ids (SubdomainID) that this object will be applied

C++ Type:std::vector

Description:The list of block ids (SubdomainID) that this object will be applied

### Optional Parameters

• control_tagsAdds user-defined labels for accessing object parameters via control logic.

C++ Type:std::vector

Description:Adds user-defined labels for accessing object parameters via control logic.

• enableTrueSet the enabled status of the MooseObject.

Default:True

C++ Type:bool

Description:Set the enabled status of the MooseObject.

• seed0The seed for the master random number generator

Default:0

C++ Type:unsigned int

Description:The seed for the master random number generator

• implicitTrueDetermines whether this object is calculated using an implicit or explicit form

Default:True

C++ Type:bool

Description:Determines whether this object is calculated using an implicit or explicit form

• 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 computeSubdomainProperties() 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

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 computeSubdomainProperties() for the 0th quadrature point, and then copy that value to the other qps. Evaluations on element qps will be skipped

• output_propertiesList of material properties, from this material, to output (outputs must also be defined to an output type)

C++ Type:std::vector

Description:List of material properties, from this material, to output (outputs must also be defined to an output type)

• outputsnone Vector of output names were you would like to restrict the output of variables(s) associated with this object

Default:none

C++ Type:std::vector

Description:Vector of output names were you would like to restrict the output of variables(s) associated with this object