MALAMUTE 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 MALAMUTE application.

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 purpose of MALAMUTE is to serve as a simulation platform and library for a variety of advanced manufacturing (AM) processes and to connect the microscale characteristics and evolution of materials with their engineering-scale, post-manufacture performance. MALAMUTE currently simulates several main AM processes, including: EFAS (also known as SPS), directed energy deposition, and surface melting. MALAMUTE's main goal is to bring together the combined multiphysics capabilities of the MOOSE ecosystem to provide an open platform for future research in novel materials development and AM technologies.

System Scope

MALAMUTE performs simulations related to AM processes. These models often include highly coupled systems of equations related to heat conduction, electromagnetics, Navier Stokes, mechanics, and surface morphology, amongst others. Material models are also included to support these simulations (such as graphite and stainless steel), and they themselves are often dependent on simulation variables: temperature, electromagnetic field strength, stress/strain, etc. While many models within MALAMUTE are performed at the "engineering scale" (i.e., at the scale of centimeters and meters), the MultiApp System can be leveraged to allow for multiscale coupling to the micro- and nano-scale of a given experiment. This allows for not only experimental process design and evaluation at the operator level but also evaluation of a process on the formation of a part and the experiment's end result.

In addition to modeling full experiments (like in EFAS), MALAMUTE also contains building blocks for use in larger manufacturing models or as individual studies, such as directed energy deposition and laser welding (with surface deformation and melting). Mechanics models for pressing procedures are also under development.

Assumptions and Dependencies

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

errorerror:Missing Template Item: "log-revisions"

If errors are found in issue references related to the changelog (e.g., commit history), these should be noted here. The commit in which the incorrect issue reference occurs should be listed, and the correct issue should be added alongside each entry. Relevant links to all items are required. An example of this is shown below:

MOOSE CommitIncorrect Referenced IssueCorrect Referenced Issue
48db61idaholab/sockeye#19845idaholab/sockeye#130

The document must include the "log-revisions" template item, this can be included by adding the following to the markdown file (sqa/malamute_rtm.md):

!template! item key=log-revisions
Include text (in MooseDocs format) regarding the "log-revisions" template item here.
!template-end!

System Requirements Traceability

Functional Requirements

  • malamute: Interfacekernels
  • 2.7.1The system shall support the calculation of heat transfer across an interface due to thermal conductivity and electrostatic joule heating for the case of low thermal contact conductance and low electrical contact conductance.

    Specification(s): low_low

    Design: ThermalContactCondition

    Issue(s): #10

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.7.2The system shall support the calculation of heat transfer across an interface due to thermal conductivity and electrostatic joule heating for the case of low thermal contact conductance and high electrical contact conductance.

    Specification(s): low_high

    Design: ThermalContactCondition

    Issue(s): #10

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.7.3The system shall support the calculation of heat transfer across an interface due to thermal conductivity and electrostatic joule heating for the case of high thermal contact conductance and low electrical contact conductance.

    Specification(s): high_low

    Design: ThermalContactCondition

    Issue(s): #10

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.7.4The system shall support the calculation of heat transfer across an interface due to thermal conductivity and electrostatic joule heating for the case of high thermal contact conductance and high electrical contact conductance.

    Specification(s): high_high

    Design: ThermalContactCondition

    Issue(s): #10

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.7.5The system shall support the calculation of heat transfer across an interface due to thermal conductivity and electrostatic joule heating with the correct jacobian.

    Specification(s): jacobian

    Design: ThermalContactCondition

    Issue(s): #13#14

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

    Prerequisite(s): 2.7.12.7.22.7.32.7.4

  • 2.7.6The system shall support error-generation when the user supplies both conductances and mean hardness values (to calculate a conductance) to calculate thermal conductivity across an interface.

    Specification(s): conductance_error

    Design: ThermalContactCondition

    Issue(s): #13

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

    Prerequisite(s): 2.7.12.7.22.7.32.7.4

  • 2.7.7The system shall support the calculation of thermal and electrical conductances when determining the heat transfer across an interface due to thermal conductivity and electrostatic joule heating.

    Specification(s): conductance_calculated

    Design: ThermalContactCondition

    Issue(s): #13

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.7.8The system shall calculate the correct thermal contact temperature solution when compared to an analytic result, given a one-dimensional, two-material-block scenario.

    Specification(s): analytic_solution_test

    Design: ThermalContactCondition

    Issue(s): #13

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Verification: Thermal Contact Condition Verification Case

  • malamute: Melt Pool Heat
  • 2.11.1The system shall compute laser heat source and heat loss due to convection and radiation at the level set interface.

    Specification(s): heat

    Design: Melt pool heat source

    Issue(s): #2

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.11.2The system shall compute thermal properties in gas and mushy zone phases.

    Specification(s): thermal_material

    Design: Level set thermal materialMushy zone material

    Issue(s): #2

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • malamute: Melt Pool Mass
  • 2.13.1The system shall evolve the level set variable field with the velocity due to the powder addition.

    Specification(s): mass

    Design: LevelSetPowderAddition

    Issue(s): #35

    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.