ADInterfaceJouleHeatingConstraint

Joule heating model, for the case of a closed gap interface, to calculate the heat flux contribution created when an electric potential difference occurs across that interface.

Description

The ADInterfaceJouleHeatingConstraint class is intended to calculate and add the heat source due to Joule Heating which results from the electric potential drop across an interface. The heat source is then added to the temperature field variable in a coupled electro-thermal simulation. This class is intended to be used in conjunction with ModularGapConductanceConstraint and GapFluxModelPressureDependentConduction, which enforce the closed gap interface requirement by checking for a positive normal pressure. As such, the ADInterfaceJouleHeatingConstraint takes as a required argument the name of the Lagrange Multiplier variable used in the electrical contact.

commentnote:Employ Consistency in Primary and Secondary Designations

Consistency in the selection of the primary boundary and secondary boundary among the electrical, thermal, and interface Joule Heating mortar contact input file components is recommended.

The heat source is calculated as a function of the electric potential change across the interface, as determined from the associated Lagrange multiplier , (1) where is the harmonic mean of the electrical conductivity of the primary and secondary blocks, (2) following (Cincotti et al., 2007). The Lagrange multiplier variable, passed from a separate mortar contact calculation, is calculated as (3) where the harmonic mean of the electrical conductivity is the same as given in Eq. (2). In base SI units this Lagrange multiplier variable has the units and is similar to the common approximation for the current density (4) where is the current density, is the electrical conductivity, and is the electric field.

commentnote:Closed Gap Interface Assumed by this Class

The ADInterfaceJouleHeatingConstraint class should only be employed in simulations when the user is certain that the current-density-like electric potential contact Lagrange multiplier variable is nonzero only when the interface gap is closed. The ADInterfaceJouleHeatingConstraint class may also be used in simulations with an open gap at the interface, so long as the electric potential contact Lagrange multiplier variable across that gap is zero while the interface gap is open.

With the total interface Joule heating source determined, the fraction of the heat source applied to each block at the interface is determined as (5) and (6) where is the user-defined weighting factor that governs how the heat source is divided between the two sides of the interface. The use of the negative sign in Eq. (5) and Eq. (6) indicates that the heat source is transferred into each block instead of away from the block.

Steady-State Analytical Verification

Under steady state analysis assumptions, the temperature at the interface in the primary boundary material block is given by Fourier's Law where is the length of the block, is the thermal conductivity, and is the prescribed temperature boundary condition at the edge of the material block.

Similarly, the interface temperature in the secondary block material is given as

In cases where the heat source weighting factor, Eq. (5) and Eq. (6), is set to 0.5, the temperature at the interface in each block will depend on the thermal conductivity value and size of each block.

Example Input File Syntax

[Constraints]
  [interface_heating]
    type = ADInterfaceJouleHeatingConstraint
    potential_lagrange_multiplier = potential_interface_lm
    secondary_variable = temperature
    primary_electrical_conductivity = aluminum_electrical_conductivity
    secondary_electrical_conductivity = aluminum_electrical_conductivity
    primary_boundary = moving_block_right
    primary_subdomain = interface_primary_subdomain
    secondary_boundary = fixed_block_left
    secondary_subdomain = interface_secondary_subdomain
  []
[]
(moose/modules/heat_transfer/test/tests/interface_heating_mortar/constraint_joule_heating_single_material.i)

ADInterfaceJouleHeatingConstraint should be used in conjunction with the modular gap conductance constraint, shown here,

[Constraints]
  [electrical_contact]
    type = ModularGapConductanceConstraint
    variable = potential_interface_lm
    secondary_variable = potential
    primary_boundary = moving_block_right
    primary_subdomain = interface_primary_subdomain
    secondary_boundary = fixed_block_left
    secondary_subdomain = interface_secondary_subdomain
    gap_flux_models = 'closed_electric'
  []
[]
(moose/modules/heat_transfer/test/tests/interface_heating_mortar/constraint_joule_heating_single_material.i)

and the pressure-dependent gap flux conduction user object, as shown below:

[UserObjects]
  [closed_electric]
    type = GapFluxModelPressureDependentConduction
    primary_conductivity = aluminum_electrical_conductivity
    secondary_conductivity = aluminum_electrical_conductivity
    temperature = potential
    contact_pressure = interface_normal_lm
    primary_hardness = aluminum_hardness
    secondary_hardness = aluminum_hardness
    boundary = moving_block_right
  []
[]
(moose/modules/heat_transfer/test/tests/interface_heating_mortar/constraint_joule_heating_single_material.i)

