MFEMConvectiveHeatFluxBC

Summary

Convective heat transfer boundary condition with temperature and heat transfer coefficent given by material properties to add to MFEM problems.

Overview

Adds the boundary integrator for integrating the bilinear form

where are the test and trial variables, and are scalar coefficients on the boundary independent of .

This boundary condition is particularly useful for thermal problems, where it can be used to represent a heat transfer boundary condition

by identifying as the heat transfer coefficient on the boundary, as the trial variable for the temperature, as the test variable, and as the equilibrium temperature far from the boundary.

Example Input File Syntax

[BCs]
  [bottom]
    type = MFEMScalarDirichletBC
    variable = temperature
    boundary = '1'
    value = 1.0
  []
  [top]
    type = MFEMConvectiveHeatFluxBC
    variable = temperature
    boundary = '2'
    T_infinity = reservoir_far_temperature
    heat_transfer_coefficient = heat_transfer_coefficient
  []
[]
(test/tests/kernels/heattransfer.i)

Input Parameters

  • T_infinityName of a coefficient specifying the far-field temperature. A coefficient can be any of the following: a variable, an MFEM material property, a function, or a post-processor. A functor is any of the following: a variable, a functor material property, a function, a post-processor, or a number.

    C++ Type:MooseFunctorName

    Unit:(no unit assumed)

    Controllable:No

    Description:Name of a coefficient specifying the far-field temperature. A coefficient can be any of the following: a variable, an MFEM material property, a function, or a post-processor. A functor is any of the following: a variable, a functor material property, a function, a post-processor, or a number.

  • heat_transfer_coefficientName of the coefficient specifying the heat transfer coefficient. A coefficient can be any of the following: a variable, an MFEM material property, a function, or a post-processor. A functor is any of the following: a variable, a functor material property, a function, a post-processor, or a number.

    C++ Type:MooseFunctorName

    Unit:(no unit assumed)

    Controllable:No

    Description:Name of the coefficient specifying the heat transfer coefficient. A coefficient can be any of the following: a variable, an MFEM material property, a function, or a post-processor. A functor is any of the following: a variable, a functor material property, a function, a post-processor, or a number.

Required Parameters

  • boundary-1 The list of boundaries (ids) from the mesh where this boundary condition applies. Defaults to applying BC on all boundaries.

    Default:-1

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

    Controllable:No

    Description:The list of boundaries (ids) from the mesh where this boundary condition applies. Defaults to applying BC on all boundaries.

  • variableVariable on which to apply the boundary condition

    C++ Type:std::string

    Controllable:No

    Description:Variable on which to apply the boundary condition

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_ENDThe 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_END

    C++ Type:ExecFlagEnum

    Options: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.

  • 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