Phase Field 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 Requirement Traceability Matrix (RTM) specific to the Phase Field application.

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

    • Note: Intel compilers are not supported.

  • Memory: 16 GBs (debug builds)

  • Processor: 64-bit x86

  • Disk: 30GB

System Purpose

The MOOSE is a tool for solving complex coupled Multiphysics equations using the finite element method. MOOSE uses an object-oriented design to abstract data structure management, parallelism, threading and compiling while providing an easy to use interface targeted at engineers that may not have a lot of software development experience. MOOSE will require extreme scalability and flexibility when compared to other FEM frameworks. For instance, MOOSE needs the ability to run extremely complex material models, or even third-party applications within a parallel simulation without sacrificing parallelism. This capability is in contrast to what is often seen in commercial packages, where custom material models can limit the parallel scalability, forcing serial runs in the most severe cases. When comparing high-end capabilities, many MOOSE competitors target modest-sized clusters with just a few thousand processing cores. MOOSE, however, will be required to routinely executed on much larger clusters with scalability to clusters available in the top 500 systems (top500.org). MOOSE will also be targeted at smaller systems such as high-end laptop computers.

The design goal of MOOSE is to give developers ultimate control over their physical models and applications. Designing new models or solving completely new classes of problems will be accomplished by writing standard C++ source code within the framework's class hierarchy. Scientists and engineers will be free to implement completely new algorithms using pieces of the framework where possible, and extending the framework's capabilities where it makes sense to do so. Commercial applications do not have this capability, and instead opt for either a more rigid parameter system or a limited application-specific metalanguage.

System Scope

MOOSE's scope is to provide a set of interfaces for building FEM simulations. Abstractions to all underlying libraries are provided.

Solving coupled problems where competing physical phenomena impact one and other in a significant nonlinear fashion represents a serious challenge to several solution strategies. Small perturbations in strongly-coupled parameters often have very large adverse effects on convergence behavior. These adverse effects are compounded as additional physics are added to a model. To overcome these challenges, MOOSE employs three distinct yet compatible systems for solving these types of problems.

First, an advanced numerical technique called the JFNK method is employed to solve the most fully-coupled physics in an accurate, consistent way. An example of this would be the effect of temperature on the expansion or contraction of a material. While the JFNK numerical method is very effective at solving fully-coupled equations, it can also be computationally expensive. Plus, not all physical phenomena in a given model are truly coupled to one another. For instance, in a reactor, the speed of the coolant flow may not have any direct effect on the complex chemical reactions taking place inside the fuel rods. We call such models "loosely-coupled". A robust, scalable system must strike the proper balance between the various modeling strategies to avoid performing unnecessary computations or incorrectly predicting behavior in situations such as these.

MOOSE's Multiapp system will allow modelers to group physics into logical categories where MOOSE can solve some groups fully-coupled and others loosely-coupled. The Multiapp system goes even further by also supporting a "tightly-coupled" strategy, which falls somewhere between the "fully-coupled" and "loosely-coupled" approaches. Several sets of physics can then be linked together into logical hierarchies using any one of these coupling strategies, allowing for several potential solution strategies. For instance, a complex nuclear reactor model might consist of several tightly-coupled systems of fully-coupled equations.

Finally, MOOSE's Transfers system ties all of the physics groups contained within the Multiapp system together and allows for full control over the flow of information among the various groups. This capability bridges physical phenomena from several different complementary scales simultaneously. When these three MOOSE systems are combined, myriad coupling combinations are possible. In all cases, the MOOSE framework handles the parallel communication, input, output and execution of the underlying simulation. By handling these computer science tasks, the MOOSE framework keeps modelers focused on doing research.

MOOSE innovates by building advanced simulation capabilities on top of the very best available software technologies in a way that makes them widely accessible for innovative research. MOOSE is equally capable of solving small models on common laptops and the very biggest FEM models ever attempted—all without any major changes to configuration or source code. Since its inception, the MOOSE project has focused on both developer and computational efficiency. Improved developer efficiency is achieved by leveraging existing algorithms and technologies from several leading open-source packages. Additionally, MOOSE uses several complementary parallel technologies (both the distributed-memory message passing paradigm and shared-memory thread-based approaches are used) to lay an efficient computational foundation for development. Using existing open technologies in this manner helps the developers reduce the scope of the project and keeps the size of the MOOSE code base maintainable. This approach provides users with state-of-the-art finite element and solver technology as a basis for the advanced coupling and solution strategies mentioned previously.

MOOSE's developers work openly with other package developers to make sure that cutting-edge technologies are available through MOOSE, providing researchers with competitive research opportunities. MOOSE maintains a set of objects that hide parallel interfaces while exposing advanced spatial and temporal coupling algorithms in the framework. This accessible approach places developmental technology into the hands of scientists and engineers, which can speed the pace of scientific discovery.

