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

  • xfem: Bimaterials
  • 9.1.1The XFEM module shall have the capability to calculate mechanical response in two glued, layered materials with the interface location and material properties applied to on each side of the boundary determined by a level set function.

    Specification(s): glued_bimaterial

    Design: LevelSetCutUserObjectXFEMSingleVariableConstraint

    Issue(s): #10421

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.1.2The XFEM module shall have the capability to calculate mechanical response in a composite material matrix with an inclusion with the location of the inclusion boundary and material properties applied to the matrix and inclusion determined by a prescribed level set function.

    Specification(s): inclusion_bimaterial

    Design: LevelSetCutUserObjectXFEMSingleVariableConstraint

    Issue(s): #10421

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.1.3The system shall have the capability to calculate the mechanical response in two glued, layered materials with the interface location and automatic differentiation material properties applied to on each side of the boundary determined by a level set function.

    Specification(s): glued_ad_bimaterial

    Design: LevelSetBiMaterialRankTwoLevelSetBiMaterialRankFour

    Issue(s): #15437

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 9.1.1

  • 9.1.4The XFEM module shall have the capability to calculate mechanical response in a composite material matrix with an inclusion with the location of the inclusion boundary and material properties applied to the matrix and inclusion determined by a prescribed level set function using automatic differentiation.

    Specification(s): inclusion_ad_bimaterial

    Design: LevelSetBiMaterialRankTwo

    Issue(s): #15437

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 9.1.2

  • xfem: Checkpoint
  • 9.2.1The XFEM module shall support outputting of checkpoint files.

    Specification(s): checkpoint

    Design: Checkpoint

    Issue(s): #17063

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • xfem: Corner Nodes Cut
  • 9.3.1The XFEM module shall have the capability of cutting directly through multiple nodes of a single QUAD4 element in 2D.

    Specification(s): corner_node_cut_twice

    Design: LineSegmentCutUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.3.2The XFEM module shall be able to perform mesh cuts on any combination of the edges of elements and through elements including allowing cuts that go through the nodes on the same mesh.

    Specification(s): corner_edge_cut

    Design: LineSegmentCutUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.3.3The XFEM module shall have the capability of perfoming mesh cuts on the edges of elements such that only two new nodes are generated to separate the previously connected elements.

    Specification(s): corner_node_cut

    Design: LineSegmentCutUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.3.4The XFEM module shall be capable of propagating an existing crack front along a prescribed cut in 2D.

    Specification(s): notch

    Design: LineSegmentCutUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • xfem: Diffusion Xfem
  • 9.5.1The XFEM Module shall have the capability to run 2D diffusion problems with prescribed values on the domain boundary (Dirichlet conditions) with a fixed position discontinuous interface through mesh elements.

    Specification(s): diffusion_xfem

    Design: LineSegmentCutUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.5.2The XFEM Module shall have the capability to run 2D diffusion problems with prescribed solution values on the domain boundary (Dirichlet conditions) and prescribed boundary flux values (Neumann conditions) with a fixed position discontinuous interface defined by a geometric cut user object.

    Specification(s): diffusion_xfem_flux_bc

    Design: LineSegmentCutUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.5.3The XFEM Module shall have the capability to run 2D diffusion problems with a fixed position discontinuous interface defined by the location of the zero values of a level set function with the level set variable being a Moose Variable.

    Specification(s): levelsetcut2d

    Design: LevelSetCutUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.5.4The XFEM Module shall have the capability to run 2D diffusion problems with a fixed position discontinuous interface defined by the location of the zero values of a prescribed level set function with the level set variable being a Moose AuxVariable.

    Specification(s): levelsetcut2d_aux

    Design: LevelSetCutUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.5.5The XFEM Module shall have the capability to run 3D diffusion problems with a fixed position discontinuous interface defined by the location of the zero values of a prescribed level set function with the level set variable being a Moose AuxVariable.

    Specification(s): levelsetcut3d

    Design: LevelSetCutUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • xfem: Init Solution Propagation
  • 9.6.1The XFEM module shall retain the values of auxiliary variables on child nodes and elements after running the cutting algorithm, and initialize solution variables on newly created nodes with values from parent nodes in parallel

    Specification(s): init_solution_propagation

    Design: XFEM

    Issue(s): #8763

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • xfem: Mechanical Constraint
  • 9.7.1The XFEM module shall permit applying a glued constraint across the XFEM interface for 2D solid mechanics problems.

    Specification(s): glued_penalty

    Design: XFEM

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • xfem: Moment Fitting
  • 9.8.1The XFEM module shall permit the use of the moment fitting algorithm to compute integration point weights for partial elements on 2D solid mechanics problems

    Specification(s): solid_mechanics_moment_fitting

    Design: XFEM

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.8.2The XFEM module shall permit the use of the moment fitting algorithm to compute integration point weights for partial elements on 2D problems with a 4-point integration rule

    Specification(s): diffusion_moment_fitting_four_points

    Design: XFEM

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.8.3The XFEM module shall permit the use of the moment fitting algorithm to compute integration point weights for partial elements on 2D problems with a 6-point integration rule

    Specification(s): diffusion_moment_fitting_six_points

    Design: XFEM

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • xfem: Pressure Bc
  • 9.10.1The XFEM module shall permit application of pressure boundary conditions to XFEM cut surfaces in 2D

    Specification(s): edge_2d_pressure

    Design: XFEMPressure

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.10.2The XFEM module shall permit application of pressure boundary conditions to XFEM cut surfaces in 3D

    Specification(s): edge_3d_pressure

    Design: XFEMPressure

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.10.3The XFEM module shall permit application of pressure boundary conditions to inclined XFEM cut surfaces in 2D

    Specification(s): inclined_edge_2d_pressure

    Design: XFEMPressure

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.10.4The XFEM module shall permit application of pressure boundary conditions to XFEM cut surfaces in 2D finite deformation simulations

    Specification(s): 2d_pressure_displaced_mesh

    Design: XFEMPressure

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • xfem: Second Order Elements
  • 9.11.1The XFEM module shall permit modeling of discontinuities represented with XFEM with second-order elements in 2D using TRI6 elements.

    Specification(s): diffusion_2d_tri6

    Design: XFEM

    Issue(s): #8709

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.11.2The XFEM module shall permit modeling of discontinuities represented with XFEM with second-order elements in 2D using QUAD8 elements.

    Specification(s): diffusion_2d_quad8

    Design: XFEM

    Issue(s): #8709

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.11.3The XFEM module shall permit modeling of discontinuities represented with XFEM with second-order elements in 2D using QUAD9 elements.

    Specification(s): diffusion_2d_quad9

    Design: XFEM

    Issue(s): #8709

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.11.4The XFEM module shall permit modeling of discontinuities represented with XFEM with second-order elements in 2D using QUAD9 elements when the XFEM cutting plane is prescribed using a level set field.

    Specification(s): diffusion_quad9_levelsetcut

    Design: XFEM

    Issue(s): #8709

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.11.5The XFEM module shall permit modeling of discontinuities represented with XFEM with second-order elements in 3D using TET10 elements when the XFEM cutting plane is prescribed using a level set field.

    Specification(s): diffusion_3d_tet10

    Design: XFEM

    Issue(s): #8709

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.11.6The XFEM module shall permit modeling of discontinuities represented with XFEM with second-order elements in 3D using HEX20 elements when the XFEM cutting plane is prescribed using a level set field.

    Specification(s): diffusion_3d_hex20

    Design: XFEM

    Issue(s): #8709

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.11.7The XFEM module shall permit modeling of discontinuities represented with XFEM with second-order elements in 3D using HEX27 elements when the XFEM cutting plane is prescribed using a level set field.

    Specification(s): diffusion_3d_hex27

    Design: XFEM

    Issue(s): #8709

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.11.8The XFEM module shall permit modeling of branching of discontinuities represented with XFEM by sequentially cutting second-order elements in 2D using QUAD8 elements.

    Specification(s): square_branch_quad8_2d

    Design: XFEM

    Issue(s): #8709

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.11.9The XFEM module shall permit modeling of branching of discontinuities represented with XFEM by sequentially cutting second-order elements in 2D using QUAD9 elements.

    Specification(s): square_branch_quad9_2d

    Design: XFEM

    Issue(s): #8709

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.11.10The XFEM module shall permit modeling of branching of discontinuities represented with XFEM by sequentially cutting second-order elements in 2D using TRI6 elements.

    Specification(s): square_branch_tri6_2d

    Design: XFEM

    Issue(s): #8709

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • xfem: Side Integral
  • 9.12.1The XFEM module shall properly integrate quantities on sides of cut elements that are intersected by the cutting plane in 2D

    Specification(s): side_integral_xfem

    Design: XFEM

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.12.2The XFEM module shall properly integrate quantities on sides of cut elements that are intersected by the cutting plane in 3D

    Specification(s): side_integral_3d_xfem

    Design: XFEM

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • xfem: Single Var Constraint 2D
  • 9.13.1The XFEM module shall provide an ability to apply a zero-jump, zero-flux-jump constraint across a propagating XFEM interface for one variable.

    Specification(s): propagating_1field

    Design: XFEMSingleVariableConstraint

    Issue(s): #6572

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.13.2The XFEM module shall provide an ability to apply a zero-jump, zero-flux-jump constraint across a propagating XFEM interface for one variable in a problem with another variable that does not have a constraint across that interface.

    Specification(s): propagating_2field_1constraint

    Design: XFEMSingleVariableConstraint

    Issue(s): #6572

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.13.3The XFEM module shall provide an ability to apply zero-jump, zero-flux-jump constraints across a propagating XFEM interface for two variables.

    Specification(s): propagating_2field_2constraint

    Design: XFEMSingleVariableConstraint

    Issue(s): #6572

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.13.4The XFEM module shall provide an ability to apply a zero-jump, zero-flux-jump constraint on a stationary interface for one variable.

    Specification(s): stationary_equal

    Design: XFEMSingleVariableConstraint

    Issue(s): #6572

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.13.5The XFEM module shall provide an ability to apply a zero-jump, nonzero-flux-jump (defined by a Real value) constraint on a stationary interface for one variable.

    Specification(s): stationary_fluxjump

    Design: XFEMSingleVariableConstraint

    Issue(s): #6572

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.13.6The XFEM module shall provide an ability to apply a zero-jump, nonzero-flux-jump (defined by a function) constraint on a stationary interface for one variable.

    Specification(s): stationary_fluxjump_func

    Design: XFEMSingleVariableConstraint

    Issue(s): #13756

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.13.7The XFEM module shall provide an ability to apply a nonzero-jump (defined by a Real value), zero-flux-jump constraint on a stationary interface for one variable.

    Specification(s): stationary_jump

    Design: XFEMSingleVariableConstraint

    Issue(s): #6572

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.13.8The XFEM module shall provide an ability to apply a nonzero-jump (defined by a function), zero-flux-jump constraint on a stationary interface for one variable.

    Specification(s): stationary_jump_func

    Design: XFEMSingleVariableConstraint

    Issue(s): #13756

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.13.9The XFEM module shall provide an ability to apply a nonzero-jump, nonzero-flux-jump constraint on a stationary interface for one variable.

    Specification(s): stationary_jump_fluxjump

    Design: XFEMSingleVariableConstraint

    Issue(s): #6572

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.13.10The XFEM module shall provide an ability to apply a two-sided equal value constraint on a stationary interface for one variable.

    Specification(s): equal_value

    Design: XFEMEqualValueAtInterface

    Issue(s): #11750

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • xfem: Single Var Constraint 3D
  • 9.14.1The XFEM module shall provide an ability to apply a zero-jump, zero-flux-jump constraint across a stationary XFEM interface for one variable in 3D.

    Specification(s): stationary_equal_3d

    Design: XFEMSingleVariableConstraint

    Issue(s): #6572

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.14.2The XFEM module shall provide an ability to apply a zero-jump, nonzero-flux-jump constraint across a stationary XFEM interface for one variable in 3D.

    Specification(s): stationary_fluxjump_3d

    Design: XFEMSingleVariableConstraint

    Issue(s): #6572

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.14.3The XFEM module shall provide an ability to apply a nonzero-jump, zero-flux-jump constraint across a stationary XFEM interface for one variable in 3D.

    Specification(s): stationary_jump_3d

    Design: XFEMSingleVariableConstraint

    Issue(s): #6572

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.14.4The XFEM module shall provide an ability to apply a nonzero-jump, nonzero-flux-jump constraint across a stationary XFEM interface for one variable in 3D.

    Specification(s): stationary_jump_fluxjump_3d

    Design: XFEMSingleVariableConstraint

    Issue(s): #6572

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • xfem: Solid Mechanics Basic
  • 9.15.1The XFEM module shall represent a propagating crack in a 2D mechanics problem in which crack growth occurs when the average stress in the element at the crack tip exceeds a critical value.

    Specification(s): crack_propagation_ave

    Design: XFEMRankTwoTensorMarkerUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.15.2The XFEM module shall represent a propagating crack in a 2D mechanics problem in which crack growth occurs when the average stress in the element at the crack tip exceeds a critical value defined by the value of a field variable.

    Specification(s): crack_propagation_var

    Design: XFEMRankTwoTensorMarkerUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 9.15.1

  • 9.15.3The XFEM module shall represent a propagating crack in a 2D mechanics problem in which crack growth occurs when the stress at any of the quadrature points in the element at the crack tip exceeds a critical value defined by the value of a field variable.

    Specification(s): crack_propagation_single_point

    Design: XFEMRankTwoTensorMarkerUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.15.4The XFEM module shall permit definition of a stationary crack in a 3D mechanics model with XFEM, where the crack is defined using a rectangular cutting plane by RectangleCutUserObject

    Specification(s): edge_crack_3d

    Design: RectangleCutUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.15.5The XFEM module shall represent a propagating crack in a 3D mechanics model with XFEM, where the crack is defined using a topologically surface cutting mesh by CrackMeshCut3DUserObject and allowed to propagate with growth speeds determined by the fatigue cracking Paris law

    Specification(s): edge_crack_3d_fatigue

    Design: CrackMeshCut3DUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.15.6The XFEM module shall represent a propagating crack in a 3D mechanics model with XFEM, where the crack is defined using a topologically surface cutting mesh by CrackMeshCut3DUserObject and allowed to propagate with growth directions determined by the maximum hoop stress law

    Specification(s): edge_crack_3d_mhs

    Design: CrackMeshCut3DUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.15.7The XFEM module shall represent a propagating crack in a 3D mechanics model with XFEM, where the crack is defined using a topologically surface cutting mesh by CrackMeshCut3DUserObject

    Specification(s): edge_crack_3d_propagation

    Design: CrackMeshCut3DUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.15.8The XFEM module shall permit definition of a stationary crack in a 3D mechanics model with XFEM, where the crack is defined using an elliptical cutting plane by EllipseCutUserObject

    Specification(s): elliptical_crack

    Design: EllipseCutUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.15.9The XFEM system shall permit computation of fracture domain integrals in 3D mechanics problems where a stationary embedded circular crack is defined by a cutting plane geometry and points along the crack front for the domain integral are explicitly specified.

    Specification(s): penny_crack

    Design: DomainIntegral SystemCircleCutUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.15.10The XFEM system shall permit computation of fracture domain integrals in 3D mechanics problems where a stationary embedded circular crack is defined by a cutting plane geometry and points along the crack front for the domain integral provided by a class that derives from CrackFrontPointsProvider.

    Specification(s): penny_crack_cfp

    Design: DomainIntegral SystemCircleCutUserObject

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.15.11The XFEM system shall permit branched cracks to be represented in 2D by sequentially cutting a 4-noded quadrilateral element by two prescribed evolving cutting planes

    Specification(s): square_branch_quad_2d

    Design: XFEM

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.15.12The XFEM system shall permit branched cracks to be represented in 2D by sequentially cutting a 3-noded triangle element by two prescribed evolving cutting planes

    Specification(s): square_branch_tri_2d

    Design: XFEM

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 9.15.13The XFEM system shall provide an accessor function to the crack_tip_origin_direction_map

    Specification(s): test_crack_counter

    Design: XFEM

    Issue(s): #6320

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

Usability Requirements

Performance Requirements

System Interface Requirements

References

No citations exist within this document.