Fluid Properties System Design Description

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

note

This document serves as an addendum to Framework System Design Description and captures information for SDD specific to the Fluid Properties application.

Framework System Design Description

Introduction

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

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

A streamlined build system
An API aimed at extensible
Straightforward APIs providing sensible default information
Integrated, automatic, and rigorous testing
Rapid, continuous integration development cycle
Codified, rigorous path for contributing
Applications are modular and composable

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

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

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

Use Cases

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

System Purpose

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

System Scope

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

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

Dependencies and Limitations

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

Software Dependency	Description
libMesh	Finite Element Library and I/O routines
PETSc	Solver Package
hypre	Multigrid Preconditioner
MPI	A distributed parallel processing library (MPICH)

Figure 1: A diagram of the MOOSE code platform.

References

ISO/IEC/IEEE 24765:2010(E). Systems and software engineering—Vocabulary. first edition, December 15 2010.

@manual{ISO-systems-software,
    author = "24765:2010(E), ISO/IEC/IEEE",
    title = "Systems and software engineering---Vocabulary",
    edition = "First",
    year = "2010",
    month = "December 15"
}

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.

@manual{ASME-NQA-1-2008,
    author = "NQA-1, ASME",
    title = "ASME NQA-1-2008 with the NQA-1a-2009 addenda: Quality Assurance Requirements for Nuclear Facility Applications",
    orginization = "American Socieity of Mechanical Engineers",
    year = "2009",
    month = "August 31",
    edition = "First"
}

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

Acronym	Description
API	Application Programming Interface
DOE-NE	Department of Energy, Nuclear Energy
FE	finite element
FEM	Finite Element Method
GUI	graphical user interface
HIT	Hierarchical Input Text
HPC	High Performance Computing
I/O	Input/Output
INL	Idaho National Laboratory
MOOSE	Multiphysics Object Oriented Simulation Environment
MPI	Message Passing Interface
PDEs	partial differential equations
SDD	Software Design Description

Design Stakeholders and Concerns

Design Stakeholders

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

Stakeholder Design Concerns

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

System Design

The MOOSE framework itself is composed of a wide range of pluggable systems. Each system is generally composed of a single or small set of C++ objects intended to be specialized by a Developer to solve a specific problem. To accomplish this design goal, MOOSE uses several modern object-oriented design patterns. The primary overarching pattern is the "Factory Pattern". Users needing to extend MOOSE may inherit from one of MOOSE's systems to providing an implementation meeting his or her needs. The design of each of these systems is documented on the mooseframework.org wiki in the Tutorial section. Additionally, up-to-date documentation extracted from the source is maintained on the the mooseframework.org documentation site after every successful merge to MOOSE's stable branch. After these objects are created, the can be registered with the framework and used immediately in a MOOSE input file.

System Structure

The MOOSE framework architecture consists of a core and several pluggable systems. The core of MOOSE consists of a number of key objects responsible for setting up and managing the user-defined objects of a finite element simulation. This core set of objects has limited extendability and exist for every simulation configuration that the framework is capable of running.

Adaptivity

Adaptivity/Indicators

Adaptivity/Markers

AuxKernels

AuxKernels/MatVecRealGradAuxKernel

AuxKernels/MaterialVectorAuxKernel

AuxKernels/MaterialVectorGradAuxKernel

AuxScalarKernels

AuxVariables

AuxVariables/MultiAuxVariables

BCs

BCs/CavityPressure

BCs/CoupledPressure

BCs/InclinedNoDisplacementBC

BCs/Periodic

BCs/Pressure

Bounds

Closures

Components

Constraints

Contact

ControlLogic

Controls

CoupledHeatTransfers

Covariance

DGKernels

Dampers

Debug

Debug/MaterialDerivativeTest

DeprecatedBlock

DiracKernels

Distributions

DomainIntegral

Executioner

Executioner/Adaptivity

Executioner/Predictor

Executioner/Quadrature

Executioner/TimeIntegrator

Executioner/TimeStepper

Executors

FVBCs

FVInterfaceKernels

FVKernels

FluidPropertiesInterrogator

Functions

GeochemicalModelInterrogator

GlobalParams

GrayDiffuseRadiation

HeatStructureMaterials

ICs

ICs/PolycrystalICs

ICs/PolycrystalICs/BicrystalBoundingBoxIC

ICs/PolycrystalICs/BicrystalCircleGrainIC

ICs/PolycrystalICs/PolycrystalColoringIC

ICs/PolycrystalICs/PolycrystalRandomIC

ICs/PolycrystalICs/PolycrystalVoronoiVoidIC

ICs/PolycrystalICs/Tricrystal2CircleGrainsIC

InterfaceKernels

Kernels

Kernels/CHPFCRFFSplitKernel

Kernels/DynamicTensorMechanics

Kernels/HHPFCRFFSplitKernel

Kernels/PFCRFFKernel

Kernels/PolycrystalElasticDrivingForce

Kernels/PolycrystalKernel

Kernels/PolycrystalStoredEnergy

Kernels/PoroMechanics

Kernels/RigidBodyMultiKernel

Kernels/TensorMechanics

Materials

Mesh

Mesh/Partitioner

Modules

Modules/CompressibleNavierStokes

Modules/FluidProperties

Modules/HeatConduction

Modules/HeatConduction/ThermalContact

Modules/HeatConduction/ThermalContact/BC

Modules/IncompressibleNavierStokes

Modules/NavierStokesFV

Modules/Peridynamics

Modules/Peridynamics/Mechanics

Modules/Peridynamics/Mechanics/GeneralizedPlaneStrain

Modules/Peridynamics/Mechanics/Master

Modules/PhaseField

Modules/PhaseField/Conserved

Modules/PhaseField/DisplacementGradients

Modules/PhaseField/EulerAngles2RGB

Modules/PhaseField/GrainGrowth

Modules/PhaseField/GrandPotential

Modules/PhaseField/Nonconserved

Modules/PorousFlow

Modules/PorousFlow/BCs

Modules/TensorMechanics

Modules/TensorMechanics/CohesiveZoneMaster

Modules/TensorMechanics/DynamicMaster

Modules/TensorMechanics/GeneralizedPlaneStrain

Modules/TensorMechanics/GlobalStrain

