Heat Transfer System Design Description

This template follows INL template TEM-140, "IT System Design Description."

commentnote

This document serves as an addendum to Framework System Design Description and captures information for SDD specific to the Heat Transfer module.

Introduction

The MOOSE Heat Transfer module is based on the MOOSE framework and thus inherits the unique features and base characteristics of the framework, as outlined in the Framework System Design Description. Specific details unique to the module are outlined in this document.

System Purpose

The Software Design Description provided here is description of each object in the system. The pluggable architecture of the underlying framework of the Heat Transfer module makes MOOSE and MOOSE-based applications straightforward to develop as each piece of end-user (developer) code that goes into the system follows a well-defined interface for the underlying systems that those object plug into. These descriptions are provided through developer-supplied "markdown" files that are required for all new objects that are developed as part of the Heat Transfer module. More information about the design documentation for MOOSE-based applications and like the Heat Transfer module can be found in Documenting MOOSE.

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.

Dependencies and Limitations

The Heat Transfer module inherits the software dependencies and limitations of the MOOSE framework, as well as the dependencies and limitations of the ray tracing module. The Heat Transfer module does not support modeling heat transfer due to convection, e.g. bulk fluid motion. The Navier-Stokes module must be used for that purpose.

Definitions and Acronyms

This section defines, or provides the definition of, all terms and acronyms required to properly understand this specification.

Definitions

  • Pull (Merge) Request: A proposed change to the software (e.g. usually a code change, but may also include documentation, requirements, design, and/or testing).

  • Baseline: A specification or product (e.g., project plan, maintenance and operations (M&O) plan, requirements, or design) that has been formally reviewed and agreed upon, that thereafter serves as the basis for use and further development, and that can be changed only by using an approved change control process (NQA-1, 2009).

  • Validation: Confirmation, through the provision of objective evidence (e.g., acceptance test), that the requirements for a specific intended use or application have been fulfilled (24765:2010(E), 2010).

  • Verification: (1) The process of: evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase. (2) Formal proof of program correctness (e.g., requirements, design, implementation reviews, system tests) (24765:2010(E), 2010).

Acronyms

AcronymDescription
APIApplication Programming Interface
DOE-NEDepartment of Energy, Nuclear Energy
FEfinite element
HITHierarchical Input Text
HPCHigh Performance Computing
I/OInput/Output
INLIdaho National Laboratory
MOOSEMultiphysics Object Oriented Simulation Environment
MPIMessage Passing Interface
SDDSoftware Design Description

Design Stakeholders and Concerns

Design Stakeholders

Stakeholders for MOOSE include several of the funding sources including DOE-NE and the INL. However, Since MOOSE is an open-source project, several universities, companies, and foreign governments have an interest in the development and maintenance of the MOOSE project.

Stakeholder Design Concerns

Concerns from many of the stakeholders are similar. These concerns include correctness, stability, and performance. The mitigation plan for each of these can be addressed. For correctness, Heat Transfer module development requires either regression or unit testing for all new code added to the repository. The project contains several comparisons against analytical solutions where possible and also other verification methods such as MMS. For stability, the Heat Transfer module (located within the MOOSE repository) maintains multiple branches to incorporate several layers of testing both internally and for dependent applications. Finally, performance tests are also performed as part of the the normal testing suite to monitor code change impacts to performance.

System Design

The Heat Transfer module inherits the wide range of pluggable systems from MOOSE. More information regarding MOOSE system design can be found in the framework System Design section. Most of the capability of the Heat Transfer module comes through volumetric kernels, integrated boundary conditions, and mortar-method based constraints. The kernels model volumetric heat conduction and heat sources and sinks. The boundary conditions and mortar constraints model surface heat transfer due to conduction and radiation. Documentation for each object, data structure, and process specific to the module are kept up-to-date alongside the MOOSE documentation. Expected failure modes and error conditions are accounted for via regression testing, and error conditions are noted in object documentation where applicable.

System Structure

The architecture of the Heat Transfer module consists of a core and several pluggable systems (both inherited from the MOOSE framework). The core of MOOSE consists of a number of key objects responsible for setting up and managing the user-defined objects of a finite element or finite volume simulation. This core set of objects has limited extendability and exists for every simulation configuration that the module is capable of running.

The MooseApp is the top-level object used to hold all of the other objects in a simulation. In a normal simulation a single MooseApp object is created and "run()". This object uses its Factory objects to build user-defined objects which are stored in a series of Warehouse objects and executed. The Finite Element and/or Finite Volume data is stored in the Systems and Assembly objects while the domain information (the Mesh) is stored in the Mesh object. A series of threaded loops are used to run parallel calculations on the objects created and stored within the warehouses.

MOOSE's pluggable systems are documented on MOOSE website, and those for the Heat Transfer module are on this webpage, accessible through the high-level system links above. Each of these systems has a set of defined polymorphic interfaces and are designed to accomplish a specific task within the simulation. The design of these systems is fluid and is managed through agile methods and ticket request system either on GitHub (for MOOSE) or on the defined software repository for this application.

Data Design and Control

At a high level, the system is designed to process HIT input files to construct several objects that will constitute an FE simulation. Some of the objects in the simulation may in turn load other file-based resources to complete the simulation. Examples include meshes or data files. The system will then assemble systems of equations and solve them using the libraries of the Code Platform. The system can then output the solution in one or more supported output formats commonly used for visualization.

Human-Machine Interface Design

The Heat Transfer module is a command-line driven program. All interaction with the Heat Transfer module is ultimately done through the command line. This is typical for HPC applications that use the MPI interface for running on super computing clusters. Optional GUIs may be used to assist in creating input files and launching executables on the command line.

System Design Interface

All external system interaction is performed either through file I/O or through local API calls. Neither the Heat Transfer module, nor the MOOSE framework, nor the other MOOSE modules are designed to interact with any external system directly through remote procedure calls. Any code to code coupling performed using the framework are done directly through API calls either in a static binary or after loading shared libraries.

Security Structure

The Heat Transfer module does not require any elevated privileges to operate and does not run any stateful services, daemons or other network programs. Distributed runs rely on the MPI library.

Requirements Cross-Reference

  • heat_transfer: ADConvectiveHeatFluxBC
  • 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: HeatConduction
  • 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

  • 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

  • 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: ConvectiveFluxFunction
  • 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

  • 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

  • heat_transfer: ConvectiveHeatFluxBC
  • 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: GapHeatTransfer
  • 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

  • 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

  • 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

  • 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

  • 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

  • 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.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: GapConductance
  • 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.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: ThermalContactAction
  • 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.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.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: CoupledConvectiveHeatFluxBC
  • 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

  • heat_transfer: HeatSource
  • 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

  • heat_transfer: FunctionRadiativeBC
  • 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

  • 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

  • heat_transfer: GaussianEnergyFluxBC
  • 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: HeatConductionFV
  • 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.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: HeatConductionCG
  • 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

  • heat_transfer: RayTracingViewFactor
  • 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

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

  • heat_transfer: Heat Transfer Module
  • 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

  • 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

  • 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

  • 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

  • heat_transfer: ThinLayerHeatTransfer
  • 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

References

  1. ISO/IEC/IEEE 24765:2010(E). Systems and software engineering—Vocabulary. first edition, December 15 2010.[BibTeX]
  2. ASME NQA-1. ASME NQA-1-2008 with the NQA-1a-2009 addenda: Quality Assurance Requirements for Nuclear Facility Applications. first edition, August 31 2009.[BibTeX]