Layered1DContactInterfaceStress

Retrieves the out of plane stress and the coordinate transformation value at a particular boundary. These computations aid in the approximation of the action of friction on a contact interface.

Description

Layered1DContactInterfaceStress retrieves the coordinate transformation and out-of-plane stiffness near the contact interface. This elemental user object supplies this information upon request from the nodal user object Layered1DFrictionalForce, which computes frictional forces for a layered one-dimensional simulation.

commentnote:This capability only works for serial runs
commentnote:Number of layers

This object assumes that the number of layers provided as input correspond to those that can have mechanical contact, i.e. plenum layers can be disregarded.

commentnote:Axial dimensions of fuel and rod

direction_min and direction_max correspond to the physical locations of the top and bottom layers of fuel and cladding, respectively, considering the rod layers that can be into mechanical contact. direction_min and direction_max do not refer to the absolute minimum and maximum of the blocks. On the contrary, the fuel pin geometry that reads from the mesh in layered simulations will assume that the minimum value for the fuel area would be: direction_min - 0.5 * slice_height.

Example Input Syntax

User object input for secondary side (fuel)

[UserObjects<<<{"href": "../../syntax/UserObjects/index.html"}>>>]
  [1DContactStressOOP_fuel]
    type = Layered1DContactInterfaceStress<<<{"description": "Retrieves the out of plane stress and the coordinate transformation value at a particular boundary. These computations aid in the approximation of the action of friction on a contact interface.", "href": "Layered1DContactInterfaceStress.html"}>>>
    direction<<<{"description": "The direction of the layers."}>>> = y
    stress_name<<<{"description": "Name of the stress tensor used for retrieving the out of plane stress value for a layered problem."}>>> = stress
    num_layers<<<{"description": "The number of layers."}>>> = 10
    # If we do not provide the numbers below, it will look at the mesh, in all blocks to set the layer number. Then, it will
    # be wrong because the cladding has more height and won't be able to identify layers in the fuel.
    direction_min<<<{"description": "Minimum coordinate along 'direction' that bounds the layers"}>>> = 0.00917
    direction_max<<<{"description": "Maximum coordinate along 'direction' that bounds the layers"}>>> = 0.11591

    block<<<{"description": "The list of blocks (ids or names) that this object will be applied"}>>> = fuel
    execute_on<<<{"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."}>>> = 'LINEAR NONLINEAR'
  []
[]
(examples/1.5D_rodlet_10pellets/1_5D_friction.i)

User object input for primary side (cladding)

[UserObjects<<<{"href": "../../syntax/UserObjects/index.html"}>>>]
  [1DContactStressOOP_cladding]
    type = Layered1DContactInterfaceStress<<<{"description": "Retrieves the out of plane stress and the coordinate transformation value at a particular boundary. These computations aid in the approximation of the action of friction on a contact interface.", "href": "Layered1DContactInterfaceStress.html"}>>>
    direction<<<{"description": "The direction of the layers."}>>> = y
    stress_name<<<{"description": "Name of the stress tensor used for retrieving the out of plane stress value for a layered problem."}>>> = stress
    num_layers<<<{"description": "The number of layers."}>>> = 10
    # If we do not provide the numbers below, it will look at the mesh, in all blocks to set the layer number. Then, it will
    # be wrong because the cladding has more height and won't be able to identify layers in the fuel.
    direction_min<<<{"description": "Minimum coordinate along 'direction' that bounds the layers"}>>> = 0.00917
    direction_max<<<{"description": "Maximum coordinate along 'direction' that bounds the layers"}>>> = 0.11591

    block<<<{"description": "The list of blocks (ids or names) that this object will be applied"}>>> = clad
    execute_on<<<{"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."}>>> = 'LINEAR NONLINEAR'
  []
[]
(examples/1.5D_rodlet_10pellets/1_5D_friction.i)

Input Parameters

  • directionThe direction of the layers.

    C++ Type:MooseEnum

    Options:x, y, z

    Controllable:No

    Description:The direction of the layers.

  • num_layersThe number of layers.

    C++ Type:unsigned int

    Controllable:No

    Description:The number of layers.

  • stress_nameName of the stress tensor used for retrieving the out of plane stress value for a layered problem.

    C++ Type:std::string

    Controllable:No

    Description:Name of the stress tensor used for retrieving the out of plane stress value for a layered problem.

Required Parameters

  • base_nameMaterial properties base name

    C++ Type:std::string

    Controllable:No

    Description:Material properties base name

  • 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

  • boundsThe 'bounding' positions of the layers i.e.: '0, 1.2, 3.7, 4.2' will mean 3 layers between those positions.

    C++ Type:std::vector<double>

    Unit:(no unit assumed)

    Controllable:No

    Description:The 'bounding' positions of the layers i.e.: '0, 1.2, 3.7, 4.2' will mean 3 layers between those positions.

  • direction_maxMaximum coordinate along 'direction' that bounds the layers

    C++ Type:double

    Unit:(no unit assumed)

    Controllable:No

    Description:Maximum coordinate along 'direction' that bounds the layers

  • direction_minMinimum coordinate along 'direction' that bounds the layers

    C++ Type:double

    Unit:(no unit assumed)

    Controllable:No

    Description:Minimum coordinate along 'direction' that bounds the layers

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).

  • execute_onTIMESTEP_BEGIN LINEAR NONLINEARThe 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:TIMESTEP_BEGIN LINEAR NONLINEAR

    C++ Type:ExecFlagEnum

    Options:XFEM_MARK, NONE, INITIAL, LINEAR, NONLINEAR_CONVERGENCE, NONLINEAR, POSTCHECK, TIMESTEP_END, TIMESTEP_BEGIN, MULTIAPP_FIXED_POINT_END, MULTIAPP_FIXED_POINT_BEGIN, FINAL, CUSTOM

    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.

  • execution_order_group0Execution order groups are executed in increasing order (e.g., the lowest number is executed first). Note that negative group numbers may be used to execute groups before the default (0) group. Please refer to the user object documentation for ordering of user object execution within a group.

    Default:0

    C++ Type:int

    Controllable:No

    Description:Execution order groups are executed in increasing order (e.g., the lowest number is executed first). Note that negative group numbers may be used to execute groups before the default (0) group. Please refer to the user object documentation for ordering of user object execution within a group.

  • 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

Execution Scheduling 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

  • 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

  • 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.

Advanced 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.

Material Property Retrieval Parameters

Input Files