Modules/TensorMechanics/LineElementMaster

Modules/TensorMechanics/Master

Modules/TensorMechanics/MaterialVectorBodyForce

MortarGapHeatTransfer

MultiApps

NodalKernels

NodalNormals

Outputs

PorousFlowBasicTHM

PorousFlowFullySaturated

PorousFlowUnsaturated

Postprocessors

Preconditioning

Problem

RayBCs

RayKernels

ReactionNetwork

ReactionNetwork/AqueousEquilibriumReactions

ReactionNetwork/SolidKineticReactions

Reporters

Samplers

ScalarKernels

SpatialReactionSolver

StochasticTools

Surrogates

ThermalContact

TimeDependentReactionSolver

TimeIndependentReactionSolver

Trainers

Transfers

UserObjects

Variables

Variables/CHPFCRFFSplitVariables

Variables/HHPFCRFFSplitVariables

Variables/PFCRFFVariables

Variables/PolycrystalVariables

VectorPostprocessors

XFEM

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

MOOSE's pluggable systems are documented on the mooseframework.org wiki. Each of these systems has set of defined polymorphic interfaces and are designed to accomplish a specific task within the simulation. The design of these systems is fluid and is managed through agile methods and ticket request system on the Github.org website.

Data Design and Control

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

Human-Machine Interface Design

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

System Design Interface

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

Security Structure

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

Requirements Cross-Reference

fluid_properties: SpecificEnthalpyAux
6.1.1The system shall compute specific enthalpy from pressure and temperature
Specification(s): specific_enthalpy_aux
Design: SpecificEnthalpyAux
Issue(s): #19225
Collection(s): FUNCTIONAL
Type(s): Exodiff
38

fluid_properties: StagnationPressureAux
6.1.2The system shall compute stagnation pressure from specific volume, specific internal energy, and velocit
Specification(s): stagnation_pressure_aux
Design: StagnationPressureAux
Issue(s): #19225
Collection(s): FUNCTIONAL
Type(s): Exodiff
38

fluid_properties: StagnationTemperatureAux
6.1.3The system shall compute stagnation temperature from specific volume, specific internal energy, and velocity
Specification(s): stagnation_temperature_aux
Design: StagnationTemperatureAux
Issue(s): #19225
Collection(s): FUNCTIONAL
Type(s): Exodiff
38

fluid_properties: FluidDensityAux
6.1.4The system shall compute fluid density from pressure and temperature.
Specification(s): fluid_density_aux
Design: FluidDensityAux
Issue(s): #17546
Collection(s): FUNCTIONAL
Type(s): Exodiff
38

fluid_properties: BrineFluidProperties
6.2.1The system shall compute properties of brine
Specification(s): brine
Design: BrineFluidProperties
Issue(s): #6972
Collection(s): FUNCTIONAL
Type(s): CSVDiff
38
6.2.2The system shall compute properties of brine using tabulated water properties
Specification(s): brine_tabulated
Design: BrineFluidProperties
Issue(s): #6972 #12812
Collection(s): FUNCTIONAL
Type(s): CSVDiff
38

fluid_properties: CaloricallyImperfectGas
6.3.1The system shall compute properties for a calorically imperfect but otherwise ideal gas
Specification(s): calorically_imperfect_gas
Design: CaloricallyImperfectGas
Issue(s): #20101
Collection(s): FUNCTIONAL
Type(s): Exodiff
38

fluid_properties: FluidPropertiesInterrogator
6.5.1The fluid properties interrogator shall output static-state fluid properties for (p, T) input.
Specification(s): 1ph.p_T
Design: FluidPropertiesInterrogator
Issue(s): #12995
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.2The fluid properties interrogator shall output static-state fluid properties for (p, T) input in JSON format.
Specification(s): 1ph.p_T.json
Design: FluidPropertiesInterrogator
Issue(s): #13741
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.3The fluid properties interrogator shall output static-state fluid properties for (rho, e) input.
Specification(s): 1ph.rho_e
Design: FluidPropertiesInterrogator
Issue(s): #12995
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.4The fluid properties interrogator shall output static-state fluid properties for (rho, e) input in JSON format.
Specification(s): 1ph.rho_e.json
Design: FluidPropertiesInterrogator
Issue(s): #13741
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.5The fluid properties interrogator shall output static-state fluid properties for (rho, p) input.
Specification(s): 1ph.rho_p
Design: FluidPropertiesInterrogator
Issue(s): #12995
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.6The fluid properties interrogator shall output static-state fluid properties for (rho, p) input in JSON format.
Specification(s): 1ph.rho_p.json
Design: FluidPropertiesInterrogator
Issue(s): #13741
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.7The fluid properties interrogator shall output static-state and stagnation-state fluid properties for (rho, rhou, rhoE) input with a single-phase fluid properties object.
Specification(s): 1ph.rho_rhou_rhoE
Design: FluidPropertiesInterrogator
Issue(s): #12995
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.8The fluid properties interrogator shall output static-state and stagnation-state fluid properties for (rho, rhou, rhoE) input with a single-phase fluid properties object in JSON format.
Specification(s): 1ph.rho_rhou_rhoE.json
Design: FluidPropertiesInterrogator
Issue(s): #13741
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.9The fluid properties interrogator shall output two-phase and static-state, single-phase fluid properties for (p, T) input with a two-phase fluid properties object.
Specification(s): 2ph.p_T
Design: FluidPropertiesInterrogator
Issue(s): #12995
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.10The fluid properties interrogator shall output two-phase and static-state, single-phase fluid properties for (p, T) input with a two-phase fluid properties object in JSON format.
Specification(s): 2ph.p_T.json
Design: FluidPropertiesInterrogator
Issue(s): #13741
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.11The fluid properties interrogator shall output two-phase and static-state, single-phase fluid properties for (p, T) input with a two-phase NCG fluid properties object.
Specification(s): 2ph_ncg_p_T
Design: FluidPropertiesInterrogator
Issue(s): #12995
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.12The fluid properties interrogator shall output two-phase and static-state, single-phase fluid properties for (p, T) input with a two-phase NCG fluid properties object in JSON format.
Specification(s): 2ph_ncg_p_T.json
Design: FluidPropertiesInterrogator
Issue(s): #13741
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.13The fluid properties interrogator shall output static-state, single-phase fluid properties for (rho, e) input with a vapor mixture fluid properties object.
Specification(s): vapor_mixture_rho_e
Design: FluidPropertiesInterrogator
Issue(s): #12995
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.14The fluid properties interrogator shall output static-state, single-phase fluid properties for (rho, e) input with a vapor mixture fluid properties object in JSON format.
Specification(s): vapor_mixture_rho_e.json
Design: FluidPropertiesInterrogator
Issue(s): #13741
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.15The fluid properties interrogator shall output two-phase fluid properties for (p) input with a two-phase fluid properties object.
Specification(s): 2ph_p
Design: FluidPropertiesInterrogator
Issue(s): #12995
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.16The fluid properties interrogator shall output two-phase fluid properties for (p) input with a two-phase fluid properties object in JSON format.
Specification(s): 2ph_p.json
Design: FluidPropertiesInterrogator
Issue(s): #13741
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.17The fluid properties interrogator shall output two-phase fluid properties for (T) input with a two-phase fluid properties object.
Specification(s): 2ph_T
Design: FluidPropertiesInterrogator
Issue(s): #12995
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.18The fluid properties interrogator shall output two-phase fluid properties for (T) input with a two-phase fluid properties object in JSON format.
Specification(s): 2ph_T.json
Design: FluidPropertiesInterrogator
Issue(s): #13741
Collection(s): FUNCTIONAL
Type(s): RunApp
30
6.5.19The fluid properties interrogator shall throw an error if an incompatible fluid properties object is supplied.
Specification(s): err.wrong_fp_type
Design: FluidPropertiesInterrogator
Issue(s): #12995
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
30
6.5.20The fluid properties interrogator shall throw an error if an extraneous parameter(s) are supplied.
Specification(s): err.extraneous_parameter
Design: FluidPropertiesInterrogator
Issue(s): #12995
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
30
6.5.21The fluid properties interrogator shall throw an error if an no valid input sets were supplied.
Specification(s): err.no_params
Design: FluidPropertiesInterrogator
Issue(s): #12995
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
30

fluid_properties: SaturationPressureFunction
6.6.1The system shall provide a function that computes saturation pressure from a temperature function
Specification(s): test
Design: SaturationPressureFunction
Issue(s): #14755
Collection(s): FUNCTIONAL
Type(s): CSVDiff
38

fluid_properties: SaturationTemperatureFunction
6.6.2The system shall provide a function that computes saturation temperature from a pressure function
Specification(s): test
Design: SaturationTemperatureFunction
Issue(s): #14755
Collection(s): FUNCTIONAL
Type(s): CSVDiff
38

fluid_properties: RhoFromPressureTemperatureIC
6.7.1The system shall be able to set an initial condition for density given pressure and temperature as variables
Specification(s): test
Design: RhoFromPressureTemperatureIC
Issue(s): #15524
Collection(s): FUNCTIONAL
Type(s): CSVDiff
38

fluid_properties: RhoVaporMixtureFromPressureTemperatureIC
6.7.2The system shall be able to set an initial condition for density of vapor mixture given pressure and temperature as variables
Specification(s): test
Design: RhoVaporMixtureFromPressureTemperatureIC
Issue(s): #15524
Collection(s): FUNCTIONAL
Type(s): CSVDiff
38

fluid_properties: SpecificEnthalpyFromPressureTemperatureIC
6.7.3The system shall be able to set an initial condition for specific enthalpy given pressure and temperature as variables
Specification(s): test
Design: SpecificEnthalpyFromPressureTemperatureIC
Issue(s): #15561
Collection(s): FUNCTIONAL
Type(s): CSVDiff
38

fluid_properties: NaNInterface
6.9.1The system should produce a warning when a scalar NaN is produced and user required that the execution would not terminate
Specification(s): quiet_nan_scalar
Design: NaNInterface
Issue(s): #12234 #12350
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
4
6.9.2The system should produce a warning when a vector NaN is produced and user required that the execution would not terminate
Specification(s): quiet_nan_vector
Design: NaNInterface
Issue(s): #12234 #12350
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
4
6.9.3The system should report an error when a NaN is produced by a computation in DEBUG mode, by default
Specification(s): signaling_nan_dbg
Design: NaNInterface
Issue(s): #12234 #12350
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
4
6.9.4The system should not report an error when a NaN is produced by a computation in OPT mode, by default
Specification(s): signaling_nan_opt
Design: NaNInterface
Issue(s): #12234 #12350
Collection(s): FUNCTIONAL
Type(s): RunApp
33

fluid_properties: ADSaturationTemperatureMaterial
6.10.1The system shall provide an AD material that computes saturation temperature.
Specification(s): test
Design: ADSaturationTemperatureMaterial
Issue(s): #15308
Collection(s): FUNCTIONAL
Type(s): CSVDiff
35

fluid_properties: ADSurfaceTensionMaterial
6.10.2The system shall provide an AD material that computes surface tension.
Specification(s): test
Design: ADSurfaceTensionMaterial
Issue(s): #15308
Collection(s): FUNCTIONAL
Type(s): CSVDiff
35

fluid_properties: SaturationPressureMaterial
6.10.3The system shall provide a material that computes saturation pressure using automatic differentiation material properties.
Specification(s): ad
Design: SaturationPressureMaterial
Issue(s): #15860
Collection(s): FUNCTIONAL
Type(s): CSVDiff
35
6.10.4The system shall provide a material that computes saturation pressure using non-automatic differentiation material properties.
Specification(s): nonad
Design: SaturationPressureMaterial
Issue(s): #15860
Collection(s): FUNCTIONAL
Type(s): CSVDiff
35

fluid_properties: Sodium Fluid Properties
6.12.1The system shall be able to compute liquid sodium properties and compare exactly to analytical expressions.
Specification(s): exact
Design: Sodium Fluid Properties Sodium Properties Material
Issue(s): #14798
Collection(s): FUNCTIONAL
Type(s): CSVDiff
33
6.12.2The system shall be able to compute liquid sodium properties given constant thermal conductivity and specific heat values.
Specification(s): constant
Design: Sodium Fluid Properties Sodium Properties Material
Issue(s): #14798
Collection(s): FUNCTIONAL
Type(s): CSVDiff
38

