Ray Tracing Requirements Traceability Matrix

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

commentnote

This document serves as an addendum to Framework Requirements Traceability Matrix and captures information for RTM specific to the Ray Tracing application.

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 Ray Tracing application is developed using MOOSE and is based on various modules, as such the RTM for Ray Tracing 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

  • ray_tracing: Raybcs
  • 13.6.1The system shall support the dependency resolution of RayBCs.

    Specification(s): test

    Design: RayBCs

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.6.2The system shall throw a reasonable error when adding a dependency for a RayBC that does not exist.

    Specification(s): missing

    Design: RayBCs

    Issue(s): #16028

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 13.6.3The system shall report an error when changing a ray direction within a RayBC when
    1. the ray was set to not continue by another RayBC,
    2. the ray already had its direction changed,
    3. the end point of the ray was set upon generation,
    4. and when the direction is changed to the zero vector.

    Specification(s): change_direction/should_not_continue, change_direction/again, change_direction/end_set, change_direction/zero

    Design: RayBCs

    Issue(s): #16028

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 13.6.4The system shall support the specular reflection of rays on a boundary.

    Specification(s): test

    Design: ReflectRayBCRayBCs

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.6.5The system shall report a reasonable warning when using an approximation to reflect a ray on a side that is not planar.

    Specification(s): non_planar_warning

    Design: ReflectRayBCRayBCs

    Issue(s): #16028

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • ray_tracing: Raykernels
  • 13.7.1The system shall throw a reasonable error if an ADRayKernel
    1. is used with a coordinate system other than xyz or
    2. is used in an explicit manner.

    Specification(s): errors/xyz_only, errors/implicit_only

    Design: ADRayKernel

    Issue(s): #16028

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 13.7.2The system shall throw a reasonable error if a non-supported auxiliary variable is used with a ray aux kernel.

    Specification(s): const_monomial_only

    Design: AuxRayKernel

    Issue(s): #16028

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 13.7.3The system shall support the coupling of variables on rays that contribute to the residual and Jacobian.

    Specification(s): test

    Design: RayKernels

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 13.7.4The system shall be able to produce the exact Jacobian with coupled variables on rays.

    Specification(s): test_jac

    Design: RayKernels

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 13.7.5The system shall support the coupling of variables using automatic differentiation on rays that contribute to the residual and Jacobian.

    Specification(s): test_ad

    Design: RayKernels

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 13.7.6The system shall be able to produce the exact Jacobian using automatic differentiation on rays.

    Specification(s): test_ad_jac

    Design: RayKernels

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 13.7.7The system shall support the dependency resolution of RayKernels.

    Specification(s): test

    Design: RayKernels

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.7.8The system shall throw a reasonable error when adding a dependency for a RayKernel that does not exist.

    Specification(s): missing

    Design: RayKernels

    Issue(s): #16028

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 13.7.9The system shall report an error when changing a ray start and/or direction within a RayKernel when
    1. the ray was set to not continue by another RayKernel,
    2. the ray was set to not continue by another RayKernel and it is at its end point,
    3. the ray's trajectory was already changed,
    4. the ray's end point has been set,
    5. the ray's start point is not within the current element, and
    6. when the ray's new direction is set to the zero vector.

    Specification(s): change_direction/should_not_continue, change_direction/should_not_continue_at_end, change_direction/changed_again, change_direction/end_set, change_direction/out_of_elem, change_direction/zero_direction

    Design: RayKernels

    Issue(s): #16028

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 13.7.10The system shall provide the ability to compute the integral of a Function along a line.

    Specification(s): test

    Design: FunctionIntegralRayKernel

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.7.11The system shall provide the ability to compute the average value of a Function along a line.

    Specification(s): average

    Design: FunctionIntegralRayKernel

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.7.12The system shall provide an ability to produce a source term along a line.

    Specification(s): test

    Design: LineSourceRayKernel

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 13.7.13The system shall provide an ability to solve a 2D diffusion problem with a line source term, with
    1. finite elements
    2. and finite volumes.

    Specification(s): simple_diffusion/fe, simple_diffusion/fv

    Design: LineSourceRayKernel

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 13.7.14The system shall provide the ability to compute the integral of a material property along a line.

    Specification(s): test

    Design: MaterialIntegralRayKernel

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.7.15The system shall provide the ability to compute the average value of a material property along a line.

    Specification(s): average

    Design: MaterialIntegralRayKernel

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.7.16The system shall be able to store the distance traversed by a ray in each element in an auxiliary field.

    Specification(s): test

    Design: RayDistanceAux

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 13.7.17The system shall throw a reasonable error if a RayKernel
    1. is utilized with a coordinate system other than xyz or
    2. if the execute flag for the associated ray study is not set correctly to use the RayKernel.

    Specification(s): errors/xyz_only, errors/bad_execute_on

    Design: RayKernel

    Issue(s): #16028

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 13.7.18The system shall provide the ability to compute the integral of a variable along a line.

    Specification(s): test

    Design: VariableIntegralRayKernel

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.7.19The system shall provide the ability to compute the average value of a variable along a line.

    Specification(s): average

    Design: VariableIntegralRayKernel

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.7.20The system shall provide the ability to output the segment wise accumulated integral of a variable along a line with a 2D, finite-element diffusion problem.

    Specification(s): simple_diffusion_rays

    Design: VariableIntegralRayKernelRayTracingMeshOutput

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 13.7.21The system shall provide the ability to output the segment wise, linearly approximated, accumulated integral of a variable along a line with a 2D, finite-element diffusion problem.

    Specification(s): simple_diffusion_rays_nodal

    Design: VariableIntegralRayKernelRayTracingMeshOutput

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 13.7.22The system shall provide the ability to compute the line integral of a variable for a 2D diffusion problem, with
    1. finite elements
    2. and finite volumes.

    Specification(s): simple_diffusion/fe, simple_diffusion/fv

    Design: VariableIntegralRayKernel

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • ray_tracing: Traceray
  • 13.9.1The system shall be able to trace rays in a mesh that utilizes adaptiviy with the element types
    1. QUAD4,
    2. TRI3,
    3. HEX8,
    4. and EDGE2.

    Specification(s): elem_tests/quad4, elem_tests/tri3, elem_tests/hex8, elem_tests/edge2

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.2The system shall support the use of side normals to cull potential exiting sides within ray tracing for
    1. two-dimensional meshes
    2. and for three-dimensional meshes.

    Specification(s): dim/2d, dim/3d

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.3The system shall be able to trace rays within EDGE2 elements.

    Specification(s): test

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.4The system shall be able to trace rays within EDGE3 elements.

    Specification(s): test

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.5The system shall be able to trace rays within EDGE4 elements.

    Specification(s): test

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.6The system shall be able to trace rays within planar HEX20 elements
    1. from boundary vertices on boundary sides in the direction of the vertices on the other side of the same boundary element,
    2. from the centroids of boundary sides in the direction of all other vertices in the same boundary element,
    3. from the centroids of all boundary sides to the centroids of all other boundary elements,
    4. from the centroids of boundary edges in the direction of all other edge centroids in the same element,
    5. from boundary sides centroids using an angular quadrature,
    6. and from boundary element centroids using an angular quadrature.

    Specification(s): tests/vtv, tests/ctv, tests/ctc, tests/ete, tests/side_aq, tests/centroid_aq

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.7The system shall be able to trace rays within planar HEX27 elements
    1. from boundary vertices on boundary sides in the direction of the vertices on the other side of the same boundary element,
    2. from the centroids of boundary sides in the direction of all other vertices in the same boundary element,
    3. from the centroids of all boundary sides to the centroids of all other boundary elements,
    4. from the centroids of boundary edges in the direction of all other edge centroids in the same element,
    5. from boundary sides centroids using an angular quadrature,
    6. and from boundary element centroids using an angular quadrature.

    Specification(s): tests/vtv, tests/ctv, tests/ctc, tests/ete, tests/side_aq, tests/centroid_aq

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.8The system shall be able to trace rays within planar HEX8 elements
    1. from boundary vertices on boundary sides in the direction of the vertices on the other side of the same boundary element,
    2. from the centroids of boundary sides in the direction of all other vertices in the same boundary element,
    3. from the centroids of all boundary sides to the centroids of all other boundary elements,
    4. from the centroids of boundary edges in the direction of all other edge centroids in the same element,
    5. from boundary sides centroids using an angular quadrature,
    6. and from boundary element centroids using an angular quadrature.

    Specification(s): tests/vtv, tests/ctv, tests/ctc, tests/ete, tests/side_aq, tests/centroid_aq

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.9The system shall support the ending of traced rays on internal sidesets in
    1. one-dimensional meshes,
    2. two-dimensional meshes,
    3. and three-dimensional meshes.

    Specification(s): kill/1d, kill/2d, kill/3d

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.10The system shall support the specular reflection of traced rays on internal sidesets in
    1. one-dimensional meshes,
    2. two-dimensional meshes,
    3. and three-dimensional meshes.

    Specification(s): reflect/1d, reflect/2d, reflect/3d

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

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

  • 13.9.13The system shall be able to trace rays on 3D meshes that have nonplanar faces.

    Specification(s): test

    Design: RayTracingStudy

    Issue(s): #16028#16170

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

  • 13.9.15The system shall be able to trace rays within planar PRISM15 elements
    1. from boundary vertices on boundary sides in the direction of the vertices on the other side of the same boundary element,
    2. from the centroids of boundary sides in the direction of all other vertices in the same boundary element,
    3. from the centroids of all boundary sides to the centroids of all other boundary elements,
    4. from the centroids of boundary edges in the direction of all other edge centroids in the same element,
    5. from boundary sides centroids using an angular quadrature,
    6. and from boundary element centroids using an angular quadrature.

    Specification(s): tests/vtv, tests/ctv, tests/ctc, tests/ete, tests/side_aq, tests/centroid_aq

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.16The system shall be able to trace rays within planar PRISM18 elements
    1. from boundary vertices on boundary sides in the direction of the vertices on the other side of the same boundary element,
    2. from the centroids of boundary sides in the direction of all other vertices in the same boundary element,
    3. from the centroids of all boundary sides to the centroids of all other boundary elements,
    4. from the centroids of boundary edges in the direction of all other edge centroids in the same element,
    5. from boundary sides centroids using an angular quadrature,
    6. and from boundary element centroids using an angular quadrature.

    Specification(s): tests/vtv, tests/ctv, tests/ctc, tests/ete, tests/side_aq, tests/centroid_aq

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.17The system shall be able to trace rays within planar PRISM6 elements
    1. from boundary vertices on boundary sides in the direction of the vertices on the other side of the same boundary element,
    2. from the centroids of boundary sides in the direction of all other vertices in the same boundary element,
    3. from the centroids of all boundary sides to the centroids of all other boundary elements,
    4. from the centroids of boundary edges in the direction of all other edge centroids in the same element,
    5. from boundary sides centroids using an angular quadrature,
    6. and from boundary element centroids using an angular quadrature.

    Specification(s): tests/vtv, tests/ctv, tests/ctc, tests/ete, tests/side_aq, tests/centroid_aq

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.18The system shall be able to trace rays within planar PYRAMID13 elements
    1. from boundary vertices on boundary sides in the direction of the vertices on the other side of the same boundary element,
    2. from the centroids of boundary sides in the direction of all other vertices in the same boundary element,
    3. from the centroids of all boundary sides to the centroids of all other boundary elements,
    4. from the centroids of boundary edges in the direction of all other edge centroids in the same element,
    5. from boundary sides centroids using an angular quadrature,
    6. and from boundary element centroids using an angular quadrature.

    Specification(s): tests/vtv, tests/ctv, tests/ctc, tests/ete, tests/side_aq, tests/centroid_aq

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.19The system shall be able to trace rays within planar PYRAMID14 elements
    1. from boundary vertices on boundary sides in the direction of the vertices on the other side of the same boundary element,
    2. from the centroids of boundary sides in the direction of all other vertices in the same boundary element,
    3. from the centroids of all boundary sides to the centroids of all other boundary elements,
    4. from the centroids of boundary edges in the direction of all other edge centroids in the same element,
    5. from boundary sides centroids using an angular quadrature,
    6. and from boundary element centroids using an angular quadrature.

    Specification(s): tests/vtv, tests/ctv, tests/ctc, tests/ete, tests/side_aq, tests/centroid_aq

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.20The system shall be able to trace rays within planar PYRAMID5 elements
    1. from boundary vertices on boundary sides in the direction of the vertices on the other side of the same boundary element,
    2. from the centroids of boundary sides in the direction of all other vertices in the same boundary element,
    3. from the centroids of all boundary sides to the centroids of all other boundary elements,
    4. from the centroids of boundary edges in the direction of all other edge centroids in the same element,
    5. from boundary sides centroids using an angular quadrature,
    6. and from boundary element centroids using an angular quadrature.

    Specification(s): tests/vtv, tests/ctv, tests/ctc, tests/ete, tests/side_aq, tests/centroid_aq

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.21The system shall be able to trace rays within planar QUAD4 elements
    1. from boundary vertices on boundary sides in the direction of the vertices on the other side of the same boundary element,
    2. from the centroids of boundary sides in the direction of all other vertices in the same boundary element,
    3. from the centroids of all boundary sides to the centroids of all other boundary elements,
    4. from boundary sides centroids using an angular quadrature,
    5. and from boundary element centroids using an angular quadrature.

    Specification(s): tests/vtv, tests/ctv, tests/ctc, tests/side_aq, tests/centroid_aq

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.22The system shall be able to trace rays within planar QUAD8 elements
    1. from boundary vertices on boundary sides in the direction of the vertices on the other side of the same boundary element,
    2. from the centroids of boundary sides in the direction of all other vertices in the same boundary element,
    3. from the centroids of all boundary sides to the centroids of all other boundary elements,
    4. from boundary sides centroids using an angular quadrature,
    5. and from boundary element centroids using an angular quadrature.

    Specification(s): tests/vtv, tests/ctv, tests/ctc, tests/side_aq, tests/centroid_aq

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.23The system shall be able to trace rays within planar QUAD9 elements
    1. from boundary vertices on boundary sides in the direction of the vertices on the other side of the same boundary element,
    2. from the centroids of boundary sides in the direction of all other vertices in the same boundary element,
    3. from the centroids of all boundary sides to the centroids of all other boundary elements,
    4. from boundary sides centroids using an angular quadrature,
    5. and from boundary element centroids using an angular quadrature.

    Specification(s): tests/vtv, tests/ctv, tests/ctc, tests/side_aq, tests/centroid_aq

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

  • 13.9.25The system shall be able to trace rays within planar TET10 elements
    1. from boundary vertices on boundary sides in the direction of the vertices on the other side of the same boundary element,
    2. from the centroids of boundary sides in the direction of all other vertices in the same boundary element,
    3. from the centroids of all boundary sides to the centroids of all other boundary elements,
    4. from the centroids of boundary edges in the direction of all other edge centroids in the same element,
    5. from boundary sides centroids using an angular quadrature,
    6. and from boundary element centroids using an angular quadrature.

    Specification(s): tests/vtv, tests/ctv, tests/ctc, tests/ete, tests/side_aq, tests/centroid_aq

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.26The system shall be able to trace rays within planar TET4 elements
    1. from boundary vertices on boundary sides in the direction of the vertices on the other side of the same boundary element,
    2. from the centroids of boundary sides in the direction of all other vertices in the same boundary element,
    3. from the centroids of all boundary sides to the centroids of all other boundary elements,
    4. from the centroids of boundary edges in the direction of all other edge centroids in the same element,
    5. from boundary sides centroids using an angular quadrature,
    6. and from boundary element centroids using an angular quadrature.

    Specification(s): tests/vtv, tests/ctv, tests/ctc, tests/ete, tests/side_aq, tests/centroid_aq

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.27The system shall be able to trace rays within planar TRI3 elements
    1. from boundary vertices on boundary sides in the direction of the vertices on the other side of the same boundary element,
    2. from the centroids of boundary sides in the direction of all other vertices in the same boundary element,
    3. from the centroids of all boundary sides to the centroids of all other boundary elements,
    4. from boundary sides centroids using an angular quadrature,
    5. and from boundary element centroids using an angular quadrature.

    Specification(s): tests/vtv, tests/ctv, tests/ctc, tests/side_aq, tests/centroid_aq

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.28The system shall be able to trace rays within planar TRI6 elements
    1. from boundary vertices on boundary sides in the direction of the vertices on the other side of the same boundary element,
    2. from the centroids of boundary sides in the direction of all other vertices in the same boundary element,
    3. from the centroids of all boundary sides to the centroids of all other boundary elements,
    4. from boundary sides centroids using an angular quadrature,
    5. and from boundary element centroids using an angular quadrature.

    Specification(s): tests/vtv, tests/ctv, tests/ctc, tests/side_aq, tests/centroid_aq

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 13.9.29The system shall support not setting the incoming side at the beginning of a trace.

    Specification(s): test

    Design: RayTracingStudy

    Issue(s): #16028

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

Usability Requirements

Performance Requirements

System Interface Requirements

References

No citations exist within this document.