Heat Transfer Requirements Traceability Matrix

This template follows INL template TEM-214, "IT System Requirements Traceability Matrix."

commentnote

This document serves as an addendum to Framework Requirements Traceability Matrix and captures information for RTM specific to the Heat Transfer module.

Introduction

Minimum System Requirements

In general, the following is required for MOOSE-based development:

A POSIX compliant Unix-like operating system. This includes any modern Linux-based operating system (e.g., Ubuntu, Fedora, Rocky, etc.), or a Macintosh machine running either of the last two MacOS releases.

HardwareInformation
CPU Architecturex86_64, ARM (Apple Silicon)
Memory8 GB (16 GBs for debug compilation)
Disk Space30GB

LibrariesVersion / Information
GCC8.5.0 - 12.2.1
LLVM/Clang10.0.1 - 16.0.6
Intel (ICC/ICX)Not supported at this time
Python3.7 - 3.11
Python Packagespackaging pyaml jinja2

System Purpose

The MOOSE Heat Transfer module purpose is to model heat transfer due to conduction and radiation.

System Scope

The Heat Transfer module models volumetric heat transfer mechanisms due to conduction and body sources/sinks. Additionally surface to surface conduction and radiation may also be modeled.

Assumptions and Dependencies

The Heat Transfer module is developed using MOOSE and can itself be based on various MOOSE modules, as such the RTM for the Heat Transfer module is dependent upon the files listed at the beginning of this document.

Pre-test Instructions/Environment/Setup

Ideally all testing should be performed on a clean test machine following one of the supported configurations setup by the test system engineer. Testing may be performed on local workstations and cluster systems containing supported operating systems.

The repository should be clean prior to building and testing. When using "git" this can be done by doing a force clean in the main repository and each one of the submodules:

git clean -xfd
git submodule foreach 'git clean -xfd'

All tests must pass in accordance with the type of test being performed. This list can be found in the Software Test Plan.

Changelog Issue Revisions

Errors in changelog references can sometimes occur as a result of typos or conversion errors. If any need to be noted by the development team, they will be noted here.

The changelog for all code residing in the MOOSE repository is located in the MOOSE RTM.

System Requirements Traceability