fluid_properties: Sodium Properties Material
6.12.1The system shall be able to compute liquid sodium properties and compare exactly to analytical expressions.
Specification(s): exact
Design: Sodium Fluid Properties Sodium Properties Material
Issue(s): #14798
Collection(s): FUNCTIONAL
Type(s): CSVDiff
33
6.12.2The system shall be able to compute liquid sodium properties given constant thermal conductivity and specific heat values.
Specification(s): constant
Design: Sodium Fluid Properties Sodium Properties Material
Issue(s): #14798
Collection(s): FUNCTIONAL
Type(s): CSVDiff
38

[./specific_enthalpy_aux]
  type = 'Exodiff'
  input = 'specific_enthalpy_aux.i'
  exodiff = 'specific_enthalpy_aux_out.e'
  requirement = 'The system shall compute specific enthalpy from pressure and temperature'
  threading = '!pthreads'
  issues = '#19225'
  design = 'SpecificEnthalpyAux.md'
[../]


[./stagnation_pressure_aux]
  type = 'Exodiff'
  input = 'stagnation_pressure_aux.i'
  exodiff = 'stagnation_pressure_aux_out.e'
  requirement = 'The system shall compute stagnation pressure from specific volume, specific internal energy, and velocit'
  threading = '!pthreads'
  issues = '#19225'
  design = 'StagnationPressureAux.md'
[../]


[./stagnation_temperature_aux]
  type = 'Exodiff'
  input = 'stagnation_temperature_aux.i'
  exodiff = 'stagnation_temperature_aux_out.e'
  requirement = 'The system shall compute stagnation temperature from specific volume, specific internal energy, and velocity'
  threading = '!pthreads'
  issues = '#19225'
  design = 'StagnationTemperatureAux.md'
[../]


[./fluid_density_aux]
  type = 'Exodiff'
  input = 'fluid_density_aux.i'
  exodiff = 'fluid_density_aux_out.e'
  requirement = 'The system shall compute fluid density from pressure and temperature.'
  issues = '#17546'
  design = 'FluidDensityAux.md'
[../]

[./brine]
  type = CSVDiff
  input = 'brine.i'
  csvdiff = 'brine_out.csv'
  allow_test_objects = true
  threading = '!pthreads'
  requirement = 'The system shall compute properties of brine'
  design = 'BrineFluidProperties.md'
  issues = '#6972'
[../]


[./brine_tabulated]
  type = CSVDiff
  input = 'brine_tabulated.i'
  csvdiff = 'brine_out.csv'
  allow_test_objects = true
  threading = '!pthreads'
  prereq = brine
  requirement = 'The system shall compute properties of brine using tabulated water properties'
  design = 'BrineFluidProperties.md'
  issues = '#6972 #12812'
[../]

[calorically_imperfect_gas]
  type = Exodiff
  input = 'test.i'
  exodiff = 'test_out.e'
  requirement = 'The system shall compute properties for a calorically imperfect but otherwise ideal gas'
  design = 'CaloricallyImperfectGas.md'
  issues = '#20101'
  threading = '!pthreads'
[]

[./1ph.p_T]
  type = 'RunApp'
  input = '1ph.p_T.i'
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = 'Single-phase STATIC properties:
--------------------------------------------------------------------------------
Pressure:                              1.0000000000e\+05  Pa
Temperature:                                        300  K
Density:                                    1.162655505  kg/m\^3
Specific volume:                                 0.8601  m\^3/kg
Specific internal energy:              2.1502500000e\+05  J/kg
Specific enthalpy:                     3.0103500000e\+05  J/kg
Specific entropy:                           2422.704793  J/kg

Sound speed:                                347.0072045  m/s
Dynamic viscosity:                     1.8230000000e-05  Pa-s
Specific heat at constant pressure:             1003.45  J/\(kg-K\)
Specific heat at constant volume:                716.75  J/\(kg-K\)
Thermal conductivity:                           0.02568  W/\(m-K\)
Volumetric expansion coefficient:        0.003333333333  1/K'

  requirement = "The fluid properties interrogator shall output static-state fluid properties for (p, T) input."
  issues = '#12995'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./1ph.p_T.json]
  type = 'RunApp'
  input = '1ph.p_T.i'
  cli_args = 'FluidPropertiesInterrogator/json=true'
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = '{"static":{"T":300.0,"beta":0.[0-9]+,"c":347.[0-9]+,"cp":1003.45,"cv":716.[0-9]+,"e":215025.[0-9]+,"h":301035.0,"k":0.[0-9]+,"mu":1.823e-05,"p":100000.0,"rho":1.[0-9]+,"s":2422.[0-9]+,"v":0.86[0-9]+}}'

  requirement = "The fluid properties interrogator shall output static-state fluid properties for (p, T) input in JSON format."
  issues = '#13741'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./1ph.rho_e]
  type = 'RunApp'
  input = '1ph.rho_e.i'
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = 'Single-phase STATIC properties:
--------------------------------------------------------------------------------
Pressure:                              8.6010000000e\+04  Pa
Temperature:                                        300  K
Density:                                              1  kg/m\^3
Specific volume:                                      1  m\^3/kg
Specific internal energy:              2.1502500000e\+05  J/kg
Specific enthalpy:                     3.0103500000e\+05  J/kg
Specific entropy:                           2465.912381  J/kg

