Thermal Hydraulics Requirements Traceability Matrix

This template follows INL template TEM-214, "IT System Requirements Traceability Matrix."

Introduction

Minimum System Requirements

In general, the following is required for MOOSE-based development:

  • GCC/Clang C++17 compliant compiler (GCC @ 7.5.0, Clang @ 5.0.2 or greater)

    • Note: Intel compilers are not supported.

  • Memory: 16 GBs (debug builds)

  • Processor: 64-bit x86

  • Disk: 30GB

System Purpose

The MOOSE is a tool for solving complex coupled Multiphysics equations using the finite element method. MOOSE uses an object-oriented design to abstract data structure management, parallelism, threading and compiling while providing an easy to use interface targeted at engineers that may not have a lot of software development experience. MOOSE will require extreme scalability and flexibility when compared to other FEM frameworks. For instance, MOOSE needs the ability to run extremely complex material models, or even third-party applications within a parallel simulation without sacrificing parallelism. This capability is in contrast to what is often seen in commercial packages, where custom material models can limit the parallel scalability, forcing serial runs in the most severe cases. When comparing high-end capabilities, many MOOSE competitors target modest-sized clusters with just a few thousand processing cores. MOOSE, however, will be required to routinely executed on much larger clusters with scalability to clusters available in the top 500 systems (top500.org). MOOSE will also be targeted at smaller systems such as high-end laptop computers.

The design goal of MOOSE is to give developers ultimate control over their physical models and applications. Designing new models or solving completely new classes of problems will be accomplished by writing standard C++ source code within the framework's class hierarchy. Scientists and engineers will be free to implement completely new algorithms using pieces of the framework where possible, and extending the framework's capabilities where it makes sense to do so. Commercial applications do not have this capability, and instead opt for either a more rigid parameter system or a limited application-specific metalanguage.

System Scope

MOOSE's scope is to provide a set of interfaces for building FEM simulations. Abstractions to all underlying libraries are provided.

Solving coupled problems where competing physical phenomena impact one and other in a significant nonlinear fashion represents a serious challenge to several solution strategies. Small perturbations in strongly-coupled parameters often have very large adverse effects on convergence behavior. These adverse effects are compounded as additional physics are added to a model. To overcome these challenges, MOOSE employs three distinct yet compatible systems for solving these types of problems.

First, an advanced numerical technique called the JFNK method is employed to solve the most fully-coupled physics in an accurate, consistent way. An example of this would be the effect of temperature on the expansion or contraction of a material. While the JFNK numerical method is very effective at solving fully-coupled equations, it can also be computationally expensive. Plus, not all physical phenomena in a given model are truly coupled to one another. For instance, in a reactor, the speed of the coolant flow may not have any direct effect on the complex chemical reactions taking place inside the fuel rods. We call such models "loosely-coupled". A robust, scalable system must strike the proper balance between the various modeling strategies to avoid performing unnecessary computations or incorrectly predicting behavior in situations such as these.

MOOSE's Multiapp system will allow modelers to group physics into logical categories where MOOSE can solve some groups fully-coupled and others loosely-coupled. The Multiapp system goes even further by also supporting a "tightly-coupled" strategy, which falls somewhere between the "fully-coupled" and "loosely-coupled" approaches. Several sets of physics can then be linked together into logical hierarchies using any one of these coupling strategies, allowing for several potential solution strategies. For instance, a complex nuclear reactor model might consist of several tightly-coupled systems of fully-coupled equations.

Finally, MOOSE's Transfers system ties all of the physics groups contained within the Multiapp system together and allows for full control over the flow of information among the various groups. This capability bridges physical phenomena from several different complementary scales simultaneously. When these three MOOSE systems are combined, myriad coupling combinations are possible. In all cases, the MOOSE framework handles the parallel communication, input, output and execution of the underlying simulation. By handling these computer science tasks, the MOOSE framework keeps modelers focused on doing research.

MOOSE innovates by building advanced simulation capabilities on top of the very best available software technologies in a way that makes them widely accessible for innovative research. MOOSE is equally capable of solving small models on common laptops and the very biggest FEM models ever attempted—all without any major changes to configuration or source code. Since its inception, the MOOSE project has focused on both developer and computational efficiency. Improved developer efficiency is achieved by leveraging existing algorithms and technologies from several leading open-source packages. Additionally, MOOSE uses several complementary parallel technologies (both the distributed-memory message passing paradigm and shared-memory thread-based approaches are used) to lay an efficient computational foundation for development. Using existing open technologies in this manner helps the developers reduce the scope of the project and keeps the size of the MOOSE code base maintainable. This approach provides users with state-of-the-art finite element and solver technology as a basis for the advanced coupling and solution strategies mentioned previously.

