TMAP8 System Design Description

This template follows INL template TEM-140, "IT System Design Description."

Introduction

Many of the phenomena related to tritium transport depend on the solutions of multiple physics models, which can be described by partial differential equations that provide spatially- and temporally-varying values of solution variables. These models for individual physics often depend on each other. TMAP8 relies on the MOOSE framework to solve these physics models, accounting for the couplings that may occur between them. This document describes the system design of TMAP8.

System Purpose

The Software Design Description provided here is description of each object in the system. The pluggable architecture of the underlying framework of TMAP8 makes MOOSE and MOOSE-based applications straightforward to develop as each piece of end-user (developer) code that goes into the system follows a well-defined interface for the underlying systems that those object plug into. These descriptions are provided through developer-supplied "markdown" files that are required for all new objects that are developed as part of TMAP8. More information about the design documentation for MOOSE-based applications like TMAP8 can be found in Documenting MOOSE.

System Scope

TMAP8 is an application for performing system-level, engineering scale (i.e., at the scale of centimeters and meters), and microstructure-scale (i.e., at the scale of microns) mass and thermal transport calculations related to tritium migration. These models often include highly coupled systems of equations related to heat conduction, scalar transport, thermal hydraulics, and mechanics, amongst others. Material models are also included to support these simulations, and they themselves are often dependent on simulation variables: temperature, irradiation flux, etc. While many models within TMAP8 are performed at the system-level or engineering scale, the MultiApp System can be leveraged to allow for multiscale coupling to the micro- and nano-scale species behavior. This allows for higher fidelity modeling.

Dependencies and Limitations

TMAP8 inherits the software dependencies of the MOOSE framework, with no additional dependencies.

Definitions and Acronyms

This section defines, or provides the definition of, all terms and acronyms required to properly understand this specification.

Definitions

  • Pull (Merge) Request: A proposed change to the software (e.g. usually a code change, but may also include documentation, requirements, design, and/or testing).

  • Baseline: A specification or product (e.g., project plan, maintenance and operations (M&O) plan, requirements, or design) that has been formally reviewed and agreed upon, that thereafter serves as the basis for use and further development, and that can be changed only by using an approved change control process (NQA-1, 2009).

  • Validation: Confirmation, through the provision of objective evidence (e.g., acceptance test), that the requirements for a specific intended use or application have been fulfilled (24765:2010(E), 2010).

  • Verification: (1) The process of: evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase. (2) Formal proof of program correctness (e.g., requirements, design, implementation reviews, system tests) (24765:2010(E), 2010).

Acronyms

AcronymDescription
APIApplication Programming Interface
DOEDepartment of Energy
FEfinite element
HITHierarchical Input Text
HPCHigh Performance Computing
I/OInput/Output
INLIdaho National Laboratory
MOOSEMultiphysics Object Oriented Simulation Environment
MPIMessage Passing Interface
SDDSoftware Design Description

Design Stakeholders and Concerns

Design Stakeholders

Stakeholders for TMAP8 include several of the funding sources including DOE and INL. However, since TMAP8 is an open-source project, several universities, companies, and foreign governments have an interest in the development and maintenance of the TMAP8 project.

Stakeholder Design Concerns

Concerns from many of the stakeholders are similar. These concerns include correctness, stability, and performance. The mitigation plan for each of these can be addressed. For correctness, TMAP8 development requires either regression or unit testing for all new code added to the repository. The project contains several comparisons against analytical solutions where possible and also other verification methods such as MMS. For stability, TMAP8 maintains multiple branches to incorporate several layers of testing both internally and for dependent applications. Finally, performance tests are also performed as part of the the normal testing suite to monitor code change impacts to performance.

System Design

TMAP8 relies on MOOSE to solve the coupled physics models underlying tritium transport, accounting for the couplings that may occur between them. The design of MOOSE is based on the concept of modular code objects that define all of the aspects of the physics model. TMAP8 follows this design, providing code objects that define specific aspects of the solutions for its physics that derive from the base classes defined by the MOOSE framework and the modules that it depends on.

TMAP8 provides specialized Kernel classes that compute the contributions from the terms in the partial differential equations for heat conduction, tritium diffusion, surface reactions, and other phenomena. It also provides specialized Material classes that define the constitutive behavior of materials of interest for diffusion, solubility, trapping, resolution, reactivity, permeation, and other physical properties. In addition, it provides miscellaneous BC and InterfaceKernel classes to facilitate various aspects of these simulations, such as plasma exposure, surface reactions, and transfer of species across enclosures, among others. Much of the functionality of TMAP8 is provided by the MOOSE modules that it builds on.