Sound speed:                                347.0072045  m/s
Dynamic viscosity:                     1.8230000000e-05  Pa-s
Specific heat at constant pressure:             1003.45  J/\(kg-K\)
Specific heat at constant volume:                716.75  J/\(kg-K\)
Thermal conductivity:                           0.02568  W/\(m-K\)
Volumetric expansion coefficient:        0.003333333333  1/K'

  requirement = "The fluid properties interrogator shall output static-state fluid properties for (rho, e) input."
  issues = '#12995'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./1ph.rho_e.json]
  type = 'RunApp'
  input = '1ph.rho_e.i'
  cli_args = 'FluidPropertiesInterrogator/json=true'
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = '{"static":{"T":299.[0-9]+,"beta":0.[0-9]+,"c":347.[0-9]+,"cp":1003.45,"cv":716.[0-9]+,"e":215025.0,"h":301034.[0-9]+,"k":0.[0-9]+,"mu":1.823e-05,"p":86009.[0-9]+,"rho":1.0,"s":2465.[0-9]+,"v":1.0}}'

  requirement = "The fluid properties interrogator shall output static-state fluid properties for (rho, e) input in JSON format."
  issues = '#13741'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./1ph.rho_p]
  type = 'RunApp'
  input = '1ph.rho_p.i'
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = 'Single-phase STATIC properties:
--------------------------------------------------------------------------------
Pressure:                              1.0000000000e\+05  Pa
Temperature:                                348.7966516  K
Density:                                              1  kg/m\^3
Specific volume:                                      1  m\^3/kg
Specific internal energy:              2.5000000000e\+05  J/kg
Specific enthalpy:                     3.5000000000e\+05  J/kg
Specific entropy:                           2573.931349  J/kg

Sound speed:                                374.1657387  m/s
Dynamic viscosity:                     1.8230000000e-05  Pa-s
Specific heat at constant pressure:             1003.45  J/\(kg-K\)
Specific heat at constant volume:                716.75  J/\(kg-K\)
Thermal conductivity:                           0.02568  W/\(m-K\)
Volumetric expansion coefficient:              0.002867  1/K'

  requirement = "The fluid properties interrogator shall output static-state fluid properties for (rho, p) input."
  issues = '#12995'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./1ph.rho_p.json]
  type = 'RunApp'
  input = '1ph.rho_p.i'
  cli_args = 'FluidPropertiesInterrogator/json=true'
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = '{"static":{"T":348.[0-9]+,"beta":0.[0-9]+,"c":374.[0-9]+,"cp":1003.45,"cv":716.[0-9]+,"e":250000.[0-9]+,"h":350000.[0-9]+,"k":0.[0-9]+,"mu":1.823e-05,"p":100000.0,"rho":1.0,"s":2573.[0-9]+,"v":1.0}}'

  requirement = "The fluid properties interrogator shall output static-state fluid properties for (rho, p) input in JSON format."
  issues = '#13741'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./1ph.rho_rhou_rhoE]
  type = 'RunApp'
  input = '1ph.rho_rhou_rhoE.i'
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = 'Single-phase STATIC properties:
--------------------------------------------------------------------------------
Pressure:                                             1  Pa
Temperature:                                        2.8  K
Density:                                            0.5  kg/m\^3
Specific volume:                                      2  m\^3/kg
Specific internal energy:                             5  J/kg
Specific enthalpy:                                    7  J/kg
Specific entropy:                           2.574048543  J/kg

Sound speed:                                1.673320053  m/s
Dynamic viscosity:                     1.8230000000e-05  Pa-s
Specific heat at constant pressure:                 2.5  J/\(kg-K\)
Specific heat at constant volume:           1.785714286  J/\(kg-K\)
Thermal conductivity:                           0.02568  W/\(m-K\)
Volumetric expansion coefficient:          0.3571428571  1/K



Single-phase STAGNATION properties:
--------------------------------------------------------------------------------
Pressure:                                    1.27312569  Pa
Temperature:                                          3  K
Density:                                   0.5941253221  kg/m\^3
Specific volume:                            1.683146573  m\^3/kg
Specific internal energy:                   5.357142857  J/kg
Specific enthalpy:                                  7.5  J/kg
Specific entropy:                           2.574048543  J/kg

Sound speed:                                1.732050808  m/s
Dynamic viscosity:                     1.8230000000e-05  Pa-s
Specific heat at constant pressure:                 2.5  J/\(kg-K\)
Specific heat at constant volume:           1.785714286  J/\(kg-K\)
Thermal conductivity:                           0.02568  W/\(m-K\)
Volumetric expansion coefficient:          0.3333333333  1/K'

  requirement = "The fluid properties interrogator shall output static-state and stagnation-state fluid properties for (rho, rhou, rhoE) input with a single-phase fluid properties object."
  issues = '#12995'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./1ph.rho_rhou_rhoE.json]
  type = 'RunApp'
  input = '1ph.rho_rhou_rhoE.i'
  cli_args = 'FluidPropertiesInterrogator/json=true'
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = '{"stagnation":{"T0":2.[0-9]+,"beta0":0.[0-9]+,"c0":1.[0-9]+,"cp0":2.[0-9]+,"cv0":1.[0-9]+,"e0":5.[0-9]+,"h0":7.[0-9]+,"k0":0.[0-9]+,"mu0":1.823e-05,"p0":1.[0-9]+,"rho0":0.[0-9]+,"s0":2.[0-9]+,"v0":1.[0-9]+,"vel":1.0},"static":{"T":2.[0-9]+,"beta":0.[0-9]+,"c":1.[0-9]+,"cp":2.[0-9]+,"cv":1.[0-9]+,"e":5.0,"h":6.[0-9]+,"k":0.[0-9]+,"mu":1.823e-05,"p":0.[0-9]+,"rho":0.5,"s":2.[0-9]+,"v":2.0}}'

  requirement = "The fluid properties interrogator shall output static-state and stagnation-state fluid properties for (rho, rhou, rhoE) input with a single-phase fluid properties object in JSON format."
  issues = '#13741'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./2ph.p_T]
  type = 'RunApp'
  input = '2ph.p_T.i'
  allow_test_objects = true
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = 'TWO-PHASE properties:
--------------------------------------------------------------------------------
Critical pressure:                                   25  Pa
Latent heat of vaporization:           6.8896500000e\+05  J/kg



LIQUID phase STATIC properties:
--------------------------------------------------------------------------------
Pressure:                              1.0000000000e\+05  Pa
Temperature:                                        300  K
Density:                                    1.162655505  kg/m\^3
Specific volume:                                 0.8601  m\^3/kg
Specific internal energy:              2.1502500000e\+05  J/kg
Specific enthalpy:                     3.0103500000e\+05  J/kg
Specific entropy:                           2422.704793  J/kg

Sound speed:                                347.0072045  m/s
Dynamic viscosity:                     1.8230000000e-05  Pa-s
Specific heat at constant pressure:             1003.45  J/\(kg-K\)
Specific heat at constant volume:                716.75  J/\(kg-K\)
Thermal conductivity:                           0.02568  W/\(m-K\)
Volumetric expansion coefficient:        0.003333333333  1/K



