Reconstructed Discontinuous Galerkin 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 Reconstructed Discontinuous Galerkin module.

Introduction

Minimum System Requirements

In general, the following is required for MOOSE-based development:

A POSIX compliant Unix-like operating system. This includes any modern Linux-based operating system (e.g., Ubuntu, Fedora, Rocky, etc.), or a Macintosh machine running either of the last two MacOS releases.

HardwareInformation
CPU Architecturex86_64, ARM (Apple Silicon)
Memory8 GB (16 GBs for debug compilation)
Disk Space30GB

LibrariesVersion / Information
GCC9.0.0 - 12.2.1
LLVM/Clang10.0.1 - 19
Intel (ICC/ICX)Not supported at this time
Python3.10 - 3.13
Python Packagespackaging pyaml jinja2

System Purpose

The MOOSE rDG module is a library for the implementation of simulation tools that solve convection-dominated problems using the class of so-called reconstructed discontinuous Galerkin (rDG) methods. The specific rDG method implemented in this module is rDG(P0P1), which is equivalent to the second-order cell-centered finite volume method (FVM). Cell-centered FVMs are regarded as a subset of rDG methods in the case when the baseline polynomial solution in each element is a constant monomial. The FVMs are the most widely used numerical methods in areas such as computational fluid dynamics (CFD) and heat transfer, computational acoustics, and magnetohydrodynamics (MHD).

System Scope

The purpose of this software is to provide capability to MOOSE-based applications to use a second-order, cell-centered finite volume method (FVM). This module provides a systematic solution for implementing all required components in a second-order FVM such as slope reconstruction, slope limiting, numerical flux, and proper boundary conditions. Additionally, this module provides an implementation of these components for the scalar advection equation.

Assumptions and Dependencies

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

Changelog Issue Revisions

Errors in changelog references can sometimes occur as a result of typos or conversion errors. If any need to be noted by the development team, they will be noted here.

The changelog for all code residing in the MOOSE repository is located in the MOOSE RTM.

System Requirements Traceability

Functional Requirements

  • rdg: Auxkernels
  • 10.1.1The system shall be able compute a component of the negative gradient of a variable.

    Specification(s): test

    Design: NegativeVariableGradientComponent

    Issue(s): #62

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: Kernels
  • 10.3.1The system shall be able to solve a simple diffusion problem.

    Specification(s): test

    Design: Diffusion

    Issue(s): #108

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: Raybcs
  • 10.4.1The system shall be capable of reflecting computational particles off of boundaries and maintain consistent velocity data
    1. in a 1D domain
    2. in a 2D domain
    3. in a 3D domain

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

    Design: ReflectParticleBC

    Issue(s): #39

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • rdg: Utils
  • 10.6.1The system shall support the accumulation of point values as if they were point sources into an auxiliary field

    Specification(s): test

    Design: AuxAccumulator

    Issue(s): #9

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 10.6.2The system shall report a reasonable error when accumulating point values into an auxiliary field when the system is not properly finalized

    Specification(s): error

    Design: AuxAccumulator

    Issue(s): #9

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 10.6.3The system shall support mapping data from rays to an aux variable and reset the aux variable to 0 on each time step

    Specification(s): charge_mapping

    Design: AuxAccumulator

    Issue(s): #9

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 10.6.4The system shall support mapping data from rays to an aux variable and reset the aux variable to 0 on each time step on a 2 dimensional mesh

    Specification(s): charge_mapping2D

    Design: AuxAccumulator

    Issue(s): #9

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 10.6.5The system shall support mapping data from rays to an aux variable and then solve differential equations based on the data mapped from rays

    Specification(s): simple_potential_solve_aux

    Design: AuxAccumulator

    Issue(s): #9

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 10.6.6The system shall support the accumulation of point values as if they were point sources into a nonlinear field

    Specification(s): test

    Design: ResidualAccumulator

    Issue(s): #16

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 10.6.7The system shall allow a ray to sample the value of field variable at any point in space as it moves through space

    Specification(s): variable_sampling

    Design: VariableSampler

    Issue(s): #12

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

Usability Requirements

No requirements of this type exist for this application, beyond those of its dependencies.

Performance Requirements

No requirements of this type exist for this application, beyond those of its dependencies.

System Interface Requirements

No requirements of this type exist for this application, beyond those of its dependencies.

References

No citations exist within this document.