System Structure

TMAP8 relies on the MOOSE framework to provide the core functionality of solving multiphysics problems using the finite element method. It also relies on the MOOSE modules for much of its core functionality. A summary listing of the current modules required for complete TMAP8 operation are shown below:

The structure of TMAP8 is based on defining C++ classes that derive from classes in the MOOSE framework or modules that provide functionality that is specifically tailored to tritium migration problems. By using the interfaces defined in MOOSE base classes for these classes, TMAP8 is able to rely on MOOSE to execute these models at the appropriate times during the simulation and use their results in the desired ways.

Data Design and Control

At a high level, the system is designed to process HIT input files to construct several objects that will constitute an FE simulation. Some of the objects in the simulation may in turn load other file-based resources to complete the simulation. Examples include meshes or data files. The system will then assemble systems of equations and solve them using the libraries of the Code Platform. The system can then output the solution in one or more supported output formats commonly used for visualization.

Human-Machine Interface Design

The TMAP8 application is a command-line driven program. All interaction with TMAP8 is ultimately done through the command line. This is typical for HPC applications that use the MPI interface for running on super computing clusters. Optional GUIs may be used to assist in creating input files and launching executables on the command line.

System Design Interface

All external system interaction is performed either through file I/O or through local API calls. Neither TMAP8, nor the MOOSE framework, nor the MOOSE modules are designed to interact with any external system directly through remote procedure calls. Any code to code coupling performed using the framework are done directly through API calls either in a static binary or after loading shared libraries.

Security Structure

The TMAP8 application does not require any elevated privileges to operate and does not run any stateful services, daemons or other network programs. Distributed runs rely on the MPI library.

Requirements Cross-Reference

  • tmap8: Diffusion
  • 18.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

  • tmap8: AuxAccumulator
  • 18.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

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

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

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

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

  • tmap8: ResidualAccumulator
  • 18.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

  • tmap8: VariableSampler
  • 18.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

References

  1. ISO/IEC/IEEE 24765:2010(E). Systems and software engineering—Vocabulary. first edition, December 15 2010.[BibTeX]
  2. ASME NQA-1. ASME NQA-1-2008 with the NQA-1a-2009 addenda: Quality Assurance Requirements for Nuclear Facility Applications. first edition, August 31 2009.[BibTeX]

ActionComponents

Adaptivity

Adaptivity/Indicators

Adaptivity/Markers

Application

AuxKernels

AuxKernels/MatVecRealGradAuxKernel

AuxKernels/MaterialVectorAuxKernel

AuxKernels/MaterialVectorGradAuxKernel

AuxScalarKernels

AuxVariables

AuxVariables/MultiAuxVariables

BCs

BCs/CavityPressure

BCs/CoupledPressure

BCs/InclinedNoDisplacementBC

BCs/Periodic

BCs/Pressure

Bounds

Cardinal

Cardinal/ICs

Cardinal/ICs/BulkEnergyConservation

Cardinal/ICs/VolumetricHeatSource

ChainControls

ChemicalComposition

Closures

Components

Constraints

ControlLogic

Controls

Convergence

Correctors

CoupledHeatTransfers

Covariance

DGKernels

Dampers

Debug

Debug/MaterialDerivativeTest

DeprecatedBlock

DiracKernels

Distributions

DomainIntegral

Executioner

Executioner/Adaptivity

Executioner/Predictor

Executioner/Quadrature

Executioner/TimeIntegrator

Executioner/TimeIntegrators

Executioner/TimeStepper

Executioner/TimeSteppers

Executors

FVBCs

FVICs

FVInterfaceKernels

FVKernels

FluidProperties

FluidPropertiesInterrogator

Functions

FunctorMaterials

GlobalParams

GrayDiffuseRadiation

HDGKernels

HeatStructureMaterials

ICs

ICs/PolycrystalICs

ICs/PolycrystalICs/BicrystalBoundingBoxIC

ICs/PolycrystalICs/BicrystalCircleGrainIC

ICs/PolycrystalICs/PolycrystalColoringIC

ICs/PolycrystalICs/PolycrystalRandomIC