VAPOR phase STATIC properties:
--------------------------------------------------------------------------------
Pressure:                              1.0000000000e\+05  Pa
Temperature:                                        300  K
Density:                                    1.111111111  kg/m\^3
Specific volume:                                    0.9  m\^3/kg
Specific internal energy:              9.0000000000e\+05  J/kg
Specific enthalpy:                     9.9000000000e\+05  J/kg
Specific entropy:                      1.5368604527e\+04  J/kg

Sound speed:                                314.6426545  m/s
Dynamic viscosity:                     1.7000000000e-05  Pa-s
Specific heat at constant pressure:                3300  J/\(kg-K\)
Specific heat at constant volume:                  3000  J/\(kg-K\)
Thermal conductivity:                              0.05  W/\(m-K\)
Volumetric expansion coefficient:        0.003333333333  1/K'

  requirement = "The fluid properties interrogator shall output two-phase and static-state, single-phase fluid properties for (p, T) input with a two-phase fluid properties object."
  issues = '#12995'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./2ph.p_T.json]
  type = 'RunApp'
  input = '2ph.p_T.i'
  cli_args = 'FluidPropertiesInterrogator/json=true'
  allow_test_objects = true
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = '{"2-phase":{"h_lat":688964.[0-9]+,"p_critical":25.0},"liquid":{"static":{"T":300.0,"beta":0.[0-9]+,"c":347.[0-9]+,"cp":1003.45,"cv":716.[0-9]+,"e":215025.[0-9]+,"h":301035.0,"k":0.[0-9]+,"mu":1.823e-05,"p":100000.0,"rho":1.[0-9]+,"s":2422.[0-9]+,"v":0.[0-9]+}},"vapor":{"static":{"T":300.0,"beta":0.[0-9]+,"c":314.[0-9]+,"cp":3299.[0-9]+,"cv":2999.[0-9]+,"e":899999.[0-9]+,"h":989999.[0-9]+,"k":0.[0-9]+,"mu":1.7e-05,"p":100000.0,"rho":1.[0-9]+,"s":15368.[0-9]+,"v":0.[0-9]+}}}'

  requirement = "The fluid properties interrogator shall output two-phase and static-state, single-phase fluid properties for (p, T) input with a two-phase fluid properties object in JSON format."
  issues = '#13741'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./2ph_ncg_p_T]
  type = 'RunApp'
  input = '2ph_ncg_p_T.i'
  allow_test_objects = true
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = 'TWO-PHASE properties:
--------------------------------------------------------------------------------
Critical pressure:                                   25  Pa
Latent heat of vaporization:           8.7784021256e\+05  J/kg



LIQUID phase STATIC properties:
--------------------------------------------------------------------------------
Pressure:                              1.0000000000e\+05  Pa
Temperature:                                372.7559289  K
Density:                                    0.993600213  kg/m\^3
Specific volume:                            1.006441008  m\^3/kg
Specific internal energy:              2.5161025201e\+05  J/kg
Specific enthalpy:                     3.5225435281e\+05  J/kg
Specific entropy:                           2486.783172  J/kg

Sound speed:                                375.3688068  m/s
Dynamic viscosity:                     1.8230000000e-05  Pa-s
Specific heat at constant pressure:                 945  J/\(kg-K\)
Specific heat at constant volume:                   675  J/\(kg-K\)
Thermal conductivity:                           0.02568  W/\(m-K\)
Volumetric expansion coefficient:        0.002682720575  1/K



Vapor mixture STATIC properties:
--------------------------------------------------------------------------------
Pressure:                              1.0000000000e\+05  Pa
Temperature:                                372.7559289  K
Density:                                   0.8972309616  kg/m\^3
Specific volume:                            1.114540227  m\^3/kg
Specific internal energy:              1.0334658129e\+06  J/kg
Specific enthalpy:                     1.1449198356e\+06  J/kg

Sound speed:                                351.3883482  m/s
Dynamic viscosity:                     1.8230000000e-05  Pa-s
Specific heat at constant pressure:              3071.5  J/\(kg-K\)
Specific heat at constant volume:                2772.5  J/\(kg-K\)
Thermal conductivity:                           0.02568  W/\(m-K\)'

  requirement = "The fluid properties interrogator shall output two-phase and static-state, single-phase fluid properties for (p, T) input with a two-phase NCG fluid properties object."
  issues = '#12995'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./2ph_ncg_p_T.json]
  type = 'RunApp'
  input = '2ph_ncg_p_T.i'
  cli_args = 'FluidPropertiesInterrogator/json=true'
  allow_test_objects = true
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = '{"2-phase":{"h_lat":877840.[0-9]+,"p_critical":25.0},"liquid":{"static":{"T":372.[0-9]+,"beta":0.[0-9]+,"c":375.[0-9]+,"cp":945.[0-9]+,"cv":675.[0-9]+,"e":251610.[0-9]+,"h":352254.[0-9]+,"k":0.[0-9]+,"mu":1.823e-05,"p":100000.0,"rho":0.[0-9]+,"s":2486.[0-9]+,"v":1.[0-9]+}},"vapor-mixture":{"static":{"T":372.[0-9]+,"c":351.[0-9]+,"cp":3071.[0-9]+,"cv":2772.[0-9]+,"e":1033465.[0-9]+,"h":1144919.[0-9]+,"k":0.[0-9]+,"mu":1.[0-9]+e-05,"p":100000.0,"rho":0.[0-9]+,"v":1.[0-9]+}}}'

  requirement = "The fluid properties interrogator shall output two-phase and static-state, single-phase fluid properties for (p, T) input with a two-phase NCG fluid properties object in JSON format."
  issues = '#13741'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./vapor_mixture_rho_e]
  type = 'RunApp'
  input = 'vapor_mixture_rho_e.i'
  allow_test_objects = true
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = 'Vapor mixture STATIC properties:
--------------------------------------------------------------------------------
Pressure:                              9.0404345635e\+05  Pa
Temperature:                                2547.214296  K
Density:                                    1.187005237  kg/m\^3
Specific volume:                           0.8424562661  m\^3/kg
Specific internal energy:              2.4771659033e\+06  J/kg
Specific enthalpy:                     3.2387829780e\+06  J/kg

