Navier Stokes Failure Analysis Report

Introduction

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

Dependencies

The Navier Stokes module is developed using MOOSE and can itself be based on various MOOSE modules, as such the FAR for the Navier Stokes 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 Navier Stokes module.

  • navier_stokes: Finite Element
  • 10.2.31We shall error if the user provides less velocity components than the mesh dimension

    Specification(s): check_too_few_components

    Design: AdvectionBC

    Issue(s): #13283

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 10.2.32We shall error if the user provides more than 3 velocity components

    Specification(s): check_too_many_components

    Design: AdvectionBC

    Issue(s): #13283

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 10.2.127The system shall allow MOOSE applications to specify nonzero malloc behavior; for the Navier-Stokes application, new nonzero allocations shall be errors.

    Specification(s): malloc

    Design: MooseApp

    Issue(s): #7901

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • navier_stokes: Postprocessors
  • 10.5.9The system shall report an error if
    1. a volumetric flow rate is requested at the initialization of the simulation on a boundary internal to the flow domain when using finite volume and Rhie Chow interpolation, as this is not supported

    Specification(s): errors/initial_interior

    Design: VolumetricFlowRate

    Issue(s): #18817

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 10.5.14The system shall report an error in a pressure drop calculation if
    1. an upstream boundary for the pressure is not a boundary for the postprocessor,
    2. a downstream boundary for the pressure is not a boundary for the postprocessor,
    3. a boundary for the postprocessor is not part of either the upstream or downstream pressure evaluation,
    4. a downstream boundary is also an upstream boundary for the pressure drop,
    5. the weighting functor integrates to 0, and
    6. a face interpolation rule is specified for a finite element pressure variable.

    Specification(s): errors/upstream_not_in_boundary, errors/downstream_not_in_boundary, errors/boundary_not_drop_calc, errors/upstream_and_downstream, errors/weight_not_appropriate, errors/face_interp_scheme_for_fe

    Design: PressureDrop

    Issue(s): #23685

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException