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
  • 5.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

  • 5.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

  • 5.2.79The system shall error if hybridized discontinuous Galerkin kernels and boundary conditions implement different physics.

    Specification(s): mismatching_physics

    Design: NavierStokesHDGKernel

    Issue(s): #26405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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