TMAP8 System Requirements Specification

System Purpose

The purpose of TMAP8 is to simulate tritium transport and inventory at different length scales in a variety of materials and designs. TMAP8's main goal is to bring together the combined multiphysics capabilities of the MOOSE ecosystem to provide an open platform for future research, safety assessment, and design studies of tritium transport.

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.

System Context

The TMAP8 application is command-line driven. Like MOOSE, this is typical for a high-performance software that is designed to run across several nodes of a cluster system. As such, all usage of the software is through any standard terminal program generally available on all supported operating systems. Similarly, for the purpose of interacting through the software, there is only a single user, "the user", which interacts with the software through the command-line. TMAP8 does not maintain any back-end database or interact with any system daemons. It is an executable, which may be launched from the command line and writes out various result files as it runs.

Figure 1: Usage of TMAP8 and other MOOSE-based applications.

System Functions

Since TMAP8 is a command-line driven application, all functionality provided in the software is operated through the use of standard UNIX command line flags and the extendable MOOSE input file. TMAP8 is completely extendable so individual design pages should be consulted for specific behaviors of each user-defined object.

User Characteristics

TMAP8 has three main classes of users:

• TMAP8 Developers: These are the core developers of TMAP8. They are responsible for designing, implementing, and maintaining the software, while following and enforcing its software development standards.

• Developers: These are scientists or engineers that modify or add capabilities to TMAP8 for their own purposes, which may include research or extending its capabilities. They will typically have a background in tritium transport and material science, and in modeling and simulation techniques, but may have more limited background in code development using the C++ language. In many cases, these developers will be encouraged to contribute code back to TMAP8.

• Analysts: These are users that run TMAP8 to run simulations, but do not develop code. The primary interface of these users with TMAP8 is the input files that define their simulations. These users may interact with developers of the system requesting new features and reporting bugs found.

Assumptions and Dependencies

The TMAP8 application is developed using MOOSE and is based on various modules, as such the SRS for TMAP8 is dependent upon the files listed at the beginning of this document. Any further assumptions or dependencies are outlined in the remainder of this section.

TMAP8 has no constraints on hardware and software beyond those of the MOOSE framework and modules listed in their respective SRS documents, which are accessible through the links at the beginning of this document.

TMAP8 provides access to a number of code objects that perform computations, such as material behavior and boundary conditions. These objects each make their own physics-based assumptions, such as the units of the inputs and outputs. Those assumptions are described in the documentation for those individual objects.

Definitions

• 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

Functional Requirements

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

• tmap8: Benchmarking
• 18.2.1The system shall be capable of solving an ion wall loss problem, as described in chapter 1, pages 26-27 of Principles of Plasma Discharge and Material Processing (ISBN 0-471-72001-1), and reproduce the same
  1. field variable results, and
  2. kinetic particle results.

• tmap8: Kernels
• 18.3.1The system shall be able to solve a simple diffusion problem.

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

• tmap8: Userobjects
• 18.5.1The system shall support placing particles within a bounding box uniformly in a parallel consistent manner in the element type
  1. EDGE2
  2. TRI3
  3. QUAD4
  4. HEX8
  5. TET4
  6. PYRAMID5
  7. PRISM6
• 18.5.2The system return a useful error when the user
  1. requests an element type that initialization has not been verified for
  2. tries to setup a bounding box where a component of bottom_left is greater than top_right
• 18.5.3The system return a useful warning to remind the user that the
  1. 2 extra components of the bottom_left and top_right inputs are ignored in 1D simulations
  2. 1 extra component of the bottom_left and top_right inputs are ignored in 2D simulations
• 18.5.4The system shall be capable of placing particles inside of EDGE2 elements uniformly
  1. and solve an electrostatic potential based on the particle positions
  2. in a parallel consistent manner
  3. and compute the error between an exact electrostatic potential and the finite element solution
• 18.5.5The system shall be capable of placing particles inside of QUAD4 elements uniformly
  1. and solve an electrostatic potential based on the particle positions
  2. in a parallel consistent manner
  3. and compute the error between an exact electrostatic potential and the finite element solution
• 18.5.6The system shall be capable of placing particles inside of TRI3 elements uniformly
  1. and solve an electrostatic potential based on the particle positions
  2. in a parallel consistent manner
  3. and compute the error between an exact electrostatic potential and the finite element solution
• 18.5.7The system shall be capable of placing particles inside of HEX8 elements uniformly
  1. and solve an electrostatic potential based on the particle positions
  2. in a parallel consistent manner
  3. and compute the error between an exact electrostatic potential and the finite element solution
