Heat Conduction 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 Software Design Description (SDD) specific to the Heat Conduction application.

Introduction

Frameworks are a software development construct aiming to simplify the creation of specific classes of applications through abstraction of low-level details. The main object of creating a framework is to provide an interface to application developers that saves time and provides advanced capabilities not attainable otherwise. The MOOSE, mission is just that: provide a framework for engineers and scientists to build state-of-the-art, computationally scalable finite element based simulation tools.

MOOSE was conceived with one major objective: to be as easy and straightforward to use by scientists and engineers as possible. MOOSE is meant to be approachable by non-computational scientists who have systems of PDEs they need to solve. Every single aspect of MOOSE was driven by this singular principle from the build system to the API to the software development cycle. At every turn, decisions were made to enable this class of users to be successful with the framework. The pursuit of this goal has led to many of the unique features of MOOSE:

  • A streamlined build system

  • An API aimed at extensible

  • Straightforward APIs providing sensible default information

  • Integrated, automatic, and rigorous testing

  • Rapid, continuous integration development cycle

  • Codified, rigorous path for contributing

  • Applications are modular and composable

Each of these characteristics is meant to build trust in the framework by those attempting to use it. For instance, the build system is the first thing potential framework users come into contact with when they download a new software framework. Onerous dependency issues, complicated, hard to follow instructions or build failure can all result in a user passing on the platform. Ultimately, the decision to utilize a framework comes down to whether or not you trust the code in the framework and those developing it to be able to support your desired use-case. No matter the technical capabilities of a framework, without trust users will look elsewhere. This is especially true of those not trained in software development or computational science.

Developing trust in a framework goes beyond utilizing "best practices" for the code developed, it is equally important that the framework itself is built upon tools that are trusted. For this reason, MOOSE relies on a well-established code base of libMesh and PETSc. The libMesh library provides foundational capability for the finite element method and provides interfaces to leading-edge numerical solution packages such as PETSc.

With these principles in mind, an open source, massively parallel, finite element, multiphysics framework has been conceived. MOOSE is an on-going project started in 2008 aimed toward a common platform for creation of new multiphysics tools. This document provides design details pertinent to application developers as well as framework developers.

Use Cases

The MOOSE Framework is targeted at two main groups of actors: Developers and Users. Developers are the main use case. These are typically students and professionals trained in science and engineering fields with some level of experience with coding but typically very little formal software development training. The other user group is Users. Those who intend to use an application built upon the framework without writing any computer code themselves. Instead they may modify or create input files for driving a simulation, run the application, and analyze the results. All interactions through MOOSE are primarily through the command-line interface and through a customizable block-based input file.

System Purpose

The Software Design Description provided here is description of each object in the system. The pluggable architecture of the framework 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 framework, modules and derivative applications. More information about the design documentation can be found in Documenting MOOSE.

System Scope

The purpose of this software is to provide several libraries that can be used to build an application based upon the framework. Additionally, several utilities are provided for assisting developers and users in end-to-end FEM analysis. A brief overview of the major components are listed here:

ComponentDescription
framework libraryThe base system from which all MOOSE-based applications are created
module librariesOptional "physics" libraries that may be used in an application to provide capability
build systemThe system responsible for creating applications for a series of libraries and applications
test harnessThe extendable testing system for finding, scheduling, running, and reporting regression tests
"peacock"The GUI for building input files, executing applications, and displaying results
MooseDocsThe extendable markdown system for MOOSE providing common documentation and requirements enforcement
"stork"The script and templates for generating a new MOOSE-based application ready for building and testing
examplesA set of complete applications demonstrating the use of MOOSE's pluggable systems
tutorialsStep by step guides to building up an application using MOOSE's pluggable systems
unitAn application for unit testing individual classes or methods of C++ code

Dependencies and Limitations

The MOOSE platform has several dependencies on other software packages and has scope that is constantly evolving based upon funding, resources, priorities, and lab direction. However, the software is open-source and many features and even bugs can be offloaded to developers with appropriate levels of knowledge and direction from the main design team. The primary list of software dependencies is listed below. This list is not meant to be exhaustive. Individual operating systems may require specific packages to be installed prior to using MOOSE, which can be found on the Install MOOSE pages.

Software DependencyDescription
libMeshFinite Element Library and I/O routines
PETScSolver Package
hypreMultigrid Preconditioner
MPIA distributed parallel processing library (MPICH)

