- pluginThe path to the compiled dynamic library for the plugin you want to use
C++ Type:FileName
Controllable:No
Description:The path to the compiled dynamic library for the plugin you want to use
AbaqusUExternalDB
Coupling user object to use Abaqus UEXTERNALDB subroutines in MOOSE
Description
The AbaqusUExternalDB
user object is used to execute an _Abaqus UEXTERNALDB_ user function at various stages of the simulation. The functions can be coded in Fortran (.f
and .f90
file extensions) or C/C++ (.c
and .C
file extensions) and must be located in the plugins
directory of the app.
Data exchange between UEXTERNALDB and UMAT may require to put both functions in the same translation unit (source file).
A description of the input and output parameters of the UEXTERNALDB user subroutines can be found in the Abaqus user manual.
MOOSE has no corresponding concept of an Abaqus simulation "step". MOOSE time steps correspond to Abaqus "increments". For now the Abaqus step number passed to the UEXTERNALDB routine is always zero.
Input Parameters
- abaqus_step0Abaqus step number. This is not the same as the increment number, which corresponds to the MOOSE time step and is computed automatically.
Default:0
C++ Type:int
Controllable:No
Description:Abaqus step number. This is not the same as the increment number, which corresponds to the MOOSE time step and is computed automatically.
- execute_onTIMESTEP_ENDThe list of flag(s) indicating when this object should be executed, the available options include NONE, INITIAL, LINEAR, NONLINEAR, TIMESTEP_END, TIMESTEP_BEGIN, FINAL, CUSTOM, ALWAYS.
Default:TIMESTEP_END
C++ Type:ExecFlagEnum
Controllable:No
Description:The list of flag(s) indicating when this object should be executed, the available options include NONE, INITIAL, LINEAR, NONLINEAR, TIMESTEP_END, TIMESTEP_BEGIN, FINAL, CUSTOM, ALWAYS.
- 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
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.
Optional Parameters
- allow_duplicate_execution_on_initialFalseIn the case where this UserObject is depended upon by an initial condition, allow it to be executed twice during the initial setup (once before the IC and again after mesh adaptivity (if applicable).
Default:False
C++ Type:bool
Controllable:No
Description:In the case where this UserObject is depended upon by an initial condition, allow it to be executed twice during the initial setup (once before the IC and again after mesh adaptivity (if applicable).
- 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.
- force_postauxFalseForces the UserObject to be executed in POSTAUX
Default:False
C++ Type:bool
Controllable:No
Description:Forces the UserObject to be executed in POSTAUX
- force_preauxFalseForces the UserObject to be executed in PREAUX
Default:False
C++ Type:bool
Controllable:No
Description:Forces the UserObject to be executed in PREAUX
- force_preicFalseForces the UserObject to be executed in PREIC during initial setup
Default:False
C++ Type:bool
Controllable:No
Description:Forces the UserObject to be executed in PREIC during initial setup
- 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
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.