- boundaryThe list of boundary IDs from the mesh where this object applies
C++ Type:std::vector<BoundaryName>
Controllable:No
Description:The list of boundary IDs from the mesh where this object applies
- conductanceThermal conductance across the interface. This is equivalent to k / thickness or 1 / thermal_resistance. The conductance functor is evaluated on the variable1/subdomain1 side of the interface. A functor is any of the following: a variable, a functor material property, a function, a postprocessor or a number.
C++ Type:MooseFunctorName
Unit:(no unit assumed)
Controllable:No
Description:Thermal conductance across the interface. This is equivalent to k / thickness or 1 / thermal_resistance. The conductance functor is evaluated on the variable1/subdomain1 side of the interface. A functor is any of the following: a variable, a functor material property, a function, a postprocessor or a number.
- subdomain1The subdomains on the 1st side of the boundary.
C++ Type:std::vector<SubdomainName>
Controllable:No
Description:The subdomains on the 1st side of the boundary.
- subdomain2The subdomains on the 2nd side of the boundary.
C++ Type:std::vector<SubdomainName>
Controllable:No
Description:The subdomains on the 2nd side of the boundary.
- variable1The name of the first variable that this interface kernel applies to
C++ Type:NonlinearVariableName
Unit:(no unit assumed)
Controllable:No
Description:The name of the first variable that this interface kernel applies to
FVSideSetHeatTransferKernel
Models heat transfer across an internal sideset for the finite volume method using an interface conductance.
Description
FVSideSetHeatTransferKernel models heat transfer across an internal sideset for the finite volume method using an interface conductance. The interface heat flux is
where \(G\) is the interface conductance, \(T_1\) is the temperature on subdomain1, and \(T_2\) is the temperature on subdomain2.
The conductance functor is evaluated explicitly on the variable1 / subdomain1 side of the interface. It is not interpolated with a value from subdomain2, including when the same variable and conductance functor are defined on both subdomains.
This object is useful for representing thermal contact, gap conductance, or an unresolved thin layer between two finite volume thermal domains. For a thin layer of conductivity \(k\) and thickness \(\delta\), the equivalent interface conductance is
Equivalently, if a thermal resistance per unit area \(R_\mathrm{th}\) is known,
The kernel returns this interface flux density as the residual contribution to variable1 on subdomain1. The FVInterfaceKernel base class multiplies it by the face area and applies the opposite residual contribution to variable2 on subdomain2 when both variables belong to the same nonlinear system.
Example input syntax
[FVInterfaceKernels<<<{"href": "../../syntax/FVInterfaceKernels/index.html"}>>>]
[interface_heat_transfer]
type = FVSideSetHeatTransferKernel<<<{"description": "Models heat transfer across an internal sideset for the finite volume method using an interface conductance.", "href": "FVSideSetHeatTransferKernel.html"}>>>
boundary<<<{"description": "The list of boundary IDs from the mesh where this object applies"}>>> = interface
subdomain1<<<{"description": "The subdomains on the 1st side of the boundary."}>>> = 0
subdomain2<<<{"description": "The subdomains on the 2nd side of the boundary."}>>> = 1
variable1<<<{"description": "The name of the first variable that this interface kernel applies to"}>>> = T_left
variable2<<<{"description": "The name of the second variable that this interface kernel applies to. If not supplied, variable1 will be used."}>>> = T_right
conductance<<<{"description": "Thermal conductance across the interface. This is equivalent to k / thickness or 1 / thermal_resistance. The conductance functor is evaluated on the variable1/subdomain1 side of the interface. A functor is any of the following: a variable, a functor material property, a function, a postprocessor or a number."}>>> = interface_conductance
[]
[](modules/heat_transfer/test/tests/fviks/fv_sideset_heat_transfer/fv_sideset_heat_transfer.i)Input Parameters
- displacementsThe displacements
C++ Type:std::vector<VariableName>
Unit:(no unit assumed)
Controllable:No
Description:The displacements
- execute_onLINEARThe 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
C++ Type:ExecFlagEnum
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.
- variable2The name of the second variable that this interface kernel applies to. If not supplied, variable1 will be used.
C++ Type:NonlinearVariableName
Unit:(no unit assumed)
Controllable:No
Description:The name of the second variable that this interface kernel applies to. If not supplied, variable1 will be used.
Optional Parameters
- absolute_value_vector_tagsThe tags for the vectors this residual object should fill with the absolute value of the residual contribution
C++ Type:std::vector<TagName>
Controllable:No
Description:The tags for the vectors this residual object should fill with the absolute value of the residual contribution
- extra_matrix_tagsThe extra tags for the matrices this Kernel should fill
C++ Type:std::vector<TagName>
Controllable:No
Description:The extra tags for the matrices this Kernel should fill
- extra_vector_tagsThe extra tags for the vectors this Kernel should fill
C++ Type:std::vector<TagName>
Controllable:No
Description:The extra tags for the vectors this Kernel should fill
- matrix_onlyFalseWhether this object is only doing assembly to matrices (no vectors)
Default:False
C++ Type:bool
Controllable:No
Description:Whether this object is only doing assembly to matrices (no vectors)
- matrix_tagssystemThe tag for the matrices this Kernel should fill
Default:system
C++ Type:MultiMooseEnum
Controllable:No
Description:The tag for the matrices this Kernel should fill
- vector_tagsnontimeThe tag for the vectors this Kernel should fill
Default:nontime
C++ Type:MultiMooseEnum
Controllable:No
Description:The tag for the vectors this Kernel should fill
Contribution To Tagged Field Data 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).
- 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
- ghost_layers1The number of layers of elements to ghost.
Default:1
C++ Type:unsigned short
Controllable:No
Description:The number of layers of elements to ghost.
- use_point_neighborsFalseWhether to use point neighbors, which introduces additional ghosting to that used for simple face neighbors.
Default:False
C++ Type:bool
Controllable:No
Description:Whether to use point neighbors, which introduces additional ghosting to that used for simple face neighbors.
Parallel Ghosting 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.