• 18.5.8The system shall be capable of placing particles inside of PRISM6 elements uniformly
  1. and solve an electrostatic potential based on the particle positions
  2. in a parallel consistent manner
  3. and compute the error between an exact electrostatic potential and the finite element solution
• 18.5.9The system shall be capable of placing particles inside of PYRAMID5 elements uniformly
  1. and solve an electrostatic potential based on the particle positions
  2. in a parallel consistent manner
  3. and compute the error between an exact electrostatic potential and the finite element solution
• 18.5.10The system shall be capable of placing particles inside of TET4 elements uniformly
  1. and solve an electrostatic potential based on the particle positions
  2. in a parallel consistent manner
  3. and compute the error between an exact electrostatic potential and the finite element solution
• 18.5.11The system return a useful error when the user
  1. requests an element type that initialization has not been verified for
  2. tries to give particles zero mass
  3. tries to give particles a negative mass
  4. does not provide enough distributions to sample for velocity initialization.
  5. tries to put 0 particles in each element.
  6. tries to request that a particle type be initialized with zero number density
  7. tries to request that a particle type be initialized with a negative number density
• 18.5.12The system shall be capable of placing particles on a uniform grid on the mesh
  1. in one dimension.
• 18.5.13The system shall return a useful error when the user tries to use the UniformGridParticleInitializer in
  1. a two-dimensional simulation, and
  2. a three-dimensional simulation.
• 18.5.14The system shall be capable of contributing to the residual of a variable based on the computational particles'
  1. charge density, and
  2. number density.
• 18.5.15The system shall be capable of accurately capturing the path of charged particles in both an electric and a magnetic field
• 18.5.16The system shall be capable of accurately capturing the path of charged particles in a perpendicular magnetic field
• 18.5.17The system shall be capable of applying a linear impluse from a force field perpendicular to a particles initial velocity using the boris stepper when there is 0 magnetic field
• 18.5.18The system shall be capable of applying a linear impluse from a force field parallel to a particles velocity using the boris stepper when there is 0 magnetic field
• 18.5.19The system shall report a reasonable error from the particle stepper when
  1. the user does not provide 3 components of the electric field
  2. the user does not provide 3 components of the magnetic field
• 18.5.20The system shall be capable of applying a linear impulse from a force field perpendicular to a particle\'s initial velocity
• 18.5.21The system shall be capable of applying a linear impulse from a force field parallel to a particle's velocity
• 18.5.22The system shall report a reasonable error from the particle stepper when
  1. the user does not provide 3 components of the force field
• 18.5.23The system shall be capable of tracking 3 velocity components within the PIC capability while propagating rays in lower dimensions

• tmap8: Utils
• 18.6.1The system shall support the accumulation of point values as if they were point sources into an auxiliary field
• 18.6.2The system shall report a reasonable error when accumulating point values into an auxiliary field when the system is not properly finalized
• 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
• 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
• 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
• 18.6.6The system shall support the accumulation of point values as if they were point sources into a nonlinear field
• 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

Usability Requirements

Performance Requirements

System Interfaces

System Operations

System Modes and States

MOOSE applications normally run in normal execution mode when an input file is supplied. However, there are a few other modes that can be triggered with various command line flags as indicated here:

Physical Characteristics

The TMAP8 application is software only with no associated physical media. See System Requirements for a description of the minimum required hardware necessary for running the TMAP8 application.

Environmental Conditions

Not Applicable

System Security

MOOSE-based applications such as TMAP8 have no requirements or special needs related to system-security. The software is designed to run completely in user-space with no elevated privileges required nor recommended.

Information Management

TMAP8 as well as the core MOOSE framework in its entirety will be made publicly available on an appropriate repository hosting site. Day-to-day backups and security services will be provided by the hosting service. More information about backups of the public repository on INL-hosted services can be found on the following page: GitHub Backups

Polices and Regulations

MOOSE-based applications must comply with all export control restrictions.

System Life Cycle Sustainment

MOOSE-based development follows various agile methods. The system is continuously built and deployed in a piecemeal fashion since objects within the system are more or less independent. Every new object requires a test, which in turn requires an associated requirement and design description. The TMAP8 development team follows the NQA-1 standards.

Packaging, Handling, Shipping and Transportation

No special requirements are needed for packaging or shipping any media containing the MOOSE and TMAP8 source code. However, some MOOSE-based applications that use the TMAP8 code may be export-controlled, in which case all export control restrictions must be adhered to when packaging and shipping media.