Functional Requirements

  • heat_transfer: Ad Convective Heat Flux
  • 4.2.1The system shall provide a convective flux boundary condition which uses material properties as heat transfer coefficients and far-field temperature values using AD
    1. and match hand calculations for flux through a boundary.
    2. and approach a constant far-field temperature value over time as heat flux decreases.
    3. and couple a temperature dependent far-field temperature and heat transfer coefficient.

    Specification(s): g/flux, g/equilibrium, g/coupled

    Design: ADConvectiveHeatFluxBC

    Issue(s): #11631

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • heat_transfer: Ad Heat Conduction
  • 4.3.1AD heat conduction and the Jacobian shall be beautiful

    Specification(s): jacobian_test

    Design: ADHeatConduction

    Issue(s): #5658#12633

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • heat_transfer: Code Verification
  • 4.4.1The MOOSE solutions shall converge to the analytic solutions with an expected order of accuracy (two for linear, three for quadratic) where a standard set of heat conduction problems is used for code verification.

    Specification(s): spatial_csv

    Design: HeatConduction

    Issue(s): #15301

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • heat_transfer: Conjugate Heat Transfer
  • 4.5.1The system shall correctly model convection heat transfer across internal sidesets aka conjugate heat transfer.

    Specification(s): convection

    Design: ConjugateHeatTransfer

    Issue(s): #15114

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • heat_transfer: Convective Flux Function
  • 4.6.1The system shall allow prescribing a convective flux boundary condition using a constant heat transfer coefficient.

    Specification(s): constant

    Design: ConvectiveFluxFunction

    Issue(s): #14418

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 4.6.2The system shall allow prescribing a convective flux boundary condition using a heat transfer coefficient that is a function of position and time.

    Specification(s): time_dependent

    Design: ConvectiveFluxFunction

    Issue(s): #14418

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 4.6.1

  • 4.6.3The system shall allow prescribing a convective flux boundary condition using a heat transfer coefficient that is a function of temperature.

    Specification(s): temperature_dependent

    Design: ConvectiveFluxFunction

    Issue(s): #14418

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 4.6.2

  • heat_transfer: Convective Heat Flux
  • 4.7.1The system shall provide a convective flux boundary condition which uses material properties as heat transfer coefficients and far-field temperature values
    1. and match hand calculations for flux through a boundary.
    2. and approach a constant far-field temperature value over time as heat flux decreases.
    3. and couple a temperature dependent far-field temperature and heat transfer coefficient.

    Specification(s): g/flux, g/equilibrium, g/coupled

    Design: ConvectiveHeatFluxBC

    Issue(s): #11631

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • heat_transfer: Function Ellipsoid Heat Source
  • 4.9.1The system shall produce a moving heat source where its path is function dependent

    Specification(s): test

    Design: FunctionPathEllipsoidHeatSource

    Issue(s): #15795

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • heat_transfer: Gap Heat Transfer Balance
  • 4.13.1Energy balance must be fulfilled for the heat transfer of concentric spheres involving radiation, when the gap distance is not negligible with respect to the body main dimensions.

    Specification(s): large_gap_heat_transfer_test_sphere

    Design: GapHeatTransfer

    Issue(s): #18585

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 4.13.2Energy balance must be fulfilled for the heat transfer of concentric cylinders involving radiation in two-dimensions, when the gap distance is not negligible with respect to the body main dimensions.

    Specification(s): large_gap_heat_transfer_test_rz_cylinder

    Design: GapHeatTransfer

    Issue(s): #18585

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 4.13.3Energy balance must be fulfilled for the heat transfer of concentric cylinders involving radiation in two-dimensions with axisymmetry, when the gap distance is not negligible with respect to the body main dimensions.

    Specification(s): large_gap_heat_transfer_test_cylinder

    Design: GapHeatTransfer

    Issue(s): #18585

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • heat_transfer: Gap Heat Transfer Htonly
  • 4.14.1The system shall compute thermal contact in 1D with axisymmetric coordinates.

    Specification(s): 1D

    Design: GapHeatTransfer

    Issue(s): #27216

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.14.2Thermal contact shall solve plate heat transfer for a constant conductivity gap in 3D

    Specification(s): 3D

    Design: GapHeatTransfer

    Issue(s): #1609

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.14.3Thermal contact shall solve plate heat transfer for a constant conductivity gap in 3D using the Modules/HeatConduction/Thermal contact syntax

    Specification(s): syntax

    Design: GapHeatTransfer

    Issue(s): #1609

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.14.4Thermal contact shall solve plate heat transfer for a constant conductivity gap in 3D at each iteration

    Specification(s): 3D_Iters

    Design: GapHeatTransfer

    Issue(s): #1609

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.14.5Thermal contact shall solve cylindrical and plate heat transfer for a constant conductivity gap in 2D axisymmetric coordinates

    Specification(s): RZ

    Design: GapHeatTransfer

    Issue(s): #5104

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.14.6Thermal contact shall solve cylindrical heat transfer for a constant conductivity gap in 2D axisymmetric coordinates where the axial axis is along the x-direction

    Specification(s): ZR

    Design: GapHeatTransfer

    Issue(s): #12071

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.14.7Thermal contact shall solve spherical heat transfer for a constant conductivity gap in 1D spherically symmetric coordinates

    Specification(s): RSpherical

    Design: GapHeatTransfer

    Issue(s): #1609#5104

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.14.8Thermal contact shall solve cylindrical heat transfer for a constant conductivity gap in 3D

    Specification(s): cyl3D

    Design: GapHeatTransfer

    Issue(s): #6161

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.14.9Thermal contact shall solve cylindrical heat transfer for a constant conductivity gap in the x-y plane

    Specification(s): cyl2D

    Design: GapHeatTransfer

    Issue(s): #6161

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.14.10Thermal contact shall solve spherical heat transfer for a constant conductivity gap in 3D

    Specification(s): sphere3D

    Design: GapHeatTransfer

    Issue(s): #6161

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.14.11Thermal contact shall solve spherical heat transfer for a constant conductivity gap in 2D axisymmetric coordinates

    Specification(s): sphere2DRZ

    Design: GapHeatTransfer

    Issue(s): #6161

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.14.12Thermal contact shall solve cylindrical heat transfer for a constant conductivity gap in the x-z plane

    Specification(s): cyl2D_xz

    Design: GapHeatTransfer

    Issue(s): #11913

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.14.13Thermal contact shall solve cylindrical heat transfer for a constant conductivity gap in the y-z plane

    Specification(s): cyl2D_yz

    Design: GapHeatTransfer

    Issue(s): #11913

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.14.14Thermal contact shall solve plate heat transfer for a constant conductivity gap in the x-y plane

    Specification(s): planar_xy

    Design: GapHeatTransfer

    Issue(s): #11913

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.14.15Thermal contact shall solve plate heat transfer for a constant conductivity gap in the x-z plane

    Specification(s): planar_xz

    Design: GapHeatTransfer

    Issue(s): #11913

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.14.16Thermal contact shall solve plate heat transfer for a constant conductivity gap in the y-z plane

    Specification(s): planar_yz

    Design: GapHeatTransfer

    Issue(s): #11913

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.14.17When the 'check_boundary_restricted' option is set to false, the thermal contact system shall solve problems in which multiple faces of an element are in one of the contact surfaces, but provide an information message that contact variables may have issues in those areas.

    Specification(s): corner_wrap

    Design: GapHeatTransfer

    Issue(s): #23058

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.14.18When the 'check_boundary_restricted' option is set to true, the AuxKernels set up by the ThermalContact system shall generate an error when multiple faces of an element are in one of the contact surfaces.

    Specification(s): corner_wrap_err_check_true

    Design: GapHeatTransfer

    Issue(s): #23058

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 4.14.17

  • 4.14.19If 'quadrature=false' the thermal contact system shall generate an error if the user also sets 'check_boundary_restricted=true'.

    Specification(s): corner_wrap_err_quadrature

    Design: GapHeatTransfer

    Issue(s): #23058

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 4.14.18

  • heat_transfer: Gap Heat Transfer Radiation
  • 4.17.1The system shall be able to compute radiative heat flux across a gap using the ThermalContact methods.

    Specification(s): test

    Design: GapHeatTransfer

    Issue(s): #1609

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.17.2The system shall be able to compute radiative heat flux across a cylindrical gap using the ThermalContact methods.

    Specification(s): cylinder

    Design: GapHeatTransfer

    Issue(s): #26627

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 4.17.3The system shall be able to compute radiative heat flux across a spherical gap using the ThermalContact methods.

    Specification(s): sphere

    Design: GapHeatTransfer

    Issue(s): #26627

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • heat_transfer: Gap Perfect Transfer
  • 4.18.1The system shall support nearly perfect gap conductance (no change in temperature across the gap) through
    1. the use of a penalty parameter, and
    2. error if the penalty is set for other heat transfer types.

    Specification(s): perfect_conductance/test, perfect_conductance/error_check

    Design: GapPerfectConductance

    Issue(s): #28963

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunExceptionCSVDiff

  • heat_transfer: Heat Conduction
  • 4.21.1The system shall compute the heat transfer across small gaps for supported FEM orders and quadratures (QUAD4).

    Specification(s): perfect

    Design: GapConductance

    Issue(s): #6750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.21.2The system shall compute the heat transfer across small gaps for supported FEM orders and quadratures (QUAD8)

    Specification(s): perfectQ8

    Design: GapConductance

    Issue(s): #6750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.21.3The system shall compute the heat transfer across small gaps for supported FEM orders and quadratures (QUAD9)

    Specification(s): perfectQ9

    Design: GapConductance

    Issue(s): #6750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.21.4The system shall compute the heat transfer across small gaps for non-matching meshes.

    Specification(s): nonmatching

    Design: ThermalContactAction

    Issue(s): #6750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.21.5The system shall compute the heat transfer across small gaps for second order FEM bases.

    Specification(s): second_order

    Design: ThermalContactAction

    Issue(s): #6750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.21.6The system shall compute the heat transfer across small gaps for moving interfaces.

    Specification(s): moving

    Design: ThermalContactAction

    Issue(s): #6750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.21.7The system shall compute the heat transfer across small gaps with a specified gap conductivity.

    Specification(s): gap_conductivity_property

    Design: ThermalContactAction

    Issue(s): #6750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.21.8The system shall throw an error if the gap conductance model is used with uniform mesh refinement

    Specification(s): gap_conductivity_property_r1_error

    Design: ThermalContactAction

    Issue(s): #13043

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 4.21.9The system shall generate a parallel mesh split across 2 processes.

    Specification(s): perfect_prereq

    Design: Mesh Splitting

    Issue(s): #27203

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

    Prerequisite(s): 4.21.1

  • 4.21.10The system shall read in parallel a mesh split across 2 processes.

    Specification(s): perfect_split_mesh

    Design: Mesh Splitting

    Issue(s): #27203

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 4.21.9

  • 4.21.11The system shall support thermal contact with linear 3d hexahedral elements

    Specification(s): nonmatching

    Design: ThermalContactAction

    Issue(s): #6750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.21.12The system shall support thermal contact with second-order 3d hexahedral elements

    Specification(s): second

    Design: ThermalContactAction

    Issue(s): #6750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.21.13The system shall support thermal contact with 3d hexahedral elements where the surfaces move relative to one another

    Specification(s): moving

    Design: ThermalContactAction

    Issue(s): #6750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.21.14The system shall provide convective heat flux boundary condition where far-field temperature and convective heat transfer coefficient are given as constant variables

    Specification(s): const_hw

    Design: CoupledConvectiveHeatFluxBC

    Issue(s): #11631

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.21.15The system shall provide convective heat flux boundary condition where far-field temperature and convective heat transfer coefficient are given as spatially varying variables

    Specification(s): coupled_convective_heat_flux

    Design: CoupledConvectiveHeatFluxBC

    Issue(s): #11631

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.21.16The system shall provide convective heat flux boundary condition for multi-phase fluids where far-field temperatures and convective heat transfer coefficients are given as spatially varying variables

    Specification(s): coupled_convective_heat_flux_two_phase

    Design: CoupledConvectiveHeatFluxBC

    Issue(s): #11631

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.21.17The system shall report an error if the number of alpha components does not match the number of T_infinity components.

    Specification(s): not_enough_alpha

    Design: CoupledConvectiveHeatFluxBC

    Issue(s): #11631

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 4.21.18The system shall report an error if the number of htc components does not match the number of T_infinity components.

    Specification(s): not_enough_htc

    Design: CoupledConvectiveHeatFluxBC

    Issue(s): #11631

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 4.21.19The system shall enable scaling of the total heat flux of the convective heat flux boundary condition

    Specification(s): on_off

    Design: CoupledConvectiveHeatFluxBC

    Issue(s): #15421

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.21.20Optionally a constant attenuation shall be applied to compute the gap conductance below a gap length threshold.

    Specification(s): min_gap_order_zero

    Design: GapConductanceGapHeatTransfer

    Issue(s): #13221

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 4.21.21Optionally a linear Taylor expansion of the inverse gap length shall be applied as the attenuation to compute the gap conductance below a gap length threshold.

    Specification(s): min_gap_order_one

    Design: GapConductanceGapHeatTransfer

    Issue(s): #13221

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • heat_transfer: Heat Conduction Ortho
  • 4.22.1The system shall allow the use of an anisotropic heat conduction material set by postprocessors.

    Specification(s): test

    Design: AnisoHeatConductionMaterial

    Issue(s): #2674

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • heat_transfer: Heat Conduction Patch
  • 4.23.1The system shall compute a tri-linear temperature field

    Specification(s): test

    Design: HeatConduction

    Issue(s): #6750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.23.2The system shall compute a bi-linear temperature field for an axisymmetric problem with quad8 elements

    Specification(s): test_rz_quad8

    Design: HeatConduction

    Issue(s): #6750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.23.3The system shall compute a bi-linear temperature field for an axisymmetric problem

    Specification(s): test_rz

    Design: HeatConduction

    Issue(s): #6750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.23.4The system shall compute a tri-linear temperature field with hex20 elements

    Specification(s): test_hex20

    Design: HeatConduction

    Issue(s): #6750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.23.5The system shall compute a tri-linear temperature field with hex20 elements using an anisotropic thermal conductivity model with isotropic thermal conductivities supplied

    Specification(s): test_hex20_aniso

    Design: HeatConduction

    Issue(s): #6750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 4.23.4

  • heat_transfer: Heat Source Bar
  • 4.24.1The system shall reproduce an analytical solution of a heat source in a 1D ceramic bar.

    Specification(s): heat_source_bar

    Design: HeatSource

    Issue(s): #2582

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.24.2The system shall reproduce an analytical solution of a heat source in a 1D ceramic bar using AD kernels.

    Specification(s): ad_heat_source_bar

    Design: ADMatHeatSource

    Issue(s): #12633

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.24.3The system shall produce correct Jacobians for the AD heat conduction and heat source kernel objects.

    Specification(s): ad_heat_source_bar_jacobian

    Design: ADMatHeatSource

    Issue(s): #5658#12633

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

    Prerequisite(s): 4.24.2

  • heat_transfer: Homogenization
  • 4.25.1The system shall compute homogenized thermal conductivity using the asymptotic expansion homogenization approach

    Specification(s): heatConduction_test

    Design: HomogenizedHeatConduction

    Issue(s): #6750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.25.2The system shall compute homogenized thermal conductivity using the asymptotic expansion homogenization approach for hexagonal geometries.

    Specification(s): homogenize_tc_hexagonal

    Design: HomogenizedThermalConductivity

    Issue(s): #22919

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 4.25.3The system shall compute homogenized thermal conductivity using the asymptotic expansion homogenization approach when the heterogeneous thermal conductivities are given as tensor

    Specification(s): homogenize_tensor_tc

    Design: AnisoHomogenizedHeatConduction

    Issue(s): #22919

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.25.4The system shall compute homogenized thermal conductivity using the asymptotic expansion homogenization approach when the heterogeneous thermal conductivities are given as anisotropic tensor

    Specification(s): homogenize_aniso_tensor_tc

    Design: AnisoHomogenizedHeatConduction

    Issue(s): #22919

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • heat_transfer: Laser Bc Flux
  • 4.28.1The system shall be able to model an equilibrium between an incoming heat flux from a focused beam (e.g. laser), which is described by a Gaussian shape, and outgoing heat flux due to radiative losses.

    Specification(s): test

    Design: FunctionRadiativeBCGaussianEnergyFluxBC

    Issue(s): #24462

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • heat_transfer: Meshed Gap Thermal Contact
  • 4.29.1The ThermalContact system shall enforce heat transfer across a meshed gap in a 2D plane geometry.

    Specification(s): test

    Design: Thermal ContactGapHeatTransfer

    Issue(s): #716

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.29.2The ThermalContact system shall correctly enforce heat transfer across a meshed gap in a 2D plane geometry using a prescribed constant conductance.

    Specification(s): constant_conductance

    Design: Thermal ContactGapConductanceConstant

    Issue(s): #13061

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.29.3The ThermalContact system shall correctly enforce heat transfer across a meshed gap in a 2D plane geometry using a prescribed constant conductance with the quadrature option

    Specification(s): constant_conductance_quadrature

    Design: Thermal ContactGapConductanceConstant

    Issue(s): #13061

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 4.29.2

  • 4.29.4The ThermalContact system shall enforce heat transfer across a meshed circular annulus in a 2D plane geometry.

    Specification(s): annulus

    Design: Thermal ContactGapHeatTransfer

    Issue(s): #716

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • heat_transfer: Multiple Contact Pairs
  • 4.30.1Heat transfer module action shall allow for providing multiple contact pairs.

    Specification(s): multiple_contact_pairs

    Design: ThermalContactAction

    Issue(s): #18022

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • heat_transfer: Parallel Element Pps Test
  • 4.32.1The system shall computed an integrated value on elements in parallel

    Specification(s): test

    Design: ElementIntegralVariablePostprocessor

    Issue(s): #861

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • heat_transfer: Physics
  • 4.33.1The system shall be able to restart the temperature variable in the shorthand Physics-syntax
    1. using the default initial condition,
    2. with a user-defined initial condition,
    3. when performing a regular checkpoint restart, but still obeying the user-defined initial condition,
    4. when performing manual restart from a mesh file, ignoring the default initial condition.

    Specification(s): restart/default, restart/user_ics, restart/restart_with_user_ics, restart/restart_from_file

    Design: HeatConductionFVHeatConductionCG

    Issue(s): #28730

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 4.33.2The system shall error if the user specifies initial conditions while also requesting variables be loaded from a mesh file.

    Specification(s): error

    Design: HeatConductionFVHeatConductionCG

    Issue(s): #28730

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 4.33.3The system shall be able to define the heat conduction equation including its boundary conditions using a shorthand syntax,
    1. with Dirichlet and Neumann boundary conditions and a heat source defined using a variable,
    2. with a heat source defined using a functor,
    3. with convective heat flux boundary conditions.

    Specification(s): cg/base, cg/functor_heat, cg/convective_bc

    Design: HeatConductionCG

    Issue(s): #25642#28779

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.33.4The system shall be able to define the heat conduction equation including its boundary conditions using a shorthand syntax and a finite volume discretization
    1. with Dirichlet and Neumann boundary conditions and a heat source defined using a variable,
    2. with a heat source defined using a functor,
    3. with convective heat flux boundary conditions.

    Specification(s): fv/base, fv/functor_heat, fv/convective_bc

    Design: HeatConductionFV

    Issue(s): #25642#28779

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • heat_transfer: Radiation Transfer Symmetry
  • 4.36.1The system shall support the modeling of radiative heat transfer with symmetry boundary conditions by
    1. unfolding the problem at the symmetry boundary and
    2. by using a symmetry boundary condition.

    Specification(s): test/unfolded, test/symmetry_bc

    Design: RayTracingViewFactor

    Issue(s): #16954

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • heat_transfer: Radiative Bcs
  • 4.37.1The system shall be able to model radiative transfer from a cylindrical surface as a boundary condition.

    Specification(s): radiative_bc_cyl

    Design: InfiniteCylinderRadiativeBC

    Issue(s): #13053

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 4.37.2The system shall be able to model radiative transfer from a cylindrical surface as boundary condition with automated differentiation.

    Specification(s): ad_radiative_bc_cyl

    Design: ADInfiniteCylinderRadiativeBC

    Issue(s): #13053

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 4.37.3The system shall be able to model radiative transfer from a cylindrical surface as boundary condition with automated differentiation and provide exact Jacobian.

    Specification(s): ad_radiative_bc_cyl_jacobian

    Design: ADInfiniteCylinderRadiativeBC

    Issue(s): #13053

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 4.37.4The system shall be able to model radiative heat transfer using a user-specified emissivity function.

    Specification(s): function_radiative_bc

    Design: FunctionRadiativeBC

    Issue(s): #13053

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.37.5The system shall be able to model radiative heat transfer using a user-specified emissivity function with automated differentiation.

    Specification(s): ad_function_radiative_bc

    Design: ADFunctionRadiativeBC

    Issue(s): #13053

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.37.6The system shall be able to model radiative heat transfer using a user-specified emissivity function with automated differentiation and provide exact Jacobian.

    Specification(s): ad_function_radiative_bc_jacobian

    Design: ADFunctionRadiativeBC

    Issue(s): #13053

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • heat_transfer: Recover
  • 4.38.1The system shall run a simulation with heat conduction, a heat source, thermal contact, and boundary conditions.

    Specification(s): recover_1

    Design: Heat Transfer Module

    Issue(s): #10079

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.38.2The system shall run a short simulation with heat conduction, a heat source, thermal contact, and boundary conditions.

    Specification(s): recover_2

    Design: Heat Transfer Module

    Issue(s): #10079

    Collection(s): FUNCTIONAL

    Type(s): RunApp

    Prerequisite(s): 4.38.1

  • 4.38.3The system shall be able to recover from a short simulation and reproduce a the full time scale simulation with heat conduction, a heat source, thermal contact, and boundary conditions.

    Specification(s): recover_3

    Design: Heat Transfer Module

    Issue(s): #10079

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 4.38.2

  • 4.38.4The system shall run a simulation with heat conduction, a heat source, thermal contact, and boundary conditions with automatic differentiation.

    Specification(s): ad_recover_1

    Design: Heat Transfer Module

    Issue(s): #10079

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.38.5The system shall run a short simulation with heat conduction, a heat source, thermal contact, and boundary conditions with automatic differentiation.

    Specification(s): ad_recover_2

    Design: Heat Transfer Module

    Issue(s): #10079

    Collection(s): FUNCTIONAL

    Type(s): RunApp

    Prerequisite(s): 4.38.4

  • 4.38.6The system shall be able to recover from a short simulation and reproduce a the full time scale simulation with heat conduction, a heat source, thermal contact, and boundary conditions with automatic differentiation.

    Specification(s): ad_recover_3

    Design: Heat Transfer Module

    Issue(s): #10079

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 4.38.5

  • heat_transfer: Semiconductor Linear Conductivity
  • 4.39.1The system shall compute conductivity of semiconductors according to the Steinhart-Hart equation

    Specification(s): test

    Design: SemiconductorLinearConductivity

    Issue(s): #10278

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • heat_transfer: Thermal Materials
  • 4.41.1The system shall be able to compute thermal compliance and its sensitivity in the heat transfer module.

    Specification(s): 2d

    Design: ThermalComplianceThermalSensitivity

    Issue(s): #25602

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • heat_transfer: Thin Layer Heat Transfer
  • 4.42.1The system shall model steady state heat transfer with an interface between two domains in 2D.

    Specification(s): steady_2d

    Design: ThinLayerHeatTransfer

    Issue(s): #21988

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.42.2The system shall model steady state heat transfer with an interface between two domains in 3D.

    Specification(s): steady_3d

    Design: ThinLayerHeatTransfer

    Issue(s): #21988

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.42.3The system shall model transient heat transfer with an interface between two domains in 2D.

    Specification(s): transient_2d

    Design: ThinLayerHeatTransfer

    Issue(s): #21988

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.42.4The system shall model transient heat transfer with an interface between two domains in 3D.

    Specification(s): transient_3d

    Design: ThinLayerHeatTransfer

    Issue(s): #21988

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 4.42.5The Jacobian for the ThinLayerHeatTransfer calculations shall provide perfect jacobians.

    Specification(s): jacobian

    Design: ThinLayerHeatTransfer

    Issue(s): #21988

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • heat_transfer: Verify Against Analytical
  • 4.45.1Heat conduction shall match the answer from an analytical solution in 1D

    Specification(s): 1D_transient

    Design: HeatConduction

    Issue(s): #5975

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • Heat conduction from an AD kernel shall get the same answer as a traditional kernel in 1D

    Specification(s): ad_1D_transient

    Design: HeatConduction

    Issue(s): #5658#12633

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • AD heat conduction and the Jacobian shall be beautiful in 1D

    Specification(s): ad_1D_transient_jacobian

    Design: HeatConduction

    Issue(s): #5658#12633

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 4.45.4Heat conduction shall match the answer from an analytical solution in 2D

    Specification(s): 2D_steady_state

    Design: HeatConduction

    Issue(s): #8194

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • Heat conduction from an AD kernel shall get the same answer as a traditional kernel in 2D

    Specification(s): ad_2D_steady_state

    Design: HeatConduction

    Issue(s): #5658#12633

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • AD heat conduction and the Jacobian shall be beautiful in 2D

    Specification(s): ad_2D_steady_state_jacobian

    Design: HeatConduction

    Issue(s): #5658#12633

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • heat_transfer: View Factors
  • 4.46.1The system shall compute view factors for unobstructed, planar surfaces without normalization.

    Specification(s): unnormalized

    Design: UnobstructedPlanarViewFactor

    Issue(s): #13918#16954

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 4.46.2The system shall compute view factors for cavities with obstruction using ray tracing.

    Specification(s): obstructed

    Design: RayTracingViewFactor

    Issue(s): #13918#16954

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 4.46.3The system shall compute view factors for unobstructed, planar surfaces in two-dimensional meshes using simple quadrature rules.

    Specification(s): analytical2D

    Design: UnobstructedPlanarViewFactor

    Issue(s): #13918#16954

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 4.46.4The system shall compute view factors for unobstructed, planar surfaces in two-dimensional meshes using ray tracing.

    Specification(s): ray2D

    Design: RayTracingViewFactor

    Issue(s): #13918#16954

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 4.46.5The system shall compute view factors for unobstructed, planar surfaces in three-dimensional meshes using simple quadrature rules.

    Specification(s): analytical3D

    Design: UnobstructedPlanarViewFactor

    Issue(s): #13918#16954

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 4.46.6The system shall compute view factors for unobstructed, planar surfaces in three-dimensional meshes using ray tracing.

    Specification(s): ray3D

    Design: RayTracingViewFactor

    Issue(s): #13918#16954

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 4.46.7The system shall be able to skip rays that exit the mesh when starting from non-planar faces in three-dimensional problems.

    Specification(s): ray3D_nonplanar

    Design: RayTracingViewFactor

    Issue(s): #13918#16954

    Collection(s): FUNCTIONAL

    Type(s): RunApp

Usability Requirements

No requirements of this type exist for this application, beyond those of its dependencies.

Performance Requirements

No requirements of this type exist for this application, beyond those of its dependencies.

System Interface Requirements

No requirements of this type exist for this application, beyond those of its dependencies.

References

No citations exist within this document.