Input Parameters

  • potential_lagrange_multiplierThe name of the lagrange multiplier variable used in the calculation of the electrical potential mortar constrain calculation

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

    Unit:(no unit assumed)

    Controllable:No

    Description:The name of the lagrange multiplier variable used in the calculation of the electrical potential mortar constrain calculation

  • primary_boundaryThe name of the primary boundary sideset.

    C++ Type:BoundaryName

    Unit:(no unit assumed)

    Controllable:No

    Description:The name of the primary boundary sideset.

  • primary_electrical_conductivityThe electrical conductivity of the primary surface solid material

    C++ Type:MaterialPropertyName

    Unit:(no unit assumed)

    Controllable:No

    Description:The electrical conductivity of the primary surface solid material

  • primary_subdomainThe name of the primary subdomain.

    C++ Type:SubdomainName

    Unit:(no unit assumed)

    Controllable:No

    Description:The name of the primary subdomain.

  • secondary_boundaryThe name of the secondary boundary sideset.

    C++ Type:BoundaryName

    Unit:(no unit assumed)

    Controllable:No

    Description:The name of the secondary boundary sideset.

  • secondary_electrical_conductivityThe electrical conductivity of the secondary surface solid material

    C++ Type:MaterialPropertyName

    Unit:(no unit assumed)

    Controllable:No

    Description:The electrical conductivity of the secondary surface solid material

  • secondary_subdomainThe name of the secondary subdomain.

    C++ Type:SubdomainName

    Unit:(no unit assumed)

    Controllable:No

    Description:The name of the secondary subdomain.

