Heat Conduction Requirements Traceability Matrix
This template follows INL template TEM-214, "IT System Requirements Traceability Matrix."
This document serves as an addendum to Framework Requirements Traceability Matrix and captures information for Requirement Traceability Matrix (RTM) specific to the Heat Conduction application.
Introduction
Minimum System Requirements
In general, the following is required for MOOSE-based development:
GCC/Clang C++17 compliant compiler (GCC @ 7.5.0, Clang @ 5.0.2 or greater)
Note: Intel compilers are not supported.
Memory: 16 GBs (debug builds)
Processor: 64-bit x86
Disk: 30GB
System Purpose
The MOOSE is a tool for solving complex coupled Multiphysics equations using the finite element method. MOOSE uses an object-oriented design to abstract data structure management, parallelism, threading and compiling while providing an easy to use interface targeted at engineers that may not have a lot of software development experience. MOOSE will require extreme scalability and flexibility when compared to other FEM frameworks. For instance, MOOSE needs the ability to run extremely complex material models, or even third-party applications within a parallel simulation without sacrificing parallelism. This capability is in contrast to what is often seen in commercial packages, where custom material models can limit the parallel scalability, forcing serial runs in the most severe cases. When comparing high-end capabilities, many MOOSE competitors target modest-sized clusters with just a few thousand processing cores. MOOSE, however, will be required to routinely executed on much larger clusters with scalability to clusters available in the top 500 systems (top500.org). MOOSE will also be targeted at smaller systems such as high-end laptop computers.
The design goal of MOOSE is to give developers ultimate control over their physical models and applications. Designing new models or solving completely new classes of problems will be accomplished by writing standard C++ source code within the framework's class hierarchy. Scientists and engineers will be free to implement completely new algorithms using pieces of the framework where possible, and extending the framework's capabilities where it makes sense to do so. Commercial applications do not have this capability, and instead opt for either a more rigid parameter system or a limited application-specific metalanguage.
System Scope
MOOSE's scope is to provide a set of interfaces for building FEM simulations. Abstractions to all underlying libraries are provided.
Solving coupled problems where competing physical phenomena impact one and other in a significant nonlinear fashion represents a serious challenge to several solution strategies. Small perturbations in strongly-coupled parameters often have very large adverse effects on convergence behavior. These adverse effects are compounded as additional physics are added to a model. To overcome these challenges, MOOSE employs three distinct yet compatible systems for solving these types of problems.
First, an advanced numerical technique called the Jacobian-Free Newton-Krylov (JFNK) method is employed to solve the most fully-coupled physics in an accurate, consistent way. An example of this would be the effect of temperature on the expansion or contraction of a material. While the JFNK numerical method is very effective at solving fully-coupled equations, it can also be computationally expensive. Plus, not all physical phenomena in a given model are truly coupled to one another. For instance, in a reactor, the speed of the coolant flow may not have any direct effect on the complex chemical reactions taking place inside the fuel rods. We call such models "loosely-coupled". A robust, scalable system must strike the proper balance between the various modeling strategies to avoid performing unnecessary computations or incorrectly predicting behavior in situations such as these.
MOOSE's Multiapp system will allow modelers to group physics into logical categories where MOOSE can solve some groups fully-coupled and others loosely-coupled. The Multiapp system goes even further by also supporting a "tightly-coupled" strategy, which falls somewhere between the "fully-coupled" and "loosely-coupled" approaches. Several sets of physics can then be linked together into logical hierarchies using any one of these coupling strategies, allowing for several potential solution strategies. For instance, a complex nuclear reactor model might consist of several tightly-coupled systems of fully-coupled equations.
Finally, MOOSE's Transfers system ties all of the physics groups contained within the Multiapp system together and allows for full control over the flow of information among the various groups. This capability bridges physical phenomena from several different complementary scales simultaneously. When these three MOOSE systems are combined, myriad coupling combinations are possible. In all cases, the MOOSE framework handles the parallel communication, input, output and execution of the underlying simulation. By handling these computer science tasks, the MOOSE framework keeps modelers focused on doing research.
MOOSE innovates by building advanced simulation capabilities on top of the very best available software technologies in a way that makes them widely accessible for innovative research. MOOSE is equally capable of solving small models on common laptops and the very biggest FEM models ever attempted—all without any major changes to configuration or source code. Since its inception, the MOOSE project has focused on both developer and computational efficiency. Improved developer efficiency is achieved by leveraging existing algorithms and technologies from several leading open-source packages. Additionally, MOOSE uses several complementary parallel technologies (both the distributed-memory message passing paradigm and shared-memory thread-based approaches are used) to lay an efficient computational foundation for development. Using existing open technologies in this manner helps the developers reduce the scope of the project and keeps the size of the MOOSE code base maintainable. This approach provides users with state-of-the-art finite element and solver technology as a basis for the advanced coupling and solution strategies mentioned previously.
MOOSE's developers work openly with other package developers to make sure that cutting-edge technologies are available through MOOSE, providing researchers with competitive research opportunities. MOOSE maintains a set of objects that hide parallel interfaces while exposing advanced spatial and temporal coupling algorithms in the framework. This accessible approach places developmental technology into the hands of scientists and engineers, which can speed the pace of scientific discovery.
Assumptions and Dependencies
The Heat Conduction application is developed using MOOSE and is based on various modules, as such the RTM for Heat Conduction 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.
System Requirements Traceability
Functional Requirements
- heat_conduction: Nafems
- 5.1.1The system shall compute the transient heat conduction solution for the NAFEMS T3 benchmark problem using a coarse mesh and
- HEX8 elements
- HEX20 elements
- HEX27 elements
- EDGE2 elements
- EDGE3 elements
- QUAD4 elements
- QUAD8 elements
- QUAD9 elements
Specification(s): coarse_mesh/hex8, coarse_mesh/hex20, coarse_mesh/hex27, coarse_mesh/edge2, coarse_mesh/edge3, coarse_mesh/quad4, coarse_mesh/quad8, coarse_mesh/quad9
Design: HeatConductionTimeDerivative
Issue(s): #14838
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.1.2The system shall compute the transient heat conduction solution for the NAFEMS T3 benchmark problem using a fine mesh and
- HEX8 mesh
- HEX20 mesh
- HEX27 mesh
- EDGE2 mesh
- EDGE3 mesh
- QUAD4 mesh
- QUAD8 mesh
- QUAD9 mesh
Specification(s): fine_mesh/hex8, fine_mesh/hex20, fine_mesh/hex27, fine_mesh/edge2, fine_mesh/edge3, fine_mesh/quad4, fine_mesh/quad8, fine_mesh/quad9
Design: HeatConductionTimeDerivative
Issue(s): #14838
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- heat_conduction: Ad Convective Heat Flux
- 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
- and match hand calculations for flux through a boundary.
- and approach a constant far-field temperature value over time as heat flux decreases.
- 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: Ad Heat Conduction
- 5.3.1AD heat conduction and the Jacobian shall be beautiful
Specification(s): jacobian_test
Design: ADHeatConduction
Collection(s): FUNCTIONAL
Type(s): PetscJacobianTester
- heat_conduction: Code Verification
- 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
- heat_conduction: Conjugate Heat Transfer
- 5.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_conduction: Convective Flux Function
- 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
Prerequisite(s): 5.6.1
- 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
Prerequisite(s): 5.6.2
- heat_conduction: Convective Heat Flux
- 5.7.1The system shall provide a convective flux boundary condition which uses material properties as heat transfer coefficients and far-field temperature values
- and match hand calculations for flux through a boundary.
- and approach a constant far-field temperature value over time as heat flux decreases.
- 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: Function Ellipsoid Heat Source
- 5.8.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_conduction: Fvbcs
- 5.9.1The system shall be able to solve a heat conduction problem with boundary conditions representing radiation to an infinite cylinder.
Specification(s): infinite_cylinder_radiation
Design: FVInfiniteCylinderRadiativeBC
Issue(s): #18626
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.9.2The system shall be able to solve a heat conduction problem with diffusion/conduction/radiation combined thermal resistance boundary conditions
- using regular material properties.
- using regular material properties in RZ geometry.
- using functor material properties.
- using functor material properties in RZ geometry.
Specification(s): thermal_resistance/matprop, thermal_resistance/matprop_rz, thermal_resistance/functor_matprop, thermal_resistance/functor_matprop_rz
Design: FVThermalResistanceBC
Issue(s): #18626
Collection(s): FUNCTIONAL
Type(s): Exodiff
- heat_conduction: Gap Heat Transfer Balance
- 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
- heat_conduction: Gap Heat Transfer Htonly
- 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
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
- heat_conduction: Gap Heat Transfer Mortar
- 5.12.1We shall be able to produce the expected result for a gap conductance test case using the mortar method.
Specification(s): test
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.12.2We shall be able to produce the expected result for a gap conductance test case using the mortar method using the modular gap flux system.
Specification(s): modular
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.12.3We shall be able to produce the expected result for a combined gap conductance and radiative heat transfer test case using the mortar method using the modular gap flux system
Specification(s): modular_multiple
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.12.4We shall be able to run the mortar method on a displaced mesh, supplying the displacements with constant** auxiliary variables
Specification(s): displaced
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.12.5We shall be able to produce the expected result for a gap conductance test case using the mortar method using the modular gap flux system with a displaced mesh.
Specification(s): modular_displaced
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.12.6The system shall accurately calculate axisymmetric coordinates on mortar finite element segments
Specification(s): displaced_rz
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.12.7We shall be able to generate node-to-segment numerical results for radiation through plates and use it as a reference for mortar-based constraints.
Specification(s): bc_gap_heat_transfer_displaced_radiation
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.8We shall be able to generate mortar numerical results for radiation through plates that are close to those generated by the node-to-segment formulation.
Specification(s): modular_gap_heat_transfer_mortar_displaced_radiation
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.9We shall be able to generate node-to-segment numerical results for conduction through plates and use it as a reference for mortar-based constraints.
Specification(s): bc_gap_heat_transfer_displaced_conduction
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.10We shall be able to generate mortar numerical results for conduction through plates that are close to those generated by the node-to-segment formulation.
Specification(s): modular_gap_heat_transfer_mortar_displaced_conduction
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.11We shall be able to generate node-to-segment numerical results for conduction and radiation through cylinders and use it as a reference for mortar-based constraints.
Specification(s): large_gap_heat_transfer_test_cylinder
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.12We shall be able to generate mortar numerical results for conduction and radiationthrough cylinders that are close to those generated by the node-to-segment formulation.
Specification(s): large_gap_heat_transfer_test_cylinder_mortar
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.13We shall be able to generate node-to-segment numerical results for conduction and radiation through cylinders with axisymmetry and use it as a reference for mortar-based constraints.
Specification(s): large_gap_heat_transfer_test_rz_cylinder
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.14We shall be able to generate mortar numerical results for conduction and radiationthrough cylinders with axisymmetry that are close to those generated by the node-to-segment formulation.
Specification(s): large_gap_heat_transfer_test_rz_cylinder_mortar
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.15We shall be able to generate node-to-segment numerical results for conduction and radiation through concentric spheres with axisymmetry and use it as a reference for mortar-based constraints.
Specification(s): large_gap_heat_transfer_test_sphere
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.16We shall be able to generate mortar numerical results for conduction and radiation through concentric spheres with axisymmetry that are close to those generated by the node-to-segment formulation.
Specification(s): large_gap_heat_transfer_test_sphere_mortar
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.17We shall be able to generate mortar numerical results for conduction and radiation in two dimensions. This test is used as a reference for computing separate gap physics, i.e. for the use of multiple heat flux Lagrange multipliers
Specification(s): modular_gap_heat_transfer_mortar_displaced_radiation_conduction
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.18We shall be able to reproduce heat transfer mortar results when the gap physics (i.e. radiation and conduction) are separated in two constraint classes with independent Lagrange multipliers
Specification(s): modular_gap_heat_transfer_mortar_displaced_radiation_conduction_separate
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.19We shall be able to generate a meaningful error message if the user does not define the sphere origin when a spherical geometry has been chosen.
Specification(s): large_gap_heat_transfer_test_sphere_mortar_geometry_error
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 5.12.20We shall be able to generate a meaningful error message if the user does not define the cylinder points when a cylindrical geometry has been chosen.
Specification(s): large_gap_heat_transfer_test_cylinder_mortar_error
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 5.12.21We shall be able to generate mortar numerical results for conduction through plates that are close to those generated by the node-to-segment formulation and using the function feature to enrich the evolution of the gap conductance.
Specification(s): modular_gap_heat_transfer_mortar_displaced_conduction_function
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.22We shall be able to generate node-to-segment numerical results for conduction and radiation between two blocks in 3D and use it as a reference for mortar-based constraints.
Specification(s): gap_heat_transfer_3d
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.23We shall be able to generate node-to-segment numerical results for conduction and radiation between two blocks in 3D using HEX20 elements and use it as a reference for mortar-based constraints.
Specification(s): gap_heat_transfer_3d_hex20
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.24We shall be able to generate mortar numerical results for conduction and radiation between two blocks in 3D and match reasonably well with the node-to-segment approach with a refined mesh.
Specification(s): gap_heat_transfer_3d_mortar
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.25We shall be able to generate mortar numerical results for conduction and radiation between two blocks in 3D using HEX20 elements and match reasonably well with the node-to-segment approach with a refined mesh.
Specification(s): gap_heat_transfer_3d_mortar_hex20
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.26We shall be able to generate node-to-segment numerical results using thermal contact that resolves spherical heat transfer for a constant conductivity gap in 3D using HEX20 elements
Specification(s): gap_heat_transfer_sphere3d
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.27We shall be able to generate mortar numerical results using thermal contact that resolves spherical heat transfer for a constant conductivity gap in 3D using HEX20 elements and match reasonably well with the node-to-segment approach with a refined mesh.
Specification(s): gap_heat_transfer_sphere3d_mortar
Design: Constraints SystemModular Gap Conductance Constraint
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.12.28We shall be able to compute the thermal contact across a closed gap as a function of contact pressure,
- and the material thermal conductivities and hardness values consistent with an analytical solution for the temperatures at the interface.
Specification(s): pressure_dependent_conductance/closed_gap_prescribed_pressure
Design: GapFluxModelPressureDependentConduction
Issue(s): #20658
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- heat_conduction: Gap Heat Transfer Mortar Action
- 5.13.1We shall be able to leverage mortar constraint and user objects to describe gap heat transfer physics by spelling out those objects in the input file.
Specification(s): modular_gap_heat_transfer_mortar_displaced_radiation_conduction_verbose
Design: Constraints SystemModular Gap Conductance ConstraintMortar Gap Heat Transfer Action
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.13.2We shall be able to leverage mortar constraints and user objects to describe gap heat transfer physics by using the mortar thermal action in MOOSE.
Specification(s): modular_gap_heat_transfer_mortar_displaced_radiation_conduction_action
Design: Constraints SystemModular Gap Conductance ConstraintMortar Gap Heat Transfer Action
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.13.3We shall be able to leverage mortar constraints and user objects to describe gap heat transfer physics by using the mortar thermal action in MOOSE and describe the gap conductance with a function of temperature.
Specification(s): modular_gap_heat_transfer_mortar_displaced_conduction_UOs_function
Design: Constraints SystemModular Gap Conductance ConstraintMortar Gap Heat Transfer Action
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.13.4We shall be able to leverage mortar constraints and user objects to describe gap heat transfer physics by using the mortar thermal action in MOOSE when the lower-dimensional domains have already been appended to the mesh.
Specification(s): modular_gap_heat_transfer_mortar_displaced_radiation_conduction_action_lowerd_exists
Design: Constraints SystemModular Gap Conductance ConstraintMortar Gap Heat Transfer Action
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.13.5We shall be able to leverage mortar constraints and user objects to describe gap heat transfer physics by using the mortar thermal action in MOOSE when the user objects are manually built by the user in the input file.
Specification(s): modular_gap_heat_transfer_mortar_displaced_radiation_conduction_action_existing_UOs
Design: Constraints SystemModular Gap Conductance ConstraintMortar Gap Heat Transfer Action
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.13.6We shall be able to inform the user that he or she provided physics parameters for two ways of building gap heat transfer options and error out, to avoid having misleading input files.
Specification(s): modular_gap_heat_transfer_mortar_displaced_radiation_conduction_action_existing_UOs_error
Design: Constraints SystemModular Gap Conductance ConstraintMortar Gap Heat Transfer Action
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- heat_conduction: Gap Heat Transfer Radiation
- 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
- heat_conduction: Generate Radiation Patch
- 5.15.1The system shall be able to divide a sideset into patches for more accurate radiative transfer modeling.
Specification(s): generate_radiation_patch
Design: PatchSidesetGenerator
Issue(s): #14000
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.15.2The system shall be able to use linear partitioner for subdividing sidesets into patches.
Specification(s): generate_radiation_patch_linear
Design: PatchSidesetGenerator
Issue(s): #14000
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.15.3The system shall be able to use centroid partitioner for subdividing sidesets into patches.
Specification(s): generate_radiation_patch_centroid
Design: PatchSidesetGenerator
Issue(s): #14000
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.15.4The system shall error when centroid partitioner is used but centroid_partitioner_direction is not provided.
Specification(s): generate_radiation_patch_centroid_error
Design: PatchSidesetGenerator
Issue(s): #14000
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 5.15.5The system shall be able to use a uniform grid for subdividing sidesets into patches.
Specification(s): generate_radiation_patch_grid
Design: PatchSidesetGenerator
Issue(s): #15829
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.15.6The system shall be able to use a uniform grid for subdividing 1D sidesets into patches.
Specification(s): generate_radiation_patch_grid_2D
Design: PatchSidesetGenerator
Issue(s): #15829
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.15.7The system shall be able to adjust the number of patches of partitions that end up empty.
Specification(s): generate_radiation_patch_grid_2D_overpart
Design: PatchSidesetGenerator
Issue(s): #15829
Collection(s): FUNCTIONAL
Type(s): Exodiff
- heat_conduction: Gray Lambert Radiator
- 5.16.1The system shall check consistency of boundary and emissivity entries.
Specification(s): inconsistent_bnd_eps
Design: ConstantViewFactorSurfaceRadiation
Issue(s): #13918
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 5.16.2The system shall check consistency of boundary and view factor entries.
Specification(s): inconsistent_bnd_view_factors
Design: ConstantViewFactorSurfaceRadiation
Issue(s): #13918
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 5.16.3The system shall check consistency of fixed_boundary_temperatures and fixed_temperature_boundary entries.
Specification(s): inconsistent_iso_temperature
Design: ConstantViewFactorSurfaceRadiation
Issue(s): #13918
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 5.16.4The system shall check consistency of boundary and fixed_temperature_boundary entries.
Specification(s): inconsistent_bnd_iso_bnd
Design: ConstantViewFactorSurfaceRadiation
Issue(s): #13918
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 5.16.5The system shall check consistency of boundary and adiabatic_boundary entries.
Specification(s): inconsistent_bnd_adiabatic_bnd
Design: ConstantViewFactorSurfaceRadiation
Issue(s): #13918
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 5.16.6The system shall check consistency of the view_factors entry shape.
Specification(s): incorrect_view_factor_shape
Design: ConstantViewFactorSurfaceRadiation
Issue(s): #13918
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 5.16.7The system shall check consistency of the view_factors entry norm.
Specification(s): bad_rowsum
Design: ConstantViewFactorSurfaceRadiation
Issue(s): #13918
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 5.16.8The system shall compute radiative transfer between gray Lambert surfaces.
Specification(s): gray_lambert_cavity
Design: ConstantViewFactorSurfaceRadiationSurfaceRadiationVectorPostprocessorViewfactorVectorPostprocessor
Issue(s): #13918
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.16.9The system shall allow coupling radiative transfer between gray Lambert surfaces to solving heat conduction.
Specification(s): coupled_heat_conduction
Design: ConstantViewFactorSurfaceRadiation
Issue(s): #13918
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.16.10The system shall allow reconstructing the spatial distribution of the emission component on a radiation boundary via the T4 law.
Specification(s): coupled_heat_conduction_emission_reconstruction
Design: GrayLambertNeumannBC
Issue(s): #13918
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.16.11The system shall compute radiative transfer between gray Lambert surfaces when the view factors are provided by a userobject.
Specification(s): gray_lambert_cavity_automatic_vf
Design: ViewFactorObjectSurfaceRadiation
Issue(s): #13918
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.16.12The system shall compute radiative transfer between gray Lambert surfaces in 3D when the view factors are provided by a userobject.
Specification(s): gray_lambert_cavity_automatic_vf_3D
Design: ViewFactorObjectSurfaceRadiation
Issue(s): #13918
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- heat_conduction: Heat Conduction
- 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.4The system shall compute the heat transfer across small gaps for non-matching meshes.
Specification(s): nonmatching
Design: Thermal Contact Action
Issue(s): #6750
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.17.5The system shall compute the heat transfer across small gaps for second order FEM bases.
Specification(s): second_order
Design: Thermal Contact Action
Issue(s): #6750
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.17.6The system shall compute the heat transfer across small gaps for moving interfaces.
Specification(s): moving
Design: Thermal Contact Action
Issue(s): #6750
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.17.7The system shall compute the heat transfer across small gaps with a specified gap conductivity.
Specification(s): gap_conductivity_property
Design: Thermal Contact Action
Issue(s): #6750
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.17.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: Thermal Contact Action
Issue(s): #13043
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 5.17.9The system shall support thermal contact with linear 3d hexahedral elements
Specification(s): nonmatching
Design: Thermal Contact Action
Issue(s): #6750
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.17.10The system shall support thermal contact with second-order 3d hexahedral elements
Specification(s): second
Design: Thermal Contact Action
Issue(s): #6750
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.17.11The system shall support thermal contact with 3d hexahedral elements where the surfaces move relative to one another
Specification(s): moving
Design: Thermal Contact Action
Issue(s): #6750
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 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 ofT_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 ofT_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
- 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: Heat Conduction Ortho
- 5.18.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_conduction: Heat Conduction Patch
- 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
Prerequisite(s): 5.19.4
- heat_conduction: Heat Source Bar
- 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
- 5.20.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
- 5.20.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
Collection(s): FUNCTIONAL
Type(s): PetscJacobianTester
Prerequisite(s): 5.20.2
- heat_conduction: Homogenization
- 5.21.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
- heat_conduction: Joule Heating
- 5.22.1The system shall compute Joule heating
Specification(s): joule_heating
Design: JouleHeatingSource
Issue(s): #8220
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.22.2The system shall compute Joule heating using automatic differentiation
Specification(s): ad_joule_heating
Design: ADJouleHeatingSource
Issue(s): #15536
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.22.3The system shall compute a perfect jacobian for Joule heating using automatic differentiation
Specification(s): ad_joule_heating_jacobian
Design: ADJouleHeatingSource
Issue(s): #15536
Collection(s): FUNCTIONAL
Type(s): PetscJacobianTester
- heat_conduction: Meshed Gap Thermal Contact
- 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.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: ThermalContact SystemGapConductanceConstant
Issue(s): #13061
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.23.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: ThermalContact SystemGapConductanceConstant
Issue(s): #13061
Collection(s): FUNCTIONAL
Type(s): Exodiff
Prerequisite(s): 5.23.2
- 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: Multiple Contact Pairs
- 5.24.1Heat transfer module action shall allow for providing multiple contact pairs.
Specification(s): multiple_contact_pairs
Design: Thermal Contact Action
Issue(s): #18022
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- heat_conduction: Multiple Radiation Cavities
- 5.25.1The system shall support the the modeling of radiative heat transfer with multiple radiation cavities.
Specification(s): multiple_radiation_cavities
Design: Radiation Transfer Action
Issue(s): #16954
Collection(s): FUNCTIONAL
Type(s): Exodiff
- heat_conduction: Parallel Element Pps Test
- 5.26.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_conduction: Postprocessors
- 5.27.1The system shall compute total heat flux from heat transfer coefficient and temperature difference
Specification(s): convective_ht_side_integral
Design: ConvectiveHeatTransferSideIntegral
Issue(s): #14390
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.27.2The system shall compute total heat flux from heat transfer coefficient and temperature difference for AD variables
Specification(s): ad_convective_ht_side_integral
Design: ConvectiveHeatTransferSideIntegral
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- heat_conduction: Radiation Transfer Action
- 5.28.1The system shall provide an action to set up radiative heat transfer problems using the net radiation method for cavities with unobstructed, planar faces.
Specification(s): radiative_transfer_action_analytical
Design: Radiation Transfer Action
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.28.2The system shall provide an action to set up radiative heat transfer problems using the net radiation method and allow computing view factors using raytracing.
Specification(s): radiative_transfer_action_raytracing
Design: Radiation Transfer Action
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.28.3The system shall allow the specification of boundary names and ids in the modeling of radiative heat transfer.
Specification(s): bnd_names
Design: Radiation Transfer Action
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.28.4The system shall ensure that results between manually created radiative transfer inputs and inputs that use the radiation transfer action are identical.
Specification(s): no_action
Design: Radiation Transfer Action
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.28.5The system shall provide an action to set up radiative heat transfer problems where sidesets participating in the radiative exchange are external faces of the domain, with view factors computed by simple quadrature rules for cavities with unobstructed, planar faces.
Specification(s): external_boundary_analytical
Design: Radiation Transfer Action
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.28.6The system shall provide an action to set up radiative heat transfer problems where sidesets participating in the radiative exchange are external faces of the domain, with view factors computed by ray tracing.
Specification(s): external_boundary_ray_tracing
Design: Radiation Transfer Action
Collection(s): FUNCTIONAL
Type(s): Exodiff
- heat_conduction: Radiation Transfer Symmetry
- 5.29.1The system shall support the modeling of radiative heat transfer with symmetry boundary conditions by
- unfolding the problem at the symmetry boundary and
- 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_conduction: Radiative Bcs
- 5.30.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
- 5.30.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
- 5.30.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
- 5.30.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
- 5.30.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
- 5.30.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_conduction: Recover
- 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
Prerequisite(s): 5.31.1
- 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
Prerequisite(s): 5.31.2
- 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
Prerequisite(s): 5.31.4
- 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
Prerequisite(s): 5.31.5
- heat_conduction: Semiconductor Linear Conductivity
- 5.32.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_conduction: Sideset Heat Transfer
- 5.33.1The system shall solve the side set heat transfer model with:
- discontinuous finite elements,
- bulk gap temperature as an auxiliary variable,
- temperature dependent gap conductivity, and
- block restricted continuous finite element variables.
Specification(s): group/1D_gap, group/1D_gap_Tbulk_var, group/1D_gap_ktemp, group/CFEM_gap
Design: SideSetHeatTransferKernelSideSetHeatTransferMaterial
Issue(s): #14519
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.33.2The system shall throw an error if the specified boundary does not exist when using the DGDiffusion DGKernel.
Specification(s): 1D_gap_err
Design: SideSetHeatTransferKernelSideSetHeatTransferMaterial
Issue(s): #14519
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- heat_conduction: Transient Heat
- 5.34.1The system shall compute the time derivative term of the heat equation
Specification(s): test
Design: SpecificHeatConductionTimeDerivative
Issue(s): #7759
Collection(s): FUNCTIONAL
Type(s): Exodiff
- heat_conduction: Truss Heat Conduction
- 5.35.1The system shall model heat transfer in a bar and a strip made of two materials in series having differing thermal properties and provide equivalent solutions.
- using 1D truss elements.
- using 2D continuum elements in a 2D medium.
Specification(s): two_materials_in_domain/line, two_materials_in_domain/strip
Design: TrussHeatConductionTrussHeatConductionTimeDerivative
Issue(s): #19027
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.35.2The system shall model heat transfer in a bar/strip embedded in a medium having differing thermal properties from the bar/strip, and provide equivalent solutions.
- using 2D continuum elements for the bar contiguously meshed with a 2D medium.
- using 1D truss elements embedded in a 2D medium and connected using constraints.
- using 3D continuum elements for the bar contiguously meshed with a 3D medium.
- using 1D truss elements embedded in a 3D medium and connected using constraints.
Specification(s): w_and_wo_embedded_case/rectangle_with_strip, w_and_wo_embedded_case/rectangle_with_line, w_and_wo_embedded_case/block_with_bar, w_and_wo_embedded_case/block_with_line
Design: TrussHeatConductionTrussHeatConductionTimeDerivative
Issue(s): #19027
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.35.3The system shall generate comparison plots of the thermal solutions for a bar embedded in a continuum represented various ways.
Specification(s): plotting
Design: TrussHeatConductionTrussHeatConductionTimeDerivative
Issue(s): #19027
Collection(s): FUNCTIONAL
Type(s): RunCommand
- heat_conduction: Verify Against Analytical
- 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
- 5.36.2Heat conduction from an AD kernel shall get the same answer as a traditional kernel in 1D
Specification(s): ad_1D_transient
Design: HeatConduction
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.36.3AD heat conduction and the Jacobian shall be beautiful in 1D
Specification(s): ad_1D_transient_jacobian
Design: HeatConduction
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
- 5.36.5Heat conduction from an AD kernel shall get the same answer as a traditional kernel in 2D
Specification(s): ad_2D_steady_state
Design: HeatConduction
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 5.36.6AD heat conduction and the Jacobian shall be beautiful in 2D
Specification(s): ad_2D_steady_state_jacobian
Design: HeatConduction
Collection(s): FUNCTIONAL
Type(s): PetscJacobianTester
- heat_conduction: View Factors
- 5.37.1The system shall compute view factors for unobstructed, planar surfaces without normalization.
Specification(s): unnormalized
Design: UnobstructedPlanarViewFactor
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.37.2The system shall compute view factors for cavities with obstruction using ray tracing.
Specification(s): obstructed
Design: RayTracingViewFactor
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.37.3The system shall compute view factors for unobstructed, planar surfaces in two-dimensional meshes using simple quadrature rules.
Specification(s): analytical2D
Design: UnobstructedPlanarViewFactor
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
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.37.5The system shall compute view factors for unobstructed, planar surfaces in three-dimensional meshes using simple quadrature rules.
Specification(s): analytical3D
Design: UnobstructedPlanarViewFactor
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
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- heat_conduction: View Factors Symmetry
- 5.38.1The system shall support ensure that symmetry boundary conditions provide exactly the same answer as unfolding the problem about its axis of symmetry.
Specification(s): cavity_with_pillars
Design: Radiation Transfer ActionViewFactorRayBC
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 5.38.2The system shall support symmetry boundary conditions for view factor calculations.
Specification(s): cavity_with_pillars_symmetry_bc
Design: Radiation Transfer ActionViewFactorRayBC
Collection(s): FUNCTIONAL
Type(s): CSVDiff