Figure 1: A diagram of the MOOSE code platform.

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]

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
FEMFinite Element Method
GUIgraphical user interface
HITHierarchical Input Text
HPCHigh Performance Computing
I/OInput/Output
INLIdaho National Laboratory
MOOSEMultiphysics Object Oriented Simulation Environment
MPIMessage Passing Interface
PDEspartial differential equations
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, MOOSE 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, MOOSE 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 MOOSE framework itself is composed of a wide range of pluggable systems. Each system is generally composed of a single or small set of C++ objects intended to be specialized by a Developer to solve a specific problem. To accomplish this design goal, MOOSE uses several modern object-oriented design patterns. The primary overarching pattern is the "Factory Pattern". Users needing to extend MOOSE may inherit from one of MOOSE's systems to providing an implementation meeting his or her needs. The design of each of these systems is documented on the mooseframework.org wiki in the Tutorial section. Additionally, up-to-date documentation extracted from the source is maintained on the the mooseframework.org documentation site after every successful merge to MOOSE's stable branch. After these objects are created, the can be registered with the framework and used immediately in a MOOSE input file.

System Structure

The MOOSE framework architecture consists of a core and several pluggable systems. 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 simulation. This core set of objects has limited extendability and exist for every simulation configuration that the framework is capable of running.

Adaptivity

Adaptivity/Indicators

Adaptivity/Markers

AuxKernels

AuxKernels/MatVecRealGradAuxKernel

AuxKernels/MaterialVectorAuxKernel

AuxKernels/MaterialVectorGradAuxKernel

AuxScalarKernels

AuxVariables

AuxVariables/MultiAuxVariables

BCs

BCs/CavityPressure

BCs/CoupledPressure

BCs/InclinedNoDisplacementBC

BCs/Periodic

BCs/Pressure

Bounds

Closures

Components

Constraints

Contact

ControlLogic

Controls

CoupledHeatTransfers

Covariance

DGKernels

Dampers

Debug

Debug/MaterialDerivativeTest

DeprecatedBlock

DiracKernels

Distributions

DomainIntegral

Executioner

Executioner/Adaptivity

Executioner/Predictor

Executioner/Quadrature

Executioner/TimeIntegrator

Executioner/TimeStepper

Executors

FVBCs

FVInterfaceKernels

FVKernels

FluidPropertiesInterrogator

Functions

GeochemicalModelInterrogator

GlobalParams

GrayDiffuseRadiation

HeatStructureMaterials

ICs

ICs/PolycrystalICs

ICs/PolycrystalICs/BicrystalBoundingBoxIC

ICs/PolycrystalICs/BicrystalCircleGrainIC

ICs/PolycrystalICs/PolycrystalColoringIC

ICs/PolycrystalICs/PolycrystalRandomIC

ICs/PolycrystalICs/PolycrystalVoronoiVoidIC

ICs/PolycrystalICs/Tricrystal2CircleGrainsIC

InterfaceKernels

Kernels

Kernels/CHPFCRFFSplitKernel

Kernels/DynamicTensorMechanics

Kernels/HHPFCRFFSplitKernel

Kernels/PFCRFFKernel

Kernels/PolycrystalElasticDrivingForce

Kernels/PolycrystalKernel

Kernels/PolycrystalStoredEnergy

Kernels/PoroMechanics

Kernels/RigidBodyMultiKernel

Kernels/TensorMechanics

Materials

Mesh

Mesh/Partitioner

Modules

Modules/CompressibleNavierStokes

Modules/FluidProperties

Modules/HeatConduction

Modules/HeatConduction/ThermalContact

Modules/HeatConduction/ThermalContact/BC

Modules/IncompressibleNavierStokes

Modules/NavierStokesFV

Modules/Peridynamics

Modules/Peridynamics/Mechanics

Modules/Peridynamics/Mechanics/GeneralizedPlaneStrain
Modules/Peridynamics/Mechanics/Master

Modules/PhaseField

Modules/PhaseField/Conserved

Modules/PhaseField/DisplacementGradients

Modules/PhaseField/EulerAngles2RGB

Modules/PhaseField/GrainGrowth

Modules/PhaseField/GrandPotential

Modules/PhaseField/Nonconserved

Modules/PorousFlow

Modules/PorousFlow/BCs

Modules/TensorMechanics

Modules/TensorMechanics/CohesiveZoneMaster