Assumptions and Dependencies

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

System Requirements Traceability

Functional Requirements

  • phase_field: Chsplitchemicalpotential
  • 8.3.1

    Specification(s): simple_diffusion

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Deformedgrain
  • 8.4.1

    Specification(s): DeformedGrain

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Ebsdmeshgenerator
  • 8.5.1The system shall detect invalid or inconsistent EBSD file parameters
    1. if the EBSD data step size is zero,
    2. if the EBSD grid size is zero,
    3. if the EBSD data is zero dimensional,
    4. if the requested pre_refine levels are not possible

    Specification(s): errors/zerostep, errors/zerosize, errors/zerodim, errors/norefine

    Design: EBSDMeshGenerator

    Issue(s): #19150

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • phase_field: Gbanisotropy
  • 8.6.1A material shall be provided to compute anisotropic grain boundary energies and mobilities.

    Specification(s): test1

    Design: GBAnisotropy

    Issue(s): #4580

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.6.2A material shall be provided to compute anisotropic grain boundary energies and mobilities.

    Specification(s): test2

    Design: GBAnisotropy

    Issue(s): #4580

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.6.3A material shall be provided to compute anisotropic grain boundary energies and mobilities with an inclination dependence.

    Specification(s): test3

    Design: GBAnisotropy

    Issue(s): #4580

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.6.4The anisotropic grain boundary system shall allow the user to specify grain boundary widths independently for each interface between grains.

    Specification(s): testwidth1

    Design: GBWidthAnisotropy

    Issue(s): #8079

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Grain Velocity Computation
  • 8.7.1The system shall be able to provide a velocity vector field indicating grain boundary movement for visualization purposes.

    Specification(s): GrainBoundaryVelocityTest

    Design: GrainBoundaryVelocity

    Issue(s): #14887

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Kks System
  • 8.9.1The Kim-Kim-Suzuki model implementation shall use free energy densities provided by DerivativeParsedMaterials

    Specification(s): derivative_parsed_material

    Design: DerivativeParsedMaterial

    Issue(s): #4835

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.9.2A non-split version of the Kim-Kim-Suzuki shall be provided

    Specification(s): kks_example

    Design: KKSCHBulk

    Issue(s): #4835

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.9.3A split version of the Kim-Kim-Suzuki shall be provided

    Specification(s): kks_example_split

    Design: KKSSplitCHCRes

    Issue(s): #4835

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.9.4The split version of the Kim-Kim-Suzuki shall be yield the correct results with asymmetric free energies

    Specification(s): kks_example_offset

    Design: KKSSplitCHCRes

    Issue(s): #10315

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.9.5A multi component Kim-Kim-Suzuki model shall be implemented

    Specification(s): kks_xevac

    Design: KKSSplitCHCRes

    Issue(s): #4879

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.9.6A multi component Kim-Kim-Suzuki model shall be implemented

    Specification(s): kks_multiphase

    Design: KKSMultiACBulkC

    Issue(s): #7007

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Maskedbodyforce
  • 8.10.1

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Multismoothcircleic
  • 8.12.1We shall be able to generate multiple smooth circle initial conditions with uniform radius variation type

    Specification(s): multi_test

    Design: MultiSmoothCircleIC

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.12.2We shall be able to generate multiple smooth circle initial conditions with normal radius variation type

    Specification(s): multi_normal_test

    Design: MultiSmoothCircleIC

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.12.3We shall be able to produce a lattice of smooth circle initial conditions, allowing the circles to exist on the simulation cell boundaries and using a uniform radius variation type

    Specification(s): lattice_bounds

    Design: LatticeSmoothCircleIC

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.12.4We shall be able to produce a lattice of smooth circle initial conditions, using a uniform radius variation type

    Specification(s): lattice_test

    Design: LatticeSmoothCircleIC

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.12.5We shall be able to produce a lattice of smooth circle initial conditions using a normal radius variation type

    Specification(s): lattice_normal_test

    Design: LatticeSmoothCircleIC

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.12.6We shall be able to create multiple SpecifiedSmoothCircleICs with a small invalue

    Specification(s): lattice_small_invalue_test

    Design: LatticeSmoothCircleIC

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.12.7We shall be able to create several SpecifiedSmoothCircleICs with a standard invalue

    Specification(s): specified_test

    Design: SpecifiedSmoothCircleIC

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Nucleation
  • 8.13.1The nucleation material shall generate a free energy contribution proportional to the map value

    Specification(s): material

    Design: DiscreteNucleation

    Issue(s): #5472

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.13.2The nucleation system shall insert nuclei in a manner independen of the domain decomposition and parallelization

    Specification(s): parallel

    Design: DiscreteNucleationInserter

    Issue(s): #5472

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.13.3The nucleation system shall recoverable

    Specification(s): material_recover1

    Design: DiscreteNucleation

    Issue(s): #5472

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

    Prerequisite(s): 8.13.1

  • 8.13.4The nucleation system shall recoverable

    Specification(s): material_recover2

    Design: DiscreteNucleation

    Issue(s): #5472

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 8.13.3

  • 8.13.5The nucleation system shall recoverable

    Specification(s): parallel_recover1

    Design: DiscreteNucleationInserter

    Issue(s): #5472

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

    Prerequisite(s): 8.13.2

  • 8.13.6The nucleation system shall recoverable

    Specification(s): parallel_recover2

    Design: DiscreteNucleationInserter

    Issue(s): #5472

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 8.13.5

  • 8.13.7The map shall provide the capability of defining soft interfaces for initial nuclei

    Specification(s): soft

    Design: DiscreteNucleationMap

    Issue(s): #5526

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.13.8The marker shall trigger refinement of the nucleus insertion area

    Specification(s): marker

    Design: DiscreteNucleationMarker

    Issue(s): #12099

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.13.9The nucleation time step porocessor shall return a timestep limit that can be applied to cut the simulation timestep as new nuclei are inserted

    Specification(s): timestep

    Design: DiscreteNucleationTimeStep

    Issue(s): #12104

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.13.10The nucleation data porocessor shall return the number of currently active nuclei or whether a change to the nucleus list has occurred

    Specification(s): data

    Design: DiscreteNucleationData

    Issue(s): #12114

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.13.11The nucleation auxkernel evaluates the nucleation map onto an elemental aux variable

    Specification(s): auxkernel

    Design: DiscreteNucleationAux

    Issue(s): #12114

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.13.12The nucleation force kernel returns a forcing function based on the nucleation map

    Specification(s): force

    Design: DiscreteNucleationAux

    Issue(s): #12114

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.13.13The discrete nucleation system shall provide a deterministic nucleus inserter that uses tabulated time and location data from a file. This test assigns fixed radius

    Specification(s): file

    Design: DiscreteNucleationFromFile

    Issue(s): #12262

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.13.14The discrete nucleation system shall provide a deterministic nucleus inserter that uses tabulated time and location data from a file. This test assigns variable radius

    Specification(s): file2

    Design: DiscreteNucleationFromFile

    Issue(s): #14544

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Polynomialfreeenergy
  • 8.14.1

    Specification(s): split_order4

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.14.2

    Specification(s): split_order6

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.14.3

    Specification(s): split_order8

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.14.4

    Specification(s): direct_order4

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.14.5

    Specification(s): direct_order6

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.14.6

    Specification(s): direct_order8

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Soretdiffusion
  • 8.16.1A temperature gradient driving force for diffusion shall be added to the split form of the Cahn-Hilliard equation.

    Specification(s): split

    Design: SoretDiffusion

    Issue(s): #5324

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.16.2A temperature gradient driving force for diffusion shall be added to the split form of the Cahn-Hilliard equation, where temperature is a coupled non-linear variable

    Specification(s): split_temp

    Design: SoretDiffusion

    Issue(s): #5324

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.16.3A temperature gradient driving force for diffusion shall be added to the non-split form of the Cahn-Hilliard equation.

    Specification(s): direct

    Design: SoretDiffusion

    Issue(s): #5324

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.16.4A temperature gradient driving force for diffusion shall be added to the non-split form of the Cahn-Hilliard equation, where temperature is a coupled non-linear variable

    Specification(s): direct_temp

    Design: SoretDiffusion

    Issue(s): #5324

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Splitch
  • 8.17.1

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.17.2

    Specification(s): forward_split

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Totalfreeenergy
  • 8.18.1We shall be able to calculate the free energy (with one variable) using an AuxKernel

    Specification(s): TotalFreeEnergy

    Design: TotalFreeEnergy

    Issue(s): #4413

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.18.2We shall be able to calculate the free energy (with two variables) using an AuxKernel

    Specification(s): 2var

    Design: TotalFreeEnergy

    Issue(s): #4413

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Actions
  • 8.19.1The phase field module shall provide an action to set up an Allen-Cahn problem

    Specification(s): Nonconserved_1var

    Design: NonconservedAction

    Issue(s): #9336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.19.2The NonconservedAction shall correctly set up Allen-Cahn problems with higher order elements

    Specification(s): Nonconserved_highorder

    Design: NonconservedAction

    Issue(s): #9336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.19.3The NonconservedAction shall correctly set up Allen-Cahn problems with variable dependent mobilities

    Specification(s): Nonconserved_variableL

    Design: NonconservedAction

    Issue(s): #9336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.19.4The NonconservedAction shall correctly set up Allen-Cahn problems with multiple order parameters

    Specification(s): Nonconserved_2vars

    Design: NonconservedAction

    Issue(s): #9336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.19.5The phase field module shall provide an action to set up a non-split Cahn-Hilliard problem

    Specification(s): conserved_direct_1var

    Design: ConservedAction

    Issue(s): #9336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.19.6The phase field module shall provide an action to set up a reverse split Cahn-Hilliard problem

    Specification(s): conserved_split_1var

    Design: ConservedAction

    Issue(s): #9336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.19.7The phase field module shall provide an action to set up a reverse split Cahn-Hilliard problem with higher order elements

    Specification(s): conserved_split_1var_high_order

    Design: ConservedAction

    Issue(s): #9336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.19.8The phase field module shall provide an action to set up a non-split Cahn-Hilliard problem with variable dependent mobilities

    Specification(s): conserved_direct_1var_variable_mob

    Design: ConservedAction

    Issue(s): #9336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.19.9The phase field module shall provide an action to set up a reverse split Cahn-Hilliard problem with variable dependent mobilities

    Specification(s): conserved_split_1var_variable_mob

    Design: ConservedAction

    Issue(s): #9336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.19.10The phase field module NonconservedAction and ConservedAction can be combined to construct a coupled Allen-Chan and split Cahn-Hilliard problem

    Specification(s): both_split_2vars

    Design: ConservedActionNonconservedAction

    Issue(s): #9336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.19.11The phase field module NonconservedAction and ConservedAction can be combined to construct a coupled Allen-Chan and non-split Cahn-Hilliard problem

    Specification(s): both_direct_2vars

    Design: ConservedActionNonconservedAction

    Issue(s): #9336

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.19.12The phase field module shall provide an action to set up a forward split Cahn-Hilliard problem

    Specification(s): conserved_forward_split_1var

    Design: ConservedAction

    Issue(s): #9378

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.19.13The phase field module shall provide an action to set up grain growth problems

    Specification(s): grain_growth

    Design: GrainGrowthAction

    Issue(s): #9485

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.19.14The action to set up grain growth problems shall be able to set up an AD version of the problem which yields the same results as the non-AD version

    Specification(s): ad_grain_growth

    Design: GrainGrowthAction

    Issue(s): #13539

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 8.19.13

  • 8.19.15The action to set up grain growth problems shall be able to set up an AD version of the problem which yields the same results as the non-AD version

    Specification(s): ad_grain_growth-jac

    Design: GrainGrowthAction

    Issue(s): #13539

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

    Prerequisite(s): 8.19.14

  • 8.19.16The grain growth action shall have the ability to set up problems with a pinning particle

    Specification(s): grain_growth_with_c

    Design: GrainGrowthAction

    Issue(s): #9485

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.19.17The grain growth action shall have the ability to set up problems with a temperature gradient

    Specification(s): grain_growth_with_T_grad

    Design: GrainGrowthAction

    Issue(s): #9485

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.19.18The GrandPotentialAction shall have the ability to generate kernels

    Specification(s): grand_potential_kernels

    Design: GrandPotentialKernelAction

    Issue(s): #11386

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Ad Coupled Gradient Dot
  • 8.20.1The phase field module shall be able to compute the gradient of the rate of the variable using automatic differentiation.

    Specification(s): diffusionrate

    Design: Coupleable

    Issue(s): #16167

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • phase_field: Anisotropic Interfaces
  • 8.21.1

    Specification(s): kobayashi

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.21.2

    Specification(s): adkobayashi

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Anisotropic Mobility
  • 8.22.1A split Cahn-Hilliard kernel with an anisotropic mobility shall be provided

    Specification(s): split

    Design: CahnHilliardAniso

    Issue(s): #5596

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.22.2A non-split Cahn-Hilliard kernel with an anisotropic mobility shall be provided

    Specification(s): nonsplit

    Design: SplitCHWResAniso

    Issue(s): #5596

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.22.3A Diffusion kernel with an anisotropic material property diffusivity shall be provided

    Specification(s): diffusion

    Design: MatAnisoDiffusion

    Issue(s): #5841

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.22.4AD Diffusion with an anisotropic material property diffusivity shall agree with the non-AD version

    Specification(s): ad_diffusion

    Design: ADMatAnisoDiffusion

    Issue(s): #13632

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.22.5AD Diffusion with an anisotropic material property diffusivity shall have a perfect Jacobian

    Specification(s): ad_diffusion_jac

    Design: ADMatAnisoDiffusion

    Issue(s): #13632

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • phase_field: Automatic Differentiation
  • 8.23.1The system shall provide an automatic differentiation mat reaction kernel

    Specification(s): admatreaction

    Design: ADMatReaction

    Issue(s): #13484

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.23.2The Jacobian for the automatic differentiation mat reaction kernel shall be perfect

    Specification(s): admatreaction-jac

    Design: ADMatReaction

    Issue(s): #13484

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • phase_field: Conserved Noise
  • 8.25.1A system to supply a noise field with a domain integral of zero shall be provided

    Specification(s): integral

    Design: Langevin Noise

    Issue(s): #4763

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.25.2A system to supply a normal distributed noise field with a domain integral of zero shall be provided

    Specification(s): normal

    Design: Langevin Noise

    Issue(s): #4763

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.25.3A system to supply a uniformly distributed noise field with a domain integral of zero shall be provided

    Specification(s): uniform

    Design: Langevin Noise

    Issue(s): #4763

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.25.4A system to supply a normal distributed noise field with an amplitude mask and a domain integral of zero shall be provided

    Specification(s): integral_normal_masked

    Design: Langevin Noise

    Issue(s): #4763

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.25.5The conserved noise kernel shall error out with a helpful message if a 'seed' parameter is supplied

    Specification(s): seed_error

    Design: Langevin Noise

    Issue(s): #4763

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • phase_field: Feature Flood Test
  • 8.27.1

    Specification(s): spiral

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.27.2

    Specification(s): boxes

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.27.3

    Specification(s): l_shapes

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • phase_field: Flood Counter Aux Test
  • 8.29.1

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.29.2

    Specification(s): test_elemental

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.29.3

    Specification(s): simple

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.29.4

    Specification(s): two_var

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.29.5

    Specification(s): bound_restrict_single

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.29.6

    Specification(s): bound_restrict_all

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • phase_field: Flood Counter Periodic Test
  • 8.30.1

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Functions
  • 8.32.1A function that returns a new periodic random field with a lower wavelength cut-off shall be provided.

    Specification(s): fourier_noise

    Design: FourierNoise

    Issue(s): #13316

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Grain Boundary Area
  • 8.33.1

    Specification(s): disc

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.33.2

    Specification(s): diagonal

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • phase_field: Grain Tracker Test
  • 8.35.1The system shall properly create and track grains when using the Nodal mode of the GrainTracker algorithm.

    Specification(s): test_nodal

    Design: GrainTracker

    Issue(s): #4765

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.35.2The system shall properly create and track grains when using the Elemental mode of the GrainTracker algorithm.

    Specification(s): test_elemental

    Design: GrainTracker

    Issue(s): #4881

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.35.3The PolycrystalVoronoi object shall create a valid coloring for a given number of grains and order parameters.

    Specification(s): test_advanced_op_assignment

    Design: GrainTracker

    Issue(s): #7005#9018

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.35.4The PolycrystalUserObject base class shall error when a valid coloring cannot be found when using the simple back-tracking algorithm.

    Specification(s): test_advanced_op_assignment_bt_error

    Design: Polycrystal Initial Conditions

    Issue(s): #7005#8804

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 8.35.5The PolycrystalUserObject base class shall error when a valid coloring cannot be found when using the built-in PETSc based stochastic algorithms.

    Specification(s): test_advanced_op_assignment_petsc_error

    Design: Polycrystal Initial Conditions

    Issue(s): #7005#8804

    Collection(s): FAILURE_ANALYSISFUNCTIONAL

    Type(s): RunException

  • 8.35.6The GrainTracker/PolycrystalUserObject base class shall support having only a grain halo bleeding over a periodic edge.

    Specification(s): test_halo_periodic_bc

    Design: GrainTracker

    Issue(s): #6713#8926

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.35.7The GrainTracker object shall support remapping order parameter values.

    Specification(s): test_remapping_serial

    Design: GrainTracker

    Issue(s): #1298

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.35.8The FeatureFloodCount object shall distribute the merging of features when the processor count exceeds number of order parameters for efficiency.

    Specification(s): test_remapping_parallel

    Design: GrainTracker

    Issue(s): #11805

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 8.35.7

  • 8.35.9The GrainTracker object shall properly checkpoint unique grain information in serial.

    Specification(s): test_recovery_serial_part1

    Design: GrainTracker

    Issue(s): #6713#12427

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 8.35.10The GrainTracker object shall properly recover unique grain information in serial.

    Specification(s): test_recovery_serial_part2

    Design: GrainTracker

    Issue(s): #6713#12427

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 8.35.9

  • 8.35.11The GrainTracker object shall properly checkpoint unique grain information in parallel.

    Specification(s): test_recovery_parallel_part1

    Design: GrainTracker

    Issue(s): #6713#12427

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 8.35.12The GrainTracker object shall properly recover unique grain information in parallel.

    Specification(s): test_recovery_parallel_part2

    Design: GrainTracker

    Issue(s): #6713#12427

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 8.35.11

  • 8.35.13The GrainTracker shall support reusing the data structures from the PolycrystalUserObjectBase after the initial condition for efficiency.

    Specification(s): test_poly_ic_handoff

    Design: Polycrystal Initial Conditions

    Issue(s): #8810

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.35.14The GrainTracker shall support maintaining reserve order parameters for simulations where new grains can form.

    Specification(s): remapping_with_reserve

    Design: GrainTracker

    Issue(s): #7605

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.35.15The GrainTracker shall support beginning a simulation with no active grain structure.

    Specification(s): start_with_zero_grains

    Design: GrainTracker

    Issue(s): #12200

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.35.16The GrainTracker shall support reading EBSD data to create initial conditions where IDs in the data:
    1. are contigious starting at zero,
    2. are contigious starting not starting at zero,
    3. and arbitrary with gaps.

    Specification(s): ebsd/test_ebsd, ebsd/test_ebsd_no_zero_id, ebsd/test_ebsd_gap_id

    Design: Polycrystal Initial Conditions

    Issue(s): #5067#9060

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.35.17The GrainTracker shall support reading EBSD data to create initial conditions while supporting initial condition refinement.

    Specification(s): test_ebsd_adapt

    Design: Polycrystal Initial Conditions

    Issue(s): #5067#9060

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.35.18The GrainTracker shall support handling the splitting of a grain during a simulation.

    Specification(s): split_grain

    Design: GrainTracker

    Issue(s): #7875

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.35.19The AverageFeatureVolume Postprocessor shall calculate the average volume of each active grain in a simulation.

    Specification(s): changing_avg_volume

    Design: GrainTracker

    Issue(s): #11822

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.35.20The GrainTracker shall support a mode where it can continue even when it fails to remap for post-modern analysis and debugging.

    Specification(s): tolerate_remap_failure

    Design: GrainTracker

    Issue(s): #11843

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 8.35.21The system shall properly create PolycrystalICs with halo extensions (elements) when using DistributedMesh.

    Specification(s): distributed_poly_ic

    Design: Polycrystal Initial Conditions

    Issue(s): #12216

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.35.22The system shall properly handle a single feature or grain taking up the entire domain.

    Specification(s): one_grain

    Design: GrainTracker

    Issue(s): #12216

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.35.23The system shall grain tracking behavior even when the number of grains equals the number of order parameters when using mode Nodal.

    Specification(s): test_faux_nodal

    Design: GrainTracker

    Issue(s): #5453

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.35.24The system shall grain tracking behavior even when the number of grains equals the number of order parameters when using mode Elemental.

    Specification(s): test_faux_element

    Design: GrainTracker

    Issue(s): #5453

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.35.25The system shall output individual grain tracker volumes.

    Specification(s): grain_tracker_volume

    Design: GrainTracker

    Issue(s): #7769

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.35.26The system shall output individual grain tracker volumes assigning each element to only one grain (conservative).

    Specification(s): grain_tracker_volume_single

    Design: GrainTracker

    Issue(s): #7769

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.35.27The system shall output individual grain tracker volumes when the number of order parameters equals the number of grains.

    Specification(s): feature_flood_volume

    Design: GrainTracker

    Issue(s): #5453

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 8.35.25

  • phase_field: Misc
  • 8.37.1A material shall be implemented that provides dt, time, and time step number as material properties

    Specification(s): timestepmaterial

    Design: TimeStepMaterial

    Issue(s): #7621

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.37.2A material shall be implemented that computes the magnitude of the gradient of a given variable

    Specification(s): variablegradientmaterial

    Design: VariableGradientMaterial

    Issue(s): #7621

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.37.3An interface kernel shall be implemented to match gradients between two subdomains

    Specification(s): interface_grad

    Design: InterfaceDiffusionFluxMatch

    Issue(s): #8211

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.37.4Demonstrate an InterfaceKernel (InterfaceDiffusionFlux) that can replace a pair of integrated DiffusionFluxBC boundary conditions.

    Specification(s): interface_flux

    Design: InterfaceDiffusionBoundaryTerm

    Issue(s): #8211

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.37.5An InterfaceKernel set shall be implemented that can enforce the componentwise continuity of the gradient of a variable using the Lagrange multiplier method

    Specification(s): equal_gradient_lagrange

    Design: EqualGradientLagrangeInterface

    Issue(s): #8211

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.37.6An initial condition shall be implemented that can set the value of a variable to the value of a function evaluated over a set of up to four coupled variables

    Specification(s): coupled_value_function_ic

    Design: CoupledValueFunctionIC

    Issue(s): #16405

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • phase_field: Phase Field Crystal
  • 8.40.1

    Specification(s): auxkernel

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.40.2The system shall support a tolerance approach to handing the natural log when using the Cahn-Hilliard RFF kernel

    Specification(s): tolerance_test

    Design: CHPFCRFF

    Issue(s): #5338

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.40.3The system shall support a cancelation approach to handing the natural log when using the Cahn-Hilliard RFF kernel

    Specification(s): cancelation_test

    Design: CHPFCRFF

    Issue(s): #5338

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.40.4The system shall support an expansion approach to handing the natural log when using the Cahn-Hilliard RFF kernel

    Specification(s): expansion_test

    Design: CHPFCRFF

    Issue(s): #5338

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.40.5

    Specification(s): PFCRFF_split_test

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.40.6

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.40.7

    Specification(s): BCC_test

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.40.8

    Specification(s): FCC_test

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Phase Field Kernels
  • 8.41.1The system shall provide a non-split Cahn-Hilliard formalism

    Specification(s): CahnHilliard

    Design: CahnHilliard

    Issue(s): #3356

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.41.2The system shall provide a split Cahn-Hilliard formalism

    Specification(s): SplitCahnHilliard

    Design: SplitCHParsed

    Issue(s): #3356

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.41.3The system shall provide an AD version of the split Cahn-Hilliard formalism

    Specification(s): ADSplitCahnHilliard

    Design: ADSplitCHParsed

    Issue(s): #13138

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 8.41.2

  • 8.41.4The system shall provide a perfect Jacobian for the AD split Cahn-Hilliard problem.

    Specification(s): ADSplitCahnHilliard-jac

    Design: ADSplitCHParsed

    Issue(s): #13138

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 8.41.5The system shall provide a kernel option to implement transport terms for the off-diagonal Onsager matrix components

    Specification(s): SplitCHWRes

    Design: SplitCHWRes

    Issue(s): #14140

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.41.6The system shall provide a Allen-Cahn phase field formulation.

    Specification(s): AllenCahn

    Design: AllenCahn

    Issue(s): #3816

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.41.7The system shall provide perfect Jacobian contributions for the Allen-Cahn phase field formulation.

    Specification(s): analyzejacobian_AllenCahn

    Design: AllenCahn

    Issue(s): #3816

    Collection(s): FUNCTIONAL

    Type(s): AnalyzeJacobian

    Prerequisite(s): 8.41.13

  • 8.41.8The system shall provide a Allen-Cahn phase field formulation with a variable dependent mobility.

    Specification(s): AllenCahnVariableL

    Design: AllenCahn

    Issue(s): #3816

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.41.9The system shall provide an AD version of the Allen-Cahn phase field formulation.

    Specification(s): ADAllenCahn

    Design: ADAllenCahn

    Issue(s): #13197

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.41.10The system shall calculate a perfect Jacobian for the AD Allen-Cahn problem.

    Specification(s): ADAllenCahn-jac

    Design: ADAllenCahn

    Issue(s): #13197

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 8.41.11The system shall provide an AD version of the Allen-Cahn phase field formulation with a variable dependent mobility.

    Specification(s): ADAllenCahnVariableL

    Design: ADAllenCahn

    Issue(s): #13197

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.41.12The system shall calculate a perfect Jacobian for the AD Allen-Cahn problem with a variable dependent mobility.

    Specification(s): ADAllenCahnVariableL-jac

    Design: ADAllenCahn

    Issue(s): #13197

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 8.41.13The system shall provide a coupled Allen-Cahn formulation.

    Specification(s): CoupledAllenCahn

    Design: CoupledAllenCahn

    Issue(s): #6194

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 8.41.6

  • 8.41.14The system shall provide a coupled Allen-Cahn formulation with a user defined prefactor.

    Specification(s): CoupledCoefAllenCahn

    Design: CoupledAllenCahn

    Issue(s): #6265

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.41.15The system shall provide a coupled gradient square kernel.

    Specification(s): MatGradSquareCoupled

    Design: MatGradSquareCoupled

    Issue(s): #10721

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.41.16The system shall provide a suite of simple to understand phase field kernels for novice users.

    Specification(s): SimpleSplitCHWRes

    Design: SimpleSplitCHWRes

    Issue(s): #6910

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.41.17The system shall provide a suite of simple to understand phase field kernels for novice users.

    Specification(s): SimpleCHInterface

    Design: SimpleCHInterface

    Issue(s): #6910

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.41.18The system shall provide a free energy contribution from elastic stresses in interfaces.

    Specification(s): ACInterfaceStress

    Design: ACInterfaceStress

    Issue(s): #9658

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.41.19The system shall provide a perfect Jacobian for the free energy contribution from elastic stresses in interfaces.

    Specification(s): analyzejacobian_ACInterfaceStress

    Design: ACInterfaceStress

    Issue(s): #9658

    Collection(s): FUNCTIONAL

    Type(s): AnalyzeJacobian

  • 8.41.20The system shall verify that the barrier height and gradient energy parameter must be permitted to depend on non-linear variables.

    Specification(s): nonuniform_barrier_coefficient

    Design: ACBarrierFunction

    Issue(s): #11829

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Polycrystal Diffusion
  • 8.42.1The system shall provide a material to assign location specific diffusivities in a polycrysatal structure, compatible with multiphase switching functions

    Specification(s): polycrystal_void_diffusion

    Design: PolycrystalDiffusivity

    Issue(s): #19643

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.42.2The system shall provide a material to assign location specific diffusivities in a polycrysatal structure, compatible with any use-specified switching functions

    Specification(s): polycrystal_void_diffusion_parsed

    Design: PolycrystalDiffusivity

    Issue(s): #19643

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Reconstruction
  • 8.43.1The system shall output an RGB field that can be interpreted as either a component or a combined Euler angle given a grain structure.

    Specification(s): EulerAngleVariables2RGBAux

    Design: EulerAngleVariables2RGBAux

    Issue(s): #7332

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.43.2The system shall support reading EBSD data and initializing a Polycrystal grain structure with that data.

    Specification(s): 1phase_reconstruction

    Design: Reading EBSD Data

    Issue(s): #9110

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.43.3The system shall support reading EBSD data to initalized Polycrystal grain structures while supporting reduced order parameter IC assignment.

    Specification(s): 1phase_reconstruction_40x40

    Design: Reading EBSD Data

    Issue(s): #9110

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.43.4The system shall support reading EBSD data to initalized Polycrystal grain structures while supporting reduced order parameter IC assignment on a distributed mesh.

    Specification(s): 1phase_reconstruction_40x40_distributed

    Design: Reading EBSD Data

    Issue(s): #19150

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.43.5The system shall support reading EBSD data to initalized Polycrystal grain structures while supporting reduced order parameter IC assignment on a distributed mesh with pre-refinement to allow for adaptive coarsening.

    Specification(s): 1phase_reconstruction_40x40_distributed_pre_refine

    Design: Reading EBSD Data

    Issue(s): #19150

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.43.6The system shall support grain evolution when beginning from EBSD ICs.

    Specification(s): 1phase_evolution

    Design: Reading EBSD Data

    Issue(s): #9110

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.43.7The system shall support reading a single phase of EBSD data at a time to initialize PolycrystalICs.

    Specification(s): 2phase_reconstruction

    Design: Reading EBSD Data

    Issue(s): #9110#5920

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.43.8The system shall support reading a single phase of EBSD data at a time to initialize PolycrystalICs while supporting reduced order parameter IC assignment.

    Specification(s): 2phase_reconstruction2

    Design: Reading EBSD Data

    Issue(s): #9110#5920

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.43.9The system shall support reading EBSD data to initialize PolycrystalICs with discontinuous numbering.

    Specification(s): 2phase_reconstruction3

    Design: Reading EBSD Data

    Issue(s): #9110#5920

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.43.10The system shall support reading a single phase of EBSD data at a time to initialize PolycrystalICs while supporting reduced order parameter IC assignment and display the coloring.

    Specification(s): 2phase_reconstruction4

    Design: Reading EBSD Data

    Issue(s): #9110#5920

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 8.43.11The system shall support reading a single phase of EBSD data at a time to initialize PolycrystalICs and support regions within the domain that contain no grains at all.

    Specification(s): regions_without_grains

    Design: Reading EBSD Data

    Issue(s): #9110#5920

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 8.43.12The system shall support grain evolution when beginning from EBSD ICs and compute average orientation of non-uniformly oriented grains.

    Specification(s): average_orientation

    Design: EBSDReader

    Issue(s): #13869

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • phase_field: Solution Rasterizer
  • 8.45.1

    Specification(s): prepare

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 8.45.2

    Specification(s): test

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

    Prerequisite(s): 8.45.1

Usability Requirements

Performance Requirements

System Interface Requirements

References

No citations exist within this document.