Required Parameters

  • aux_lmAuxiliary Lagrange multiplier variable that is utilized together with the Petrov-Galerkin approach.

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

    Unit:(no unit assumed)

    Controllable:No

    Description:Auxiliary Lagrange multiplier variable that is utilized together with the Petrov-Galerkin approach.

  • compute_lm_residualsTrueWhether to compute Lagrange Multiplier residuals

    Default:True

    C++ Type:bool

    Unit:(no unit assumed)

    Controllable:No

    Description:Whether to compute Lagrange Multiplier residuals

  • compute_primal_residualsTrueWhether to compute residuals for the primal variable.

    Default:True

    C++ Type:bool

    Unit:(no unit assumed)

    Controllable:No

    Description:Whether to compute residuals for the primal variable.

  • correct_edge_droppingFalseWhether to enable correct edge dropping treatment for mortar constraints. When disabled any Lagrange Multiplier degree of freedom on a secondary element without full primary contributions will be set (strongly) to 0.

    Default:False

    C++ Type:bool

    Unit:(no unit assumed)

    Controllable:No

    Description:Whether to enable correct edge dropping treatment for mortar constraints. When disabled any Lagrange Multiplier degree of freedom on a secondary element without full primary contributions will be set (strongly) to 0.

  • debug_meshFalseWhether this constraint is going to enable mortar segment mesh debug information. An exodusfile will be generated if the user sets this flag to true

    Default:False

    C++ Type:bool

    Unit:(no unit assumed)

    Controllable:No

    Description:Whether this constraint is going to enable mortar segment mesh debug information. An exodusfile will be generated if the user sets this flag to true

  • ghost_higher_d_neighborsFalseWhether we should ghost higher-dimensional neighbors. This is necessary when we are doing second order mortar with finite volume primal variables, because in order for the method to be second order we must use cell gradients, which couples in the neighbor cells.

    Default:False

    C++ Type:bool

    Unit:(no unit assumed)

    Controllable:No

    Description:Whether we should ghost higher-dimensional neighbors. This is necessary when we are doing second order mortar with finite volume primal variables, because in order for the method to be second order we must use cell gradients, which couples in the neighbor cells.

  • ghost_point_neighborsFalseWhether we should ghost point neighbors of secondary face elements, and consequently also their mortar interface couples.

    Default:False

    C++ Type:bool

    Unit:(no unit assumed)

    Controllable:No

    Description:Whether we should ghost point neighbors of secondary face elements, and consequently also their mortar interface couples.

  • interpolate_normalsTrueWhether to interpolate the nodal normals (e.g. classic idea of evaluating field at quadrature points). If this is set to false, then non-interpolated nodal normals will be used, and then the _normals member should be indexed with _i instead of _qp

    Default:True

    C++ Type:bool

    Unit:(no unit assumed)

    Controllable:No

    Description:Whether to interpolate the nodal normals (e.g. classic idea of evaluating field at quadrature points). If this is set to false, then non-interpolated nodal normals will be used, and then the _normals member should be indexed with _i instead of _qp

  • minimum_projection_angle40Parameter to control which angle (in degrees) is admissible for the creation of mortar segments. If set to a value close to zero, very oblique projections are allowed, which can result in mortar segments solving physics not meaningfully, and overprojection of primary nodes onto the mortar segment mesh in extreme cases. This parameter is mostly intended for mortar mesh debugging purposes in two dimensions.

    Default:40

    C++ Type:double

    Unit:(no unit assumed)

    Controllable:No

    Description:Parameter to control which angle (in degrees) is admissible for the creation of mortar segments. If set to a value close to zero, very oblique projections are allowed, which can result in mortar segments solving physics not meaningfully, and overprojection of primary nodes onto the mortar segment mesh in extreme cases. This parameter is mostly intended for mortar mesh debugging purposes in two dimensions.

  • periodicFalseWhether this constraint is going to be used to enforce a periodic condition. This has the effect of changing the normals vector for projection from outward to inward facing

    Default:False

    C++ Type:bool

    Unit:(no unit assumed)

    Controllable:No

    Description:Whether this constraint is going to be used to enforce a periodic condition. This has the effect of changing the normals vector for projection from outward to inward facing

  • primary_variablePrimal variable on primary surface. If this parameter is not provided then the primary variable will be initialized to the secondary variable

    C++ Type:VariableName

    Unit:(no unit assumed)

    Controllable:No

    Description:Primal variable on primary surface. If this parameter is not provided then the primary variable will be initialized to the secondary variable

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

  • quadratureDEFAULTQuadrature rule to use on mortar segments. For 2D mortar DEFAULT is recommended. For 3D mortar, QUAD meshes are integrated using triangle mortar segments. While DEFAULT quadrature order is typically sufficiently accurate, exact integration of QUAD mortar faces requires SECOND order quadrature for FIRST variables and FOURTH order quadrature for SECOND order variables.

    Default:DEFAULT

    C++ Type:MooseEnum

    Unit:(no unit assumed)

    Options:DEFAULT, FIRST, SECOND, THIRD, FOURTH

    Controllable:No

    Description:Quadrature rule to use on mortar segments. For 2D mortar DEFAULT is recommended. For 3D mortar, QUAD meshes are integrated using triangle mortar segments. While DEFAULT quadrature order is typically sufficiently accurate, exact integration of QUAD mortar faces requires SECOND order quadrature for FIRST variables and FOURTH order quadrature for SECOND order variables.

  • secondary_variablePrimal variable on secondary surface.

    C++ Type:VariableName

    Unit:(no unit assumed)

    Controllable:No

    Description:Primal variable on secondary surface.

  • 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

    Unit:(no unit assumed)

    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.

  • use_petrov_galerkinFalseWhether to use the Petrov-Galerkin approach for the mortar-based constraints. If set to true, we use the standard basis as the test function and dual basis as the shape function for the interpolation of the Lagrange multiplier variable.

    Default:False

    C++ Type:bool

    Unit:(no unit assumed)

    Controllable:No

    Description:Whether to use the Petrov-Galerkin approach for the mortar-based constraints. If set to true, we use the standard basis as the test function and dual basis as the shape function for the interpolation of the Lagrange multiplier variable.

  • variableThe name of the lagrange multiplier variable that this constraint is applied to. This parameter may not be supplied in the case of using penalty methods for example

    C++ Type:NonlinearVariableName

    Unit:(no unit assumed)

    Controllable:No

    Description:The name of the lagrange multiplier variable that this constraint is applied to. This parameter may not be supplied in the case of using penalty methods for example

  • weighting_factor0.5Weight applied to divide the heat flux from Joule heating at the interface between the primary and secondary surfaces.

    Default:0.5

    C++ Type:double

    Unit:(no unit assumed)

    Controllable:No

    Description:Weight applied to divide the heat flux from Joule heating at the interface between the primary and secondary surfaces.

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>

    Unit:(no unit assumed)

    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>

    Unit:(no unit assumed)

    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>

    Unit:(no unit assumed)

    Controllable:No

    Description:The extra tags for the vectors this Kernel should fill

  • matrix_tagssystemThe tag for the matrices this Kernel should fill

    Default:system

    C++ Type:MultiMooseEnum

    Unit:(no unit assumed)

    Options:nontime, system

    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

    Unit:(no unit assumed)

    Options:nontime, time

    Controllable:No

    Description:The tag for the vectors this Kernel should fill

Tagging Parameters

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

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

    Unit:(no unit assumed)

    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

    Unit:(no unit assumed)

    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

    Unit:(no unit assumed)

    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

    Unit:(no unit assumed)

    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

    Unit:(no unit assumed)

    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

References

  1. Alberto Cincotti, Antonio Mario Locci, Roberto Orru, and Giacomo Cao. Modeling of sps apparatus: temperature, current and strain distribution with no powders. AIChE journal, 53(3):703–719, 2007.[BibTeX]