Modules/TensorMechanics/DynamicMaster

Modules/TensorMechanics/GeneralizedPlaneStrain

Modules/TensorMechanics/GlobalStrain

Modules/TensorMechanics/LineElementMaster

Modules/TensorMechanics/Master

Modules/TensorMechanics/MaterialVectorBodyForce

MortarGapHeatTransfer

MultiApps

NodalKernels

NodalNormals

Outputs

PorousFlowBasicTHM

PorousFlowFullySaturated

PorousFlowUnsaturated

Postprocessors

Preconditioning

Problem

RayBCs

RayKernels

ReactionNetwork

ReactionNetwork/AqueousEquilibriumReactions

ReactionNetwork/SolidKineticReactions

Reporters

Samplers

ScalarKernels

SpatialReactionSolver

StochasticTools

Surrogates

ThermalContact

TimeDependentReactionSolver

TimeIndependentReactionSolver

Trainers

Transfers

UserObjects

Variables

Variables/CHPFCRFFSplitVariables

Variables/HHPFCRFFSplitVariables

Variables/PFCRFFVariables

Variables/PolycrystalVariables

VectorPostprocessors

XFEM

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 it's Factory objects to build user defined objects which are stored in a series of Warehouse objects and executed. The Finite Element data is stored in the Systems and Assembly object 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 the mooseframework.org wiki. Each of these systems has 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 on the Github.org website.

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

MOOSE is a command-line driven program. All interaction with MOOSE and MOOSE-based codes 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 framework, nor the 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 framework 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_conduction: ADConvectiveHeatFluxBC
  • 5.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_conduction: HeatConduction
  • 5.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

  • 5.19.1The system shall compute a tri-linear temperature field

    Specification(s): test

    Design: HeatConduction

    Issue(s): #6750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

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

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

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

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

  • 5.36.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_conduction: ConvectiveFluxFunction
  • 5.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

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

  • 5.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_conduction: ConvectiveHeatFluxBC
  • 5.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_conduction: GapHeatTransfer
  • 5.10.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

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

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

  • 5.11.1Thermal 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

  • 5.11.2Thermal 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

  • 5.11.3Thermal 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

  • 5.11.4Thermal 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

  • 5.11.5Thermal 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

  • 5.11.6Thermal 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

  • 5.11.7Thermal 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

  • 5.11.8Thermal 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

  • 5.11.9Thermal 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

  • 5.11.10Thermal 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

  • 5.11.11Thermal 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

  • 5.11.12Thermal 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

  • 5.11.13Thermal 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

  • 5.11.14Thermal 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

  • 5.11.15Thermal 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

  • 5.14.1The system shall be able to compute heat flux across a gap using the ThermalContact methods

    Specification(s): test

    Design: GapHeatTransfer

    Issue(s): #1609

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 5.17.18Optionally 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

  • 5.17.19Optionally 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

  • 5.23.1The ThermalContact system shall enforce heat transfer across a meshed gap in a 2D plane geometry.

    Specification(s): test

    Design: ThermalContact SystemGapHeatTransfer

    Issue(s): #716

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): annulus

    Design: ThermalContact SystemGapHeatTransfer

    Issue(s): #716

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • heat_conduction: GapConductance
  • 5.17.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

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

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

  • 5.17.18Optionally 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

  • 5.17.19Optionally 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_conduction: CoupledConvectiveHeatFluxBC
  • 5.17.12The 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

  • 5.17.13The 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

  • 5.17.14The 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

  • 5.17.15The 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): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 5.17.16The 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): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 5.17.17The 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_conduction: HeatSource
  • 5.20.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_conduction: RayTracingViewFactor
  • 5.29.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

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

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

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

  • heat_conduction: Heat Conduction Module
  • 5.31.1The system shall run a simulation with heat conduction, a heat source, thermal contact, and boundary conditions.

    Specification(s): recover_1

    Design: Heat Conduction Module

    Issue(s): #10079

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): recover_2

    Design: Heat Conduction Module

    Issue(s): #10079

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 5.31.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 Conduction Module

    Issue(s): #10079

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 5.31.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 Conduction Module

    Issue(s): #10079

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 5.31.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 Conduction Module

    Issue(s): #10079

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 5.31.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 Conduction Module

    Issue(s): #10079

    Collection(s): FUNCTIONAL

    Type(s): Exodiff