Thermal Hydraulics Failure Analysis Report

Introduction

The FAR for the Thermal Hydraulics module describes the system functional and non-functional requirements that describe the expected interactions that the software shall provide.

Dependencies

The Thermal Hydraulics module is developed using MOOSE and can itself be based on various MOOSE modules, as such the FAR for the Thermal Hydraulics module is dependent upon the following documents.

Failure Analysis Requirements

The following is a complete list for all the requirements related to failure analysis for the Thermal Hydraulics module.

  • thermal_hydraulics: Actions
  • 11.1.2The system shall report an error for the coupled heat transfer action if the mesh is not aligned with the x, y, or z axis.

    Specification(s): misaligned

    Design: CoupledHeatTransferAction

    Issue(s): #21818

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: Closures
  • 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

  • 11.4.4The system shall report an error if the friction parameter is missing in the simple closures object.

    Specification(s): err:missing_f_1phase

    Design: Closures1PhaseSimple

    Issue(s): #19682

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 11.4.5The system shall report an error if the user attempts passing closure parameters directly to components.

    Specification(s): enumeration_option

    Design: Closures1PhaseSimple

    Issue(s): #19682

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • thermal_hydraulics: Controls
  • 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

  • 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

  • 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

  • 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: Functions
  • 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: Postprocessors
  • 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

  • 11.13.19The system shall report an error if a component parameter is selected for output but that parameter or that component does not exist.

    Specification(s): non_existent_par_name

    Design: RealComponentParameterValuePostprocessor

    Issue(s): #19724

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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