Thermal Hydraulics System Design Description

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

commentnote

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

Introduction

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

System Purpose

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

System Scope

The MOOSE Thermal Hydraulics module provides several additional systems, including a component system, a closures system, and a control logic system. The module includes basic components such as two-dimensional and three-dimensional heat structures, which solve the transient heat conduction equation, along with components that provide heat sources, boundary conditions, and interface conditions to these components. The module also includes a suite of components for solving single-phase flow, using numerical methods most suitable for compressible gas flows. These single-phase flow components include flow channels, junctions, valves, walls, and inlets/outlets. Additionally, the module provides turbomachinery components such as a shaft, motor, compressor, and turbine. In addition to components, the module provides basic closures for the single-phase flow model, as well as control logic objects such as delays, trips, and PID controllers.

Dependencies and Limitations

The Thermal Hydraulics module inherits the software dependencies of the MOOSE framework, with no additional dependencies. The design of this module is motivated by the needs of its client applications.

Definitions and Acronyms

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

Definitions

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

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

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

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

Acronyms

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

Design Stakeholders and Concerns

Design Stakeholders

Stakeholders for MOOSE include several of the funding sources including Department of Energy, Nuclear Energy (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, Thermal Hydraulics module development requires either regression or unit testing for all new code added to the repository. The project contains several comparisons against analytical solutions where possible and also other verification methods such as MMS. For stability, the Thermal Hydraulics module (located within the MOOSE repository) maintains multiple branches to incorporate several layers of testing both internally and for dependent applications. Finally, performance tests are also performed as part of the the normal testing suite to monitor code change impacts to performance.

System Design

The Thermal Hydraulics module inherits the wide range of pluggable systems from MOOSE. More information regarding MOOSE system design can be found in the framework System Design section. Documentation for each object, data structure, and process specific to the module are kept up-to-date alongside the MOOSE documentation. Expected failure modes and error conditions are accounted for via regression testing, and error conditions are noted in object documentation where applicable.

System Structure

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

AuxKernels

AuxScalarKernels

AuxVariables

BCs

Closures

Components

Constraints

ControlLogic

CoupledHeatTransfers

DGKernels

Debug

FluidProperties

Functions

HeatStructureMaterials

ICs

Kernels

Materials

Mesh

Modules

Modules/FluidProperties

Outputs

Postprocessors

Problem

ScalarKernels

UserObjects

Variables

VectorPostprocessors

The MooseApp is the top-level object used to hold all of the other objects in a simulation. In a normal simulation a single MooseApp object is created and "run()". This object uses its Factory objects to build user-defined objects which are stored in a series of Warehouse objects and executed. The Finite Element 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 MOOSE website, and those for the Thermal Hydraulics module are on this webpage, accessible through the high-level system links above. Each of these systems has a set of defined polymorphic interfaces and are designed to accomplish a specific task within the simulation. The design of these systems is solid and is managed through agile methods and ticket request system either on GitHub (for MOOSE) or on the defined software repository for this application.

Data Design and Control

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

Human-Machine Interface Design

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

System Design Interface

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

Security Structure

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

Requirements Cross-Reference

  • thermal_hydraulics: MachNumberAux
  • 11.2.2The system shall be able to compute the Mach number for 1D single phase flow.

    Specification(s): test

    Design: MachNumberAux

    Issue(s): #12123

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: PrandtlNumberAux
  • 11.2.3The system shall be able to compute the local Prandtl number in a 1D single phase channel.

    Specification(s): test

    Design: PrandtlNumberAux

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: ReynoldsNumberAux
  • 11.2.4The system shall be able to compute the local Reynolds number in a 1D single phase channel.

    Specification(s): 1phase

    Design: ReynoldsNumberAux

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: SoundSpeedAux
  • 11.2.5The system shall be able to compute the local sound of speed in the fluid in a 1D single phase channel.

    Specification(s): test

    Design: SoundSpeedAux

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: SumAux
  • 11.2.6The system shall be able to compute the sum of two fields.

    Specification(s): sum

    Design: SumAux

    Issue(s): #19679

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: ComponentGroup
  • 11.3.1The system shall allow nesting components into groups in input files

    Specification(s): test

    Design: ComponentGroup

    Issue(s): #94

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • thermal_hydraulics: Closures1PhaseTHM
  • 11.4.1The system shall compute the heat transfer coefficient and the friction factor when used with:
    1. the Dittus-Boelter correlation for the Heat Transfer Coefficient and the Churchill or Cheng-Todreas correlation for the friction factor
    2. the Kazimi-Carelli correlation for the Heat Transfer Coefficient and the Churchill or Cheng-Todreas correlation for the friction factor
    3. the Lyon correlation for the Heat Transfer Coefficient and the Churchill or Cheng-Todreas correlation for the friction factor
    4. the Mikityuk correlation for the Heat Transfer Coefficient and the Churchill or Cheng-Todreas correlation for the friction factor
    5. the Schad correlation for the Heat Transfer Coefficient and the Churchill or Cheng-Todreas correlation for the friction factor
    6. the Weisman correlation for the Heat Transfer Coefficient and the Churchill or Cheng-Todreas correlation for the friction factor
    7. the Wolf-McCarthy correlation for the Heat Transfer Coefficient and the Churchill or Cheng-Todreas correlation for the friction factor
    8. the Gnielinski correlation for the Heat Transfer Coefficient and the Churchill or Cheng-Todreas correlation for the friction factor
    9. the friction factor is prescribed by the user

    Specification(s): tests/dittus_boelter_churchill, tests/kazimi_cheng, tests/lyon, tests/mikityuk, tests/schad, tests/weisman, tests/wolf, tests/gnielinski, tests/overwriten_f

    Design: Closures1PhaseTHM

    Issue(s): #19909

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: Closures1PhaseNone
  • 11.4.2The system shall be able to define a closure object that does not define closures, so they can be defined directly in the input file.

    Specification(s): phy:

    Design: Closures1PhaseNone

    Issue(s): #19779

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.4.3The system shall report an error with a useful message if the user attempts the former way of not specifying closures.

    Specification(s): enumeration_option

    Design: Closures1PhaseNone

    Issue(s): #19779

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: Components System
  • 11.5.1The system shall report an error if a component specified in a parameter does not exist.

    Specification(s): err:nonexisting_component

    Design: Components System

    Issue(s): #19749

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 11.5.2The system shall report an error if the components are not setup in the expected order and are not in the correct setup status for an operation.

    Specification(s): err:setup_status

    Design: Components System

    Issue(s): #19749

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 11.5.19The system shall report an error if a non-existent component is specified in a flow connection component.

    Specification(s): err:connecting_to_non_existent_component

    Design: Components System

    Issue(s): #26336

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 11.5.20The system shall report an error if the old syntax for component connections is being used in an input file.

    Specification(s): err:old_connection_format

    Design: Components System

    Issue(s): #26336

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 11.5.21The system shall report an error if an incorrect syntax is used for an inlet or outlet of a component to be connected.

    Specification(s): err:incorrect_connection_format

    Design: Components System

    Issue(s): #26336

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: FreeBoundary
  • 11.5.3The system shall report an error if the FreeBoundary component is used.

    Specification(s): free_boundary

    Design: FreeBoundary

    Issue(s): #20383

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: GateValve
  • 11.5.4The system shall report an error if the GateValve component is used.

    Specification(s): gate_valve

    Design: GateValve

    Issue(s): #20383

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: SolidWall
  • 11.5.5The system shall report an error if the SolidWall component is used.

    Specification(s): solid_wall

    Design: SolidWall

    Issue(s): #20383

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: HeatGeneration
  • 11.5.7The system shall report an error if the HeatGeneration component is used.

    Specification(s): heat_generation

    Design: HeatGeneration

    Issue(s): #20383

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: FileMeshComponent
  • 11.5.11The system shall generate a mesh for the FileMeshComponent test.

    Specification(s): mesh

    Design: FileMeshComponent

    Issue(s): #22354

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 11.5.12The system shall provide a component that loads a mesh from an ExodusII file.

    Specification(s): test

    Design: FileMeshComponent

    Issue(s): #22354

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.5.13The system shall report an error for FileMeshComponent when the file is not readable.

    Specification(s): file_not_readable

    Design: FileMeshComponent

    Issue(s): #22354

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: FreeBoundary1Phase
  • 11.5.24The system shall be able to specify a free surface boundary at the inlet and outlet and show conservation of mass.

    Specification(s): phy:mass_1phase

    Design: FreeBoundary1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.25The system shall be able to specify a free surface boundary at the inlet and outlet and show conservation of momentum.

    Specification(s): phy:momentum_1phase

    Design: FreeBoundary1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.26The system shall be able to specify a free surface boundary at the inlet and outlet and show conservation of energy.

    Specification(s): phy:energy_1phase

    Design: FreeBoundary1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: GateValve1Phase
  • 11.5.27The system shall be able to simulate a gate valve in between two components for a full transient.

    Specification(s): 1phase_heavy

    Design: GateValve1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.5.28The system shall be able to simulate a gate valve in between two components for a few time steps.

    Specification(s): 1phase_light

    Design: GateValve1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.5.29The system shall be able to simulate a gate valve in between two components with the component oriented in either direction.

    Specification(s): 1phase_light_flipped

    Design: GateValve1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.5.30The system shall report an error if a gate valve is connected to more than two components.

    Specification(s): err:not_2_connections

    Design: GateValve1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 11.5.31The system shall report an error if the two components connected to a gate valve are not parallel.

    Specification(s): err:not_parallel

    Design: GateValve1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 11.5.32The system shall report an error if a gate valve is requested to perform slope reconstruction.

    Specification(s): warn:slope_reconstruction_used

    Design: GateValve1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: Quadrature System
  • 11.5.33The system shall report an error if a TRAP quadrature is used with second order components.

    Specification(s): err:2nd_order

    Design: Quadrature System

    Issue(s): #26336

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: HeatSourceFromTotalPower
  • 11.5.38The system shall provide the heat source shape for a cylindrical heat structure when power component and power shape function are supplied

    Specification(s): phy:power_component_shape_cylindrical

    Design: HeatSourceFromTotalPower

    Issue(s): #19679

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.5.39The system shall provide the heat source shape for a plate heat structure when power component and power shape function are supplied

    Specification(s): phy:power_component_shape_plate

    Design: HeatSourceFromTotalPower

    Issue(s): #19679

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.5.40The system shall be able to impose a heat source from the component, computed from the component power and shape shape, onto a plate heat structure component and prove conservation of energy.

    Specification(s): phy:conservation_plate

    Design: HeatSourceFromTotalPower

    Issue(s): #19679

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.41The system shall be able to impose a heat source from the component, computed from the component power and shape shape, onto a cylindrical heat structure component and prove conservation of energy.

    Specification(s): phy:conservation_cylinder

    Design: HeatSourceFromTotalPower

    Issue(s): #19679

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.42The system shall be able to apply a heat source, computed from the component power norm and shape, onto a component whose mesh is loaded from a mesh file.

    Specification(s): phy:conservation_from_file_3d

    Design: HeatSourceFromTotalPower

    Issue(s): #19679

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.43The system shall report an error if the heat structure to apply a heat source on, computed from the component power norm and shape, is not of the expected heat structure interface type.

    Specification(s): err:no_hs

    Design: HeatSourceFromTotalPower

    Issue(s): #19679

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 11.5.44The system shall report an error if the specified subdomain to apply a heat source on, computed from the component power norm and shape, does not exist.

    Specification(s): err:wrong_block_name

    Design: HeatSourceFromTotalPower

    Issue(s): #19679

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 11.5.45The system shall report an error if the heat structure to apply a heat source on, computed from the component power norm and shape, is not of the expected type.

    Specification(s): err:wrong_power_comp

    Design: HeatSourceFromTotalPower

    Issue(s): #19679

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: HeatStructureFromFile3D
  • 11.5.63The system shall be able to use an external mesh file to create a 3D heat structure.

    Specification(s): phy:standalone

    Design: HeatStructureFromFile3D

    Issue(s): #19831

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.5.64The system shall report an error if the mesh from an external mesh file for a 3D heat structure is not 3D.

    Specification(s): err:2d_mesh

    Design: HeatStructureFromFile3D

    Issue(s): #19831

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 11.11.10The system shall be able to produce an exodus file for setting initial conditions in 3D heat structures

    Specification(s): steady_state

    Design: HeatStructureFromFile3D

    Issue(s): #20553

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.11.11The system shall be able to use an exodus file for setting initial conditions in 3D heat structures

    Specification(s): test

    Design: HeatStructureFromFile3DSolutionIC

    Issue(s): #20553

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • thermal_hydraulics: HSBoundaryHeatFlux
  • 11.5.120The system shall be able to apply a heat flux boundary condition on the boundary of a cylindrical heat structure and show conservation of energy.

    Specification(s): energy_conservation_cylindrical

    Design: HSBoundaryHeatFlux

    Issue(s): #19711

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.121The system shall be able to apply a heat flux boundary condition on the boundary of a plate heat structure and show conservation of energy.

    Specification(s): energy_conservation_plate

    Design: HSBoundaryHeatFlux

    Issue(s): #19711

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.122The system shall be able to apply a heat flux boundary condition on the boundary of a heat structure created from a 3D mesh file and show conservation of energy.

    Specification(s): energy_conservation_from_file_3d

    Design: HSBoundaryHeatFlux

    Issue(s): #19711

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: HSBoundaryRadiation
  • 11.5.123The system shall be able to apply a radiative heat flux boundary condition on the boundary of a cylindrical heat structure and show conservation of energy.

    Specification(s): energy_conservation_cylindrical

    Design: HSBoundaryRadiation

    Issue(s): #19778

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.124The system shall be able to apply a radiative heat flux boundary condition on the boundary of a plate heat structure and show conservation of energy.

    Specification(s): energy_conservation_plate

    Design: HSBoundaryRadiation

    Issue(s): #19778

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.125The system shall be able to apply a radiative heat flux boundary condition on the boundary of a heat structure created from a 3D mesh file and show conservation of energy.

    Specification(s): energy_conservation_from_file_3d

    Design: HSBoundaryRadiation

    Issue(s): #19778

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: Outlet1Phase
  • 11.5.163The system shall be able to model an outlet connected to a sealed pipe with 1D single phase compressible flow.

    Specification(s): phy:solidwall_outlet_3eqn

    Design: Outlet1Phase

    Issue(s): #26336#19722

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.5.164The system shall be able to control the pressure at a pressure outlet dynamically during a 1D single phase flow simulation.

    Specification(s): clg:ctrl_p_3eqn

    Design: Outlet1Phase

    Issue(s): #26336#19722

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.165The system shall be able to compute numerically accurate Jacobians for 1D single phase flow with a pressure outlet.

    Specification(s): jacobian

    Design: Outlet1Phase

    Issue(s): #26336#19722

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • thermal_hydraulics: Pump1Phase
  • 11.5.168The system shall be able to model a pump in 1D single phase flow and show conservation of mass and energy.

    Specification(s): phy:pump_mass_energy_conservation

    Design: Pump1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.169The system shall be able to model a pump in 1D single phase flow within a slanted pipe and show conservation of mass and energy.

    Specification(s): phy:pump_mass_energy_conservation_orientation

    Design: Pump1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.170The system shall be able to compute the expected pressure rise when modeling a pump in 1D single phase flow.

    Specification(s): phy:pressure_check

    Design: Pump1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.171The system shall be able to compute the expected pressure rise when modeling a pump in 1D single phase flow with an orientation not aligned with one of the frame axis.

    Specification(s): phy:pressure_check_orientation

    Design: Pump1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.172The system shall be able to compute the expected pressure rise when modeling a pump in 1D single phase flow with the flow aligned with the X axis.

    Specification(s): phy:pipe_friction_pump_head_balance_x_direction

    Design: Pump1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.5.173The system shall be able to compute the expected pressure rise when modeling a pump in 1D single phase flow with the flow aligned with the Y axis.

    Specification(s): phy:pipe_friction_pump_head_balance_y_direction

    Design: Pump1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.5.174The system shall be able to model a pump in a 1D single phase flow loop.

    Specification(s): phy:pump_loop

    Design: Pump1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.5.175The system shall allow for controlling the pump head

    Specification(s): clg:head

    Design: Pump1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.176The system shall allow for controlling the pump head and maintain a numerically correct Jacobian.

    Specification(s): jacobian

    Design: Pump1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • thermal_hydraulics: Shaft
  • 11.5.177The system shall report an error if a shaft is created with no connected components.

    Specification(s): err:no_connected_components

    Design: Shaft

    Issue(s): #26336

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 11.11.16The system shall be able to produce an exodus file for setting initial conditions in shaft

    Specification(s): steady_state

    Design: Shaft

    Issue(s): #20553

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.11.17The system shall be able to use an exodus file for setting initial conditions in shaft

    Specification(s): test

    Design: ShaftScalarSolutionIC

    Issue(s): #20553

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: SimpleTurbine1Phase
  • 11.5.199The system shall be able to model a simple turbine in 1D single phase compressible flow and show mass and energy conservation.

    Specification(s): phy:conservation

    Design: SimpleTurbine1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.200The system shall be able to model a simple turbine in 1D single phase compressible flow.

    Specification(s): phy:test

    Design: SimpleTurbine1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.5.201The system shall be able to control the turbine power in a 1D single phase compressible flow simulation with a simple turbine.

    Specification(s): clg:test

    Design: SimpleTurbine1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.202The system shall be able to compute a numerically accurate Jacobian when using a simple turbine model in a 1D single phase compressible flow simulation.

    Specification(s): jacobian

    Design: SimpleTurbine1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • thermal_hydraulics: SolidWall1Phase
  • 11.5.203The system shall be able to model a wall in a 1D single phase compressible flow simulation.

    Specification(s): phy:3eqn

    Design: SolidWall1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.5.204The system shall be able to compute a numerically accurate Jacobian when using a wall inlet (with no flow) in a 1D single phase compressible flow simulation.

    Specification(s): jacobian

    Design: SolidWall1Phase

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • thermal_hydraulics: TotalPower
  • 11.5.206The system shall be able to apply a heat source in a heat structure component.

    Specification(s): phy:constant_power

    Design: TotalPower

    Issue(s): #19762

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.5.207The system shall be able to dynamically control the heat source in a heat structure component.

    Specification(s): clg:power

    Design: TotalPower

    Issue(s): #19762

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: DelayControl
  • 11.6.2The system shall be able to delay a control signal in time.

    Specification(s): test

    Design: DelayControl

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.6.3The system shall report an error if the delay for the action of a control is set by the user to be negative.

    Specification(s): err.negative_tau

    Design: DelayControl

    Issue(s): #26336

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: ControlLogic System
  • 11.6.4The system shall use dependency resolution to execute Control objects in the correct order.

    Specification(s): test

    Design: ControlLogic System

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.6.5The system shall report an error if non-existent control data is requested in a control logic object.

    Specification(s): non_existent_control_data

    Design: ControlLogic System

    Issue(s): #26336

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: PIDControl
  • 11.6.8The system shall be able to use a proportional-integral-derivative law to adjust controllable flow parameters to be able to match a desired target quantity.

    Specification(s): test

    Design: PIDControl

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: SetBoolValueControl
  • 11.6.9The system shall be able to set a boolean parameter to the value of a boolean control data.

    Specification(s): test

    Design: SetBoolValueControl

    Issue(s): #19850

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: SetRealValueControl
  • 11.6.12The system shall be able to set a floating point parameter to the value of a floating point control data.

    Specification(s): test

    Design: SetRealValueControl

    Issue(s): #19850

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: SmootherControl
  • 11.6.13The system shall be able to smooth an input signal using a moving average.

    Specification(s): test

    Design: SmootherControl

    Issue(s): #27831

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: TerminateControl
  • 11.6.14The system shall be able to use control logic to terminate a simulation gracefully.

    Specification(s): no_error

    Design: TerminateControl

    Issue(s): #19679

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 11.6.15The system shall be able to use control logic to terminate a simulation with an error.

    Specification(s): throw_error

    Design: TerminateControl

    Issue(s): #19679

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: Controls System
  • 11.6.17The system shall be able to execute controls at the beginning of simulation time steps.

    Specification(s): test

    Design: Controls System

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: UnitTripControl
  • 11.6.18The system shall provide a unit trip component that report true if the trip condition was met and false otherwise.

    Specification(s): no_latch

    Design: UnitTripControl

    Issue(s): #619

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.6.19The system shall provide a unit trip component that stays in tripped state after the trip happened.

    Specification(s): latch

    Design: UnitTripControl

    Issue(s): #619

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.6.20The system shall report an error when an unit trip condition does not evaluate as boolean value.

    Specification(s): err:not_boolean

    Design: UnitTripControl

    Issue(s): #619

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: PiecewiseFunction
  • 11.7.1The system shall be able to piece together several functions in a given axis, directly from the input file.

    Specification(s): function_values

    Design: PiecewiseFunction

    Issue(s): #19765

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.7.2The system shall report an error if the the user passes an inconsistent number of functions to piece together and number of points of connections between the functions.

    Specification(s): error_inconsistent_number_of_points

    Design: PiecewiseFunction

    Issue(s): #19765

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 11.7.3The system shall report an error if the the user passes points of connections between functions to piece together that are not in increasing order.

    Specification(s): error_points_nonascending_order

    Design: PiecewiseFunction

    Issue(s): #19765

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 11.7.4The system shall report an error if the user references a function to piece functions together in the list of function pieced together, hence creating an infinite recursion.

    Specification(s): error_self_reference

    Design: PiecewiseFunction

    Issue(s): #19765

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: ConvectionHeatTransferBC
  • 11.9.1The system shall be able to compute numerically accurate Jacobians when specifying a convective heat transfer boundary condition.

    Specification(s): test

    Design: ConvectionHeatTransferBC

    Issue(s): #19679

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • thermal_hydraulics: ConvectionHeatTransferRZBC
  • 11.9.2The system shall be able to compute numerically accurate Jacobians when specifying a cylindrical convective heat transfer boundary condition in a cartesian frame of reference.

    Specification(s): test

    Design: ConvectionHeatTransferRZBC

    Issue(s): #19679

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • thermal_hydraulics: RadiativeHeatFluxBC
  • 11.9.5The system shall be able to compute numerically accurate Jacobians when specifying a radiative boundary condition.

    Specification(s): test

    Design: RadiativeHeatFluxBC

    Issue(s): #19778

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • thermal_hydraulics: RadiativeHeatFluxRZBC
  • 11.9.6The system shall be able to compute numerically accurate Jacobians when specifying a radiative boundary condition using cylindrical coordinates in a cartesian frame of reference.

    Specification(s): test

    Design: RadiativeHeatFluxRZBC

    Issue(s): #19778

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • thermal_hydraulics: OneD3EqnEnergyFlux
  • 11.9.11The system shall be able to compute numerically accurate Jacobians when computing the contribution from the energy advection term to the fluid energy equation.

    Specification(s): one_d_3eqn_energy_flux

    Design: OneD3EqnEnergyFlux

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • thermal_hydraulics: ADSolidMaterial
  • 11.9.16The system shall be able to use the material property system to define solid properties for a solid energy equation.

    Specification(s): ad_solid_material

    Design: ADSolidMaterial

    Issue(s): #20662

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • thermal_hydraulics: ConstantMaterial
  • 11.9.17The system shall be able to compute a numerically accurate Jacobian when using a constant material to define a property and its (null) derivatives with regards to the nonlinear conserved variables.

    Specification(s): constant_material

    Design: ConstantMaterial

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • thermal_hydraulics: MaterialDerivativeTestKernel
  • 11.9.18The system shall be able to compute a numerically accurate Jacobian when computing density as a fluid property and its derivatives with regards to the nonlinear conserved variables.

    Specification(s): density_3eqn_material

    Design: MaterialDerivativeTestKernel

    Issue(s): #19747

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 11.9.21The system shall be able to compute a numerically accurate Jacobian when computing pressure as a fluid property and its derivatives with regards to the nonlinear conserved variables.

    Specification(s): pressure_3eqn_material

    Design: MaterialDerivativeTestKernel

    Issue(s): #19747

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 11.9.22The system shall be able to compute a numerically accurate Jacobian when computing specific internal energy as a fluid property and its derivatives with regards to the nonlinear conserved variables.

    Specification(s): specific_internal_energy_3eqn

    Design: MaterialDerivativeTestKernel

    Issue(s): #19747

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 11.9.23The system shall be able to compute a numerically accurate Jacobian when computing specific volume as a fluid property and its derivatives with regards to the nonlinear conserved variables.

    Specification(s): specific_volume_3eqn

    Design: MaterialDerivativeTestKernel

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 11.9.24The system shall be able to compute a numerically accurate Jacobian when computing velocity as a fluid property and its derivatives with regards to the nonlinear conserved variables.

    Specification(s): velocity_3eqn

    Design: MaterialDerivativeTestKernel

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 11.9.25The system shall be able to compute a numerically accurate Jacobian when computing specific enthalpy as a fluid property and its derivatives with regards to the nonlinear conserved variables.

    Specification(s): enthalpy_3eqn

    Design: MaterialDerivativeTestKernel

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 11.9.27The system shall be able to compute a numerically accurate Jacobian when computing temperature as a fluid property and its derivatives with regards to the nonlinear conserved variables.

    Specification(s): temperature_3eqn_material

    Design: MaterialDerivativeTestKernel

    Issue(s): #19747

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 11.9.28The system shall be able to compute a numerically accurate Jacobian when computing total enthalpy as a fluid property and its derivatives with regards to the nonlinear conserved variables.

    Specification(s): total_enthalpy_3eqn

    Design: MaterialDerivativeTestKernel

    Issue(s): #19747

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • thermal_hydraulics: DynamicViscosityMaterial
  • 11.9.19The system shall be able to compute a numerically accurate Jacobiain when computing the dynamic viscosity and its derivatives with regards to the nonlinear conserved variables.

    Specification(s): dynamic_viscosity

    Design: DynamicViscosityMaterial

    Issue(s): #26411

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • thermal_hydraulics: Materials System
  • 11.9.20The system shall be able to compute a numerically accurate Jacobian when computing the constant derivatives of material properties linearly dependent on the nonlinear conserved variables.

    Specification(s): linear_test_material

    Design: Materials System

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • thermal_hydraulics: ReynoldsNumberMaterial
  • 11.9.26The system shall be able to compute a numerically accurate Jacobian when computing the Reynolds number and its derivatives with regards to the nonlinear conserved variables.

    Specification(s): reynolds_number

    Design: ReynoldsNumberMaterial

    Issue(s): #26411

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 11.10.32The system shall be able to compute the Reynolds number as a material property.

    Specification(s): test

    Design: ReynoldsNumberMaterial

    Issue(s): #26411

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: ADConvectionHeatFluxMaterial
  • 11.10.5The system shall be able to compute the convective heat flux and store it as a material property to be able to propagate derivatives through automatic differentiation.

    Specification(s): test

    Design: ADConvectionHeatFluxMaterial

    Issue(s): #26411

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: ADConvectionHeatFluxHSMaterial
  • 11.10.6The system shall be able to compute the convective heat flux in a heat structure and store it as a material property to be able to propagate derivatives through automatic differentiation.

    Specification(s): test

    Design: ADConvectionHeatFluxHSMaterial

    Issue(s): #26411

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: Adaptivity System
  • 11.11.1The system shall be able to use adaptive mesh refinement in a 1D single phase compressible flow simulation.

    Specification(s): single_block

    Design: Adaptivity System

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • thermal_hydraulics: SolutionIC
  • 11.11.6The system shall be able to use an exodus file for setting initial conditions in flow channels

    Specification(s): test

    Design: FlowChannel1PhaseSolutionIC

    Issue(s): #20553

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.11.7The system shall report an error when a block is non found in the restart ExodusII file

    Specification(s): non_existent_block

    Design: SolutionIC

    Issue(s): #20526

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 11.11.9The system shall be able to use an exodus file for setting initial conditions in heat structures

    Specification(s): test

    Design: Heat StructuresSolutionIC

    Issue(s): #20465

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.11.11The system shall be able to use an exodus file for setting initial conditions in 3D heat structures

    Specification(s): test

    Design: HeatStructureFromFile3DSolutionIC

    Issue(s): #20553

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.11.13The system shall be able to use an exodus file for setting initial conditions in a heat structure and a connected flow channel.

    Specification(s): test

    Design: HeatTransferFromHeatStructure1PhaseSolutionIC

    Issue(s): #20553

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.11.15The system shall be able to use an exodus file for setting initial conditions in heat transfer from 3D heat structures

    Specification(s): test

    Design: HeatTransferFromHeatStructure3D1PhaseSolutionIC

    Issue(s): #20553

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • thermal_hydraulics: Heat Structures
  • 11.11.8The system shall be able to produce an exodus file for setting initial conditions in heat structures

    Specification(s): steady_state

    Design: Heat Structures

    Issue(s): #20465

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.11.9The system shall be able to use an exodus file for setting initial conditions in heat structures

    Specification(s): test

    Design: Heat StructuresSolutionIC

    Issue(s): #20465

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • thermal_hydraulics: ScalarSolutionIC
  • 11.11.17The system shall be able to use an exodus file for setting initial conditions in shaft

    Specification(s): test

    Design: ShaftScalarSolutionIC

    Issue(s): #20553

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: Flow Junctions
  • 11.11.18The system shall be able to produce an exodus file for setting initial conditions in volume junctions

    Specification(s): steady_state

    Design: Flow Junctions

    Issue(s): #20553

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.11.19The system shall be able to use an exodus file for setting initial conditions in volume junctions

    Specification(s): test

    Design: Flow Junctions

    Issue(s): #20553

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.11.20The system shall report an error if one tries to use an exodus file for setting initial conditions in a volume junction, with parallel threads.

    Specification(s): parallel_threading_error

    Design: Flow Junctions

    Issue(s): #28670

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: Mesh System
  • 11.11.21The system shall be able to only output the components' mesh and avoid running the rest of the simulation.

    Specification(s): test

    Design: Mesh System

    Issue(s): #19836

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • thermal_hydraulics: Restart and Recover
  • 11.11.22The system shall be able to create a checkpoint for restarting a single phase compressible flow simulation.

    Specification(s): part1

    Design: Restart and Recover

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.11.23The system shall be able to restart from a checkpoint in a single phase compressible flow simulation.

    Specification(s): part2

    Design: Restart and Recover

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.11.24The system shall be able to restart from a checkpoint in a single phase compressible flow simulation, and override some of the restarted values with initial conditions.

    Specification(s): part2_ics

    Design: Restart and Recover

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • thermal_hydraulics: SolutionUserObject
  • 11.11.25The system shall be able to generate a power profile in an Exodus file to be read from a 1D flow simulation.

    Specification(s): power_profile

    Design: SolutionUserObject

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 11.11.26The system shall be able to read a power profile from an Exodus file to apply on components in a 1D single phase compressible flow simulation.

    Specification(s): surrogate_power_profile

    Design: SolutionUserObject

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • thermal_hydraulics: THMSetupOutputAction
  • 11.12.1The system shall be able to disable the output of scalar variables to the console.

    Specification(s): disable

    Design: THMSetupOutputAction

    Issue(s): #23498

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 11.12.2The system shall be able to allow the output of scalar variables to the console.

    Specification(s): allow

    Design: THMSetupOutputAction

    Issue(s): #23498

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • thermal_hydraulics: ADFlowBoundaryFlux1Phase
  • 11.13.2The system shall be able to compute a component of the flux vector at a boundary in 1D single phase compressible flow simulations.

    Specification(s): test

    Design: ADFlowBoundaryFlux1Phase

    Issue(s): #19812

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: ADFlowJunctionFlux1Phase
  • 11.13.3The system shall be able to compute a component of the flux vector at a junction in 1D single phase compressible flow simulations.

    Specification(s): test

    Design: ADFlowJunctionFlux1Phase

    Issue(s): #19809

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: RZSymmetry
  • 11.13.4The system should report an error when users set subdomain-restricted RZ-symmtrical THM-specific objects on RZ-subdomains.

    Specification(s): err:rz_domain

    Design: RZSymmetry

    Issue(s): #215

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 11.13.6The system should error out when users set boundary-restricted RZ-symmtrical THM-specific objects on RZ-subdomains.

    Specification(s): err:rz_domain

    Design: RZSymmetry

    Issue(s): #26336

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: FunctionSideIntegralRZ
  • 11.13.5The system shall be able to integrate the values of a function on a side, assuming cylindrical coordinates in a Cartesian frame of reference.

    Specification(s): test

    Design: FunctionSideIntegralRZ

    Issue(s): #26411

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: HeatRateConvection
  • 11.13.8The system shall be able to compute the convective heat flux rate on a boundary.

    Specification(s): test

    Design: HeatRateConvection

    Issue(s): #19897

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: HeatRateConvectionRZ
  • 11.13.10The system shall be able to compute the convective heat flux rate on a boundary in a single phase simulation, using cylindical coordinates in a Cartesian frame of reference.

    Specification(s): test

    Design: HeatRateConvectionRZ

    Issue(s): #26411

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: HeatRateExternalAppConvectionRZ
  • 11.13.11The system shall be able to compute the convective heat flux rate on a boundary in a single phase simulation, using cylindical coordinates in a Cartesian frame of reference, with an external temperature and a heat transfer coefficient computed by an external application.

    Specification(s): test

    Design: HeatRateExternalAppConvectionRZ

    Issue(s): #19816

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: HeatRateHeatFlux
  • 11.13.12The system shall compute the heat rate for a user-provided heat flux function.

    Specification(s): test

    Design: HeatRateHeatFlux

    Issue(s): #24261

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: HeatRateHeatFluxRZ
  • 11.13.13The system shall compute the heat rate for a user-provided heat flux function for a cylindrical boundary.

    Specification(s): test

    Design: HeatRateHeatFluxRZ

    Issue(s): #24261

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: HeatRateRadiation
  • 11.13.14The system shall be able to compute a radiative heat flux on a boundary.

    Specification(s): test

    Design: HeatRateRadiation

    Issue(s): #19897

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: HeatRateRadiationRZ
  • 11.13.15The system shall be able to compute a radiative heat flux on a boundary, using cylindrical coordinates in a Cartesian frame of reference.

    Specification(s): test

    Design: HeatRateRadiationRZ

    Issue(s): #26411

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: ADSideFluxIntegralRZ
  • 11.13.21The system shall be able to compute a diffusive flux on a boundary, using cylindrical coordinates in a Cartesian frame of reference.

    Specification(s): test

    Design: ADSideFluxIntegralRZ

    Issue(s): #19861

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: Brayton Cycle
  • 11.14.4The system shall be able to model an open Brayton cycle

    Specification(s): open

    Design: Brayton Cycle

    Issue(s): #20196

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.14.5The system shall be able to model a closed Brayton cycle

    Specification(s): closed

    Design: Brayton Cycle

    Issue(s): #20196

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.14.6The system shall be able to model an open recuperated Brayton cycle

    Specification(s): recuperated

    Design: Brayton Cycle

    Issue(s): #20196

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • thermal_hydraulics: LayeredAverageRZ
  • 11.16.2The system shall be able to compute layered averages along a boundary, using cylindrical coordinates in a Cartesian frame of reference.

    Specification(s): test

    Design: LayeredAverageRZ

    Issue(s): #26336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • thermal_hydraulics: Logger
  • 11.17.1The system shall be able to output warnings in a batch.

    Specification(s): warnings

    Design: Logger

    Issue(s): #19747#27064

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 11.17.2The system shall be able to output errors in a batch.

    Specification(s): errors

    Design: Logger

    Issue(s): #19747#27064

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: CubicTransition
  • 11.17.3The system shall be able to compute a smooth cubic transition between two functions of a variable.

    Specification(s): cubic_nonad

    Design: CubicTransition

    Issue(s): #26411

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.17.4The system shall be able to compute a smooth weighted transition between two functions of a variable.

    Specification(s): weighted_nonad

    Design: CubicTransition

    Issue(s): #26411

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.17.5The system shall be able to compute a numerically accurate Jacobian when performing a smooth cubic transition between two functions of a variable, showing that derivatives were computed accurately.

    Specification(s): cubic_derivative

    Design: CubicTransition

    Issue(s): #26411

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • thermal_hydraulics: WeightedTransition
  • 11.17.6The system shall be able to compute a numerically accurate Jacobian when performing a smooth weighted transition between two functions of a variable, showing that derivatives were computed accurately.

    Specification(s): weighted_derivative

    Design: WeightedTransition

    Issue(s): #26411

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 11.17.7The system shall be able to compute a smooth cubic transition between two functions of a variable and conserving derivatives with automatic differentiation.

    Specification(s): ad_cubic

    Design: WeightedTransition

    Issue(s): #26411

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.17.8The system shall be able to compute a smooth weighted transition between two functions of a variable and conserving derivatives with automatic differentiation.

    Specification(s): ad_weighted

    Design: WeightedTransition

    Issue(s): #26411

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: Sampler1DReal
  • 11.18.1The system shall provide a vector post-processor to sample regular material properties in one or more blocks.

    Specification(s): non_ad

    Design: Sampler1DReal

    Issue(s): #19819#20612

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • The system shall provide a vector post-processor to sample AD material properties in one or more blocks.

    Specification(s): ad

    Design: Sampler1DReal

    Issue(s): #19819#20612

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 11.18.3The system shall report an error if a non-existent material property is requested for the block material property sampler vector post-processor.

    Specification(s): error_on_nonexistent_matprop

    Design: Sampler1DReal

    Issue(s): #19819#20612

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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]