Fluid Structure Interaction 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 Fluid Structure Interaction module.

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 @ 10.0.1 or greater)

    • Note: Intel compilers are not supported.

  • Memory: 8 GBs of RAM for optimized compilation (16 GBs for debug compilation), 2 GB per core execution

  • Processor: 64-bit x86 or ARM64 (specifically, Apple Silicon)

  • Disk: 30GB

  • A POSIX compliant Unix-like operating system, including the two most recent versions of MacOS and most current versions of Linux.

  • Git version control system

  • Python @ 3.7 or greater

System Purpose

The purpose of this software is to allow simulation of interfacial interactions between fluid and solid domains. Both acoustic and full Navier-Stokes models of the fluid domain are supported; small and finite strain models from the tensor mechanics module may be used for the solid domain.

System Scope

The MOOSE Fluid Structure Interaction module provides interface kernels for simulating the interactions between neighboring fluid and solid subdomains. It can be used as a standalone application or can be included in downstream applications interested in modeling fluid structure interactions.

Assumptions and Dependencies

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

  • fsi: 2D-Finite-Strain-Steady
  • 6.1.1The system shall be able to model fluid channel compression and solid expansion with a finite strain material model, which requires being able to evaluate stateful material properties on interfaces.

    Specification(s): test

    Design: Fluid-Structure Interaction Module

    Issue(s): #21900

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • fsi: 2D-Small-Strain-Transient
  • 6.2.1We shall be able to combine navier-stokes and tensor-mechanics simulation capabilities to do some basic fluid-structure interaction simulations and produce equivalent results when the Navier-Stokes equations are implemented using
    1. scalar field variables for velocity components and hand-coded Jacobians,
    2. and a vector field variable for velocity and a Jacobian computed using automatic differentation. Additionally,
    3. the automatic differentation Jacobian shall be (nearly) perfect when the fluid domain equations are run on the displaced mesh, and
    4. perfect when the fluid domain equations are run on the undisplaced mesh, and

    Specification(s): fsi/INS, fsi/INSAD, fsi/INSAD_displaced_jac, fsi/INSAD_undisplaced_jac

    Design: Fluid-Structure Interaction Module

    Issue(s): #12462

    Collection(s): FUNCTIONAL

    Type(s): ExodiffPetscJacobianTester

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.