Sound speed:                                997.8878004  m/s
Dynamic viscosity:                     1.8230000000e-05  Pa-s
Specific heat at constant pressure:              1271.5  J/\(kg-K\)
Specific heat at constant volume:                 972.5  J/\(kg-K\)
Thermal conductivity:                           0.02568  W/\(m-K\)'

  requirement = "The fluid properties interrogator shall output static-state, single-phase fluid properties for (rho, e) input with a vapor mixture fluid properties object."
  issues = '#12995'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./vapor_mixture_rho_e.json]
  type = 'RunApp'
  input = 'vapor_mixture_rho_e.i'
  cli_args = 'FluidPropertiesInterrogator/json=true'
  allow_test_objects = true
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = '{"static":{"T":2547.[0-9]+,"c":997.[0-9]+,"cp":1271.[0-9]+,"cv":972.[0-9]+,"e":2477165.[0-9]+,"h":3238782.[0-9]+,"k":0.[0-9]+,"mu":1.[0-9]+e-05,"p":904043.[0-9]+,"rho":1.[0-9]+,"v":0.[0-9]+}}'

  requirement = "The fluid properties interrogator shall output static-state, single-phase fluid properties for (rho, e) input with a vapor mixture fluid properties object in JSON format."
  issues = '#13741'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./2ph_p]
  type = 'RunApp'
  input = '2ph.p.i'
  allow_test_objects = true
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = 'TWO-PHASE properties:
--------------------------------------------------------------------------------
Critical pressure:                                   25  Pa
Saturation temperature:                2.0000000000e\+05  K
Latent heat of vaporization:           4.5931000000e\+08  J/kg'

  requirement = "The fluid properties interrogator shall output two-phase fluid properties for (p) input with a two-phase fluid properties object."
  issues = '#12995'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./2ph_p.json]
  type = 'RunApp'
  input = '2ph.p.i'
  cli_args = 'FluidPropertiesInterrogator/json=true'
  allow_test_objects = true
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = '{"2-phase":{"T_sat":200000.0,"h_lat":459309999.[0-9]+,"p_critical":25.0}}'

  requirement = "The fluid properties interrogator shall output two-phase fluid properties for (p) input with a two-phase fluid properties object in JSON format."
  issues = '#13741'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./2ph_T]
  type = 'RunApp'
  input = '2ph.T.i'
  allow_test_objects = true
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = 'TWO-PHASE properties:
--------------------------------------------------------------------------------
Critical pressure:                                   25  Pa
Saturation pressure:                                900  Pa
Latent heat of vaporization:           6.8896500000e\+05  J/kg
Surface tension:                                   1500  N/m'

  requirement = "The fluid properties interrogator shall output two-phase fluid properties for (T) input with a two-phase fluid properties object."
  issues = '#12995'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./2ph_T.json]
  type = 'RunApp'
  input = '2ph.T.i'
  cli_args = 'FluidPropertiesInterrogator/json=true'
  allow_test_objects = true
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_out = '{"2-phase":{"h_lat":688964.[0-9]+,"p_critical":25.0,"p_sat":900.0,"sigma":1500.0}}'

  requirement = "The fluid properties interrogator shall output two-phase fluid properties for (T) input with a two-phase fluid properties object in JSON format."
  issues = '#13741'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./err.wrong_fp_type]
  type = RunException
  input = 'err.wrong_fp_type.i'
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_err = "The type of the parameter 'fp' must be derived from type 'SinglePhaseFluidProperties', 'VaporMixtureFluidProperties', or 'TwoPhaseFluidProperties'"

  requirement = "The fluid properties interrogator shall throw an error if an
      incompatible fluid properties object is supplied."
  issues = '#12995'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./err.extraneous_parameter]
  type = RunException
  input = '1ph.rho_e.i'
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_err = "fp_interrogator\: \(rho\,e\) has been specified\; T cannot be specified\."
  cli_args = "FluidPropertiesInterrogator/T=300"

  requirement = "The fluid properties interrogator shall throw an error if an
      extraneous parameter(s) are supplied."
  issues = '#12995'
  design = 'FluidPropertiesInterrogator.md'
[../]


[./err.no_params]
  type = RunException
  input = 'err.no_params.i'
  allow_warnings = true
  method = 'OPT'
  threading = '!pthreads'
  expect_err = "fp_interrogator\: For one-phase fluid properties\, you must provide one of the following
combinations of thermodynamic properties:"

  requirement = "The fluid properties interrogator shall throw an error if an
      no valid input sets were supplied."
  issues = '#12995'
  design = 'FluidPropertiesInterrogator.md'
[../]

[./test]
  type = 'CSVDiff'
  input = 'saturation_pressure_function.i'
  csvdiff = 'saturation_pressure_function_out.csv'
  allow_test_objects = True

  requirement = 'The system shall provide a function that computes saturation pressure from a temperature function'
  design = '/SaturationPressureFunction.md'
  issues = '#14755'
[../]

[./test]
  type = 'CSVDiff'
  input = 'saturation_temperature_function.i'
  csvdiff = 'saturation_temperature_function_out.csv'
  allow_test_objects = True

  requirement = 'The system shall provide a function that computes saturation temperature from a pressure function'
  design = '/SaturationTemperatureFunction.md'
  issues = '#14755'
[../]

[test]
  type = 'CSVDiff'
  input = 'test.i'
  csvdiff = 'test_out.csv'
  rel_err = 1e-10
  requirement = 'The system shall be able to set an initial condition for density given pressure and temperature as variables'
  design = 'RhoFromPressureTemperatureIC.md'
  issues = '#15524'
[]

[./test]
  type = 'CSVDiff'
  input = 'test.i'
  csvdiff = 'test_out.csv'
  rel_err = 1e-10
  requirement = 'The system shall be able to set an initial condition for density of vapor mixture given pressure and temperature as variables'
  design = 'RhoVaporMixtureFromPressureTemperatureIC.md'
  issues = '#15524'
[../]

[test]
  type = 'CSVDiff'
  input = 'test.i'
  csvdiff = 'test_out.csv'
  rel_err = 1e-10
  requirement = 'The system shall be able to set an initial condition for specific enthalpy given pressure and temperature as variables'
  design = 'SpecificEnthalpyFromPressureTemperatureIC.md'
  issues = '#15561'
[]

[./quiet_nan_scalar]
  type = 'RunException'
  input = 'nan_interface.i'
  cli_args = 'Modules/FluidProperties/fp/emit_on_nan=warning'
  allow_test_objects = True
  method = 'DBG'
  threading = '!pthreads'

  requirement = 'The system should produce a warning when a scalar NaN is produced and user required that the execution would not terminate'
  expect_err = "fp: A NaN was produced."
  design = '/NaNInterface.md'
  issues = '#12234 #12350'
[../]


[./quiet_nan_vector]
  type = 'RunException'
  input = 'nan_interface.i'
  cli_args = 'Modules/FluidProperties/fp/emit_on_nan=warning Kernels/test_kernel/test_vector_version=true'
  allow_test_objects = True
  method = 'DBG'
  threading = '!pthreads'

  requirement = 'The system should produce a warning when a vector NaN is produced and user required that the execution would not terminate'
  expect_err = "fp: A NaN was produced."
  design = '/NaNInterface.md'
  issues = '#12234 #12350'
[../]


[./signaling_nan_dbg]
  type = 'RunException'
  input = 'nan_interface.i'
  allow_test_objects = True
  method = 'DBG'
  threading = '!pthreads'

  requirement = 'The system should report an error when a NaN is produced by a computation in DEBUG mode, by default'
  expect_err = "fp: A NaN was produced."
  design = '/NaNInterface.md'
  issues = '#12234 #12350'
[../]


[./signaling_nan_opt]
  type = 'RunApp'
  input = 'nan_interface.i'
  allow_test_objects = True
  method = 'OPT'
  threading = '!pthreads'

  requirement = 'The system should not report an error when a NaN is produced by a computation in OPT mode, by default'
  design = '/NaNInterface.md'
  issues = '#12234 #12350'
[../]

[./test]
  type = 'CSVDiff'
  input = 'ad_saturation_temperature_material.i'
  csvdiff = 'ad_saturation_temperature_material_out.csv'
  allow_test_objects = True
  recover = false

  requirement = 'The system shall provide an AD material that computes saturation temperature.'
  design = '/ADSaturationTemperatureMaterial.md'
  issues = '#15308'
[../]

[./test]
  type = 'CSVDiff'
  input = 'ad_surface_tension_material.i'
  csvdiff = 'ad_surface_tension_material_out.csv'
  allow_test_objects = True
  recover = false

  requirement = 'The system shall provide an AD material that computes surface tension.'
  design = '/ADSurfaceTensionMaterial.md'
  issues = '#15308'
[../]


[ad]
  type = 'CSVDiff'
  input = 'saturation_pressure_material.i'
  csvdiff = 'saturation_pressure_material_out.csv'
  recover = false

  requirement = 'The system shall provide a material that computes saturation pressure using automatic differentiation material properties.'
[]


[nonad]
  type = 'CSVDiff'
  input = 'saturation_pressure_material.i'
  cli_args = "
      Materials/T_mat/type=GenericConstantMaterial
      Materials/p_sat_mat/type=SaturationPressureMaterial
      Postprocessors/p_sat_pp/type=ElementAverageMaterialProperty"
  csvdiff = 'saturation_pressure_material_out.csv'
  prereq = 'ad'
  recover = false

  requirement = 'The system shall provide a material that computes saturation pressure using non-automatic differentiation material properties.'
[]


[./exact]
  type = CSVDiff
  input = 'exact.i'
  csvdiff = 'exact_out.csv'
  abs_zero = 1e-9
  # At the initial time, an assertion is triggered regarding the temperature
  # exceeding the critical temperature. The temperature variable stays within
  # this critical temperature, but temperature computed from the given enthalpy
  # does not.
  method = 'OPT'
  requirement = 'The system shall be able to compute liquid sodium properties and compare exactly to analytical expressions.'
[../]


[./constant]
  type = CSVDiff
  input = 'constant.i'
  csvdiff = 'constant_out.csv'
  requirement = 'The system shall be able to compute liquid sodium properties given constant thermal conductivity and specific heat values.'
[../]


[./exact]
  type = CSVDiff
  input = 'exact.i'
  csvdiff = 'exact_out.csv'
  abs_zero = 1e-9
  # At the initial time, an assertion is triggered regarding the temperature
  # exceeding the critical temperature. The temperature variable stays within
  # this critical temperature, but temperature computed from the given enthalpy
  # does not.
  method = 'OPT'
  requirement = 'The system shall be able to compute liquid sodium properties and compare exactly to analytical expressions.'
[../]


[./constant]
  type = CSVDiff
  input = 'constant.i'
  csvdiff = 'constant_out.csv'
  requirement = 'The system shall be able to compute liquid sodium properties given constant thermal conductivity and specific heat values.'
[../]

Introduction
Use Cases
References
Definitions and Acronyms
Design Stakeholders and Concerns
System Design
Adaptivity
AuxKernels
AuxScalarKernels
AuxVariables
BCs
Bounds
Closures
Components
Constraints
Contact
ControlLogic
Controls
CoupledHeatTransfers
Covariance
DGKernels
Dampers
Debug
DeprecatedBlock
DiracKernels
Distributions
DomainIntegral
Executioner
Executors
FVBCs
FVInterfaceKernels
FVKernels
FluidPropertiesInterrogator
Functions
GeochemicalModelInterrogator
GlobalParams
GrayDiffuseRadiation
HeatStructureMaterials
ICs
InterfaceKernels
Kernels
Materials
Mesh
Modules
MortarGapHeatTransfer
MultiApps
NodalKernels
NodalNormals
Outputs
PorousFlowBasicTHM
PorousFlowFullySaturated
PorousFlowUnsaturated
Postprocessors
Preconditioning
Problem
RayBCs
RayKernels
ReactionNetwork
Reporters
Samplers
ScalarKernels
SpatialReactionSolver
StochasticTools
Surrogates
ThermalContact
TimeDependentReactionSolver
TimeIndependentReactionSolver
Trainers
Transfers
UserObjects
Variables
VectorPostprocessors
XFEM
Requirements Cross - Reference