MOOSE's developers work openly with other package developers to make sure that cutting-edge technologies are available through MOOSE, providing researchers with competitive research opportunities. MOOSE maintains a set of objects that hide parallel interfaces while exposing advanced spatial and temporal coupling algorithms in the framework. This accessible approach places developmental technology into the hands of scientists and engineers, which can speed the pace of scientific discovery.

Assumptions and Dependencies

The Thermal Hydraulics application is developed using MOOSE and is based on various modules, as such the RTM for Thermal Hydraulics is dependent upon the files listed at the beginning of this document.

Pre-test Instructions/Environment/Setup

Ideally all testing should be performed on a clean test machine following one of the supported configurations setup by the test system engineer. Testing may be performed on local workstations and cluster systems containing supported operating systems.

The repository should be clean prior to building and testing. When using "git" this can be done by doing a force clean in the main repository and each one of the submodules:


git clean -xfd
git submodule foreach 'git clean -xfd'

All tests must pass in accordance with the type of test being performed. This list can be found in the Software Test Plan.

System Requirements Traceability

Functional Requirements

  • thermal_hydraulics: Actions
  • 15.1.1

    Specification(s): action

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • thermal_hydraulics: Auxkernels
  • 15.2.1The system shall compute convective heat flux between fluid and wall temperature for 1-phase flow

    Specification(s): test

    Design: ConvectiveHeatFlux1PhaseAux

    Issue(s): #60

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.2.2

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.2.3

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.2.4

    Specification(s): 1phase

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.2.5

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.2.6

    Specification(s): sum

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.2.7

    Specification(s): weighted_average

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: Base
  • 15.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

  • 15.3.2

    Specification(s): warning

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.3.3

    Specification(s): loop_identification

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • thermal_hydraulics: Closures
  • 15.4.1

    Specification(s): phy:

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.4.2

    Specification(s): enumeration_option

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 15.4.3

    Specification(s): err:missing_f_1phase

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 15.4.4

    Specification(s): enumeration_option

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • thermal_hydraulics: Controls
  • 15.6.1

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.6.2

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.6.3

    Specification(s): err.negative_tau

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 15.6.4

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.6.5

    Specification(s): non_existent_control_data

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 15.6.6

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.6.7The system shall provide a control that evaluates a parsed function

    Specification(s): test

    Design: ParsedFunctionControl

    Issue(s): #93

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.6.8

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.6.9

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.6.10

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.6.11

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.6.12

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.6.13

    Specification(s): no_error

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.6.14

    Specification(s): throw_error

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 15.6.15

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.6.16

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

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

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

    Type(s): RunException

  • thermal_hydraulics: Jacobians
  • 15.8.1

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.2

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.3

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.4

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.5

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.6

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.7

    Specification(s): mass_free_constraint

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.8

    Specification(s): one_d_3eqn_momentum_flux

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.9

    Specification(s): one_d_3eqn_momentum_area_gradient

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.10

    Specification(s): one_d_3eqn_momentum_friction

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.11

    Specification(s): one_d_3eqn_energy_flux

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.12

    Specification(s): one_d_energy_wall_heating

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.13

    Specification(s): one_d_3eqn_momentum_gravity

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.14

    Specification(s): one_d_3eqn_energy_gravity

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.15

    Specification(s): one_d_3eqn_energy_heat_source

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.16

    Specification(s): ad_solid_material

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.17

    Specification(s): constant_material

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.18

    Specification(s): density_3eqn_material

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.19

    Specification(s): dynamic_viscosity

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.20

    Specification(s): linear_test_material

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.21

    Specification(s): pressure_3eqn_material

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.22

    Specification(s): specific_internal_energy_3eqn

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.23

    Specification(s): specific_volume_3eqn

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.24

    Specification(s): velocity_3eqn

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.25

    Specification(s): enthalpy_3eqn

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.26

    Specification(s): reynolds_number

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.27

    Specification(s): temperature_3eqn_material

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.28

    Specification(s): total_enthalpy_3eqn

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.29

    Specification(s): wall_friction_function

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.30

    Specification(s): wall_friction_churchill

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.31

    Specification(s): rhoV

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.32

    Specification(s): rhouV

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.33

    Specification(s): rhovV

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.34

    Specification(s): rhowV

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.35

    Specification(s): rhoEV

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.36

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.8.37

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • thermal_hydraulics: Materials
  • 15.9.1

    Specification(s): ad_average_wall_temperature_3eqn

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.2

    Specification(s): ad_alt_def

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.3

    Specification(s): ad_err.n_hw_sources

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 15.9.4

    Specification(s): ad_err.n_phf_sources

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 15.9.5

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.6

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.7

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.8

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.9

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.10

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.11

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.12

    Specification(s): test_name

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.13

    Specification(s): average_wall_temperature_3eqn

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.14

    Specification(s): alt_def

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.15

    Specification(s): err.n_hw_sources

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 15.9.16

    Specification(s): err.n_phf_sources

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 15.9.17

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.18

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.19

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.20

    Specification(s): churchill

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.21

    Specification(s): churchill_ad

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.22

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.9.23

    Specification(s): test_name

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: Output
  • 15.11.1

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 15.11.2

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • thermal_hydraulics: Postprocessors
  • 15.12.1

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.12.2

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

    Type(s): RunException

  • 15.12.4

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.12.5The 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): #215

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 15.12.6

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.12.7

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.12.8

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.12.9

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.12.10

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.12.11

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.12.12

    Specification(s): heat_structure_energy_plate

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.12.13

    Specification(s): heat_structure_energy_plate_T_ref

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.12.14

    Specification(s): heat_structure_energy_cylinder

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.12.15

    Specification(s): non_existent_par_name

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 15.12.16The system shall provide a post-processor to retrieve the torque and moment of inertia from a shaft-connected component.

    Specification(s): test

    Design: ShaftConnectedComponentPostprocessor

    Issue(s): #20196

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.12.17

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.12.18The system shall compute specific impulse from conditions on a boundary

    Specification(s): Isp_1ph

    Design: SpecificImpulse1Phase

    Issue(s): #189

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: Problems
  • 15.13.1

    Specification(s): without_junction

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.2

    Specification(s): with_junction

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.3The system shall be able to model an open Brayton cycle
    1. for a few time steps, and
    2. for a long duration.

    Specification(s): open/light, open/heavy

    Design: Brayton Cycle

    Issue(s): #20196

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.13.4The system shall be able to model a closed Brayton cycle
    1. for a few time steps, and
    2. for a long duration.

    Specification(s): closed/light, closed/heavy

    Design: Brayton Cycle

    Issue(s): #20196

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.13.5

    Specification(s): 1phase

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.6

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.13.7The system shall produce an accurate solution to the Lax shock tube benchmark problem
    1. using an explicit temporal discretization, and
    2. using an implicit temporal discretization.

    Specification(s): all/explicit, all/implicit

    Design: FlowChannel1Phase

    Issue(s): #5

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.8

    Specification(s): 1phase

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.13.9

    Specification(s): sedov_blast_wave

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.10

    Specification(s): sod_shock_tube_erk2_heavy

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.11

    Specification(s): sod_shock_tube_erk2_light

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.12

    Specification(s): non_x_direction_1phase

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.13

    Specification(s): sod_shock_tube_be

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.14

    Specification(s): square_wave_minmod

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.15

    Specification(s): square_wave_none

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.16

    Specification(s): square_wave_mc

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.17

    Specification(s): square_wave_superbee

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.18

    Specification(s): 3eqn

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.19

    Specification(s): woodward_colella_blast_wave

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • thermal_hydraulics: Scalarkernels
  • 15.14.1

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.14.2

    Specification(s): postprocessor_source

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: Userobjects
  • 15.15.1

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.15.2

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.3The system shall allow computing changes in channel flow areas from deformation.

    Specification(s): layered_area_change

    Design: LayeredFlowAreaChange

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • thermal_hydraulics: Utils
  • 15.16.1

    Specification(s): cubic_nonad

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.16.2

    Specification(s): weighted_nonad

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.16.3

    Specification(s): cubic_derivative

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.16.4

    Specification(s): weighted_derivative

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.16.5

    Specification(s): ad_cubic

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.16.6

    Specification(s): ad_weighted

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • thermal_hydraulics: Vectorpostprocessors
  • 15.17.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

  • 15.17.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): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 15.17.4

    Specification(s): sampler_1d_vector

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

Usability Requirements

Performance Requirements

System Interface Requirements

References

No citations exist within this document.