ICs/PolycrystalICs/PolycrystalVoronoiVoidIC

ICs/PolycrystalICs/Tricrystal2CircleGrainsIC

InterfaceKernels

Kernels

Kernels/CHPFCRFFSplitKernel

Kernels/DynamicSolidMechanics

Kernels/DynamicTensorMechanics

Kernels/HHPFCRFFSplitKernel

Kernels/PFCRFFKernel

Kernels/PolycrystalElasticDrivingForce

Kernels/PolycrystalKernel

Kernels/PolycrystalStoredEnergy

Kernels/PoroMechanics

Kernels/RigidBodyMultiKernel

Kernels/SolidMechanics

Kernels/TensorMechanics

Likelihood

LinearFVBCs

LinearFVKernels

Materials

Mesh

Mesh/BatchMeshGeneratorAction

Mesh/Partitioner

MeshDivisions

MeshModifiers

Modules

Modules/CompressibleNavierStokes

Modules/FluidProperties

Modules/HeatTransfer

Modules/HeatTransfer/ThermalContact

Modules/HeatTransfer/ThermalContact/BC

Modules/IncompressibleNavierStokes

Modules/NavierStokesFV

Modules/PhaseField

Modules/PhaseField/Conserved

Modules/PhaseField/DisplacementGradients

Modules/PhaseField/EulerAngles2RGB

Modules/PhaseField/GrainGrowth

Modules/PhaseField/GrainGrowthLinearizedInterface

Modules/PhaseField/GrandPotential

Modules/PhaseField/Nonconserved

Modules/SolidProperties

Modules/TensorMechanics

Modules/TensorMechanics/CohesiveZoneMaster

Modules/TensorMechanics/DynamicMaster

Modules/TensorMechanics/GeneralizedPlaneStrain

Modules/TensorMechanics/GlobalStrain

Modules/TensorMechanics/LineElementMaster

Modules/TensorMechanics/Master

Modules/TensorMechanics/MaterialVectorBodyForce

MortarGapHeatTransfer

MultiApps

NEML2

NodalKernels

NodalNormals

Outputs

ParameterStudy

Physics

Physics/Diffusion

Physics/Diffusion/ContinuousGalerkin

Physics/Diffusion/FiniteVolume

Physics/HeatConduction

Physics/HeatConduction/FiniteElement

Physics/HeatConduction/FiniteVolume

Physics/MultiSpeciesDiffusion

Physics/MultiSpeciesDiffusion/ContinuousGalerkin

Physics/NavierStokes

Physics/NavierStokes/Flow

Physics/NavierStokes/FlowSegregated

Physics/NavierStokes/FluidHeatTransfer

Physics/NavierStokes/FluidHeatTransferSegregated

Physics/NavierStokes/ScalarTransport

Physics/NavierStokes/ScalarTransportSegregated

Physics/NavierStokes/SolidHeatTransfer

Physics/NavierStokes/Turbulence

Physics/NavierStokes/TwoPhaseMixture

Physics/NavierStokes/TwoPhaseMixtureSegregated

Physics/SolidMechanics

Physics/SolidMechanics/CohesiveZone

Physics/SolidMechanics/Dynamic

Physics/SolidMechanics/GeneralizedPlaneStrain

Physics/SolidMechanics/GlobalStrain

Physics/SolidMechanics/LineElement

Physics/SolidMechanics/LineElement/QuasiStatic

Physics/SolidMechanics/MaterialVectorBodyForce

Physics/SolidMechanics/QuasiStatic

Positions

Postprocessors

Preconditioning

Problem

Problem/Filters

Problem/MGXS

Problem/Tallies

ProjectedStatefulMaterialStorage

QuadInterWrapperMesh

QuadSubChannelMesh

RayBCs

RayKernels

ReactionNetwork

ReactionNetwork/AqueousEquilibriumReactions

ReactionNetwork/SolidKineticReactions

Reporters

Samplers

ScalarKernels

SolidProperties

StochasticTools

SubChannel

Surrogates

ThermalContact

Times

Trainers

Transfers

TriInterWrapperMesh

TriSubChannelMesh

UserObjects

VariableMappings

Variables

Variables/CHPFCRFFSplitVariables

Variables/HHPFCRFFSplitVariables

Variables/PFCRFFVariables

Variables/PolycrystalVariables

VectorPostprocessors