Ray Tracing Failure Analysis Report

Introduction

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

Dependencies

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

  • ray_tracing: Traceray
  • 14.9.11The system shall throw an error if RayBCs are defined on internal sidesets, but the study does not have internal sideset capability enabled.

    Specification(s): internal_sidesets_disabled

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 14.9.12The system shall throw an error if RayBCs are defined on internal sidesets and said internal sidesets are not bounded by different subdomains.

    Specification(s): not_subdomain_bounded

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 14.9.14The system shall by default warn that tracing on non-planar faces is an approximation.

    Specification(s): warning

    Design: RayTracingStudy

    Issue(s): #16028#16170

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 14.9.24The system shall report an error when a ray hits a boundary during tracing and
    1. the boundary does not have any RayBCs
    2. and then the boundary does not have any RayBCs that change the trajectory of the ray or end the ray.

    Specification(s): error/both, error/one

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException