Reactor System Design Description
This template follows INL template TEM-140, "IT System Design Description."
This document serves as an addendum to Framework System Design Description and captures information for Software Design Description (SDD) specific to the Reactor application.
Introduction
Frameworks are a software development construct aiming to simplify the creation of specific classes of applications through abstraction of low-level details. The main object of creating a framework is to provide an interface to application developers that saves time and provides advanced capabilities not attainable otherwise. The MOOSE, mission is just that: provide a framework for engineers and scientists to build state-of-the-art, computationally scalable finite element based simulation tools.
MOOSE was conceived with one major objective: to be as easy and straightforward to use by scientists and engineers as possible. MOOSE is meant to be approachable by non-computational scientists who have systems of partial differential equations (PDEs) they need to solve. Every single aspect of MOOSE was driven by this singular principle from the build system to the API to the software development cycle. At every turn, decisions were made to enable this class of users to be successful with the framework. The pursuit of this goal has led to many of the unique features of MOOSE:
A streamlined build system
An API aimed at extensible
Straightforward APIs providing sensible default information
Integrated, automatic, and rigorous testing
Rapid, continuous integration development cycle
Codified, rigorous path for contributing
Applications are modular and composable
Each of these characteristics is meant to build trust in the framework by those attempting to use it. For instance, the build system is the first thing potential framework users come into contact with when they download a new software framework. Onerous dependency issues, complicated, hard to follow instructions or build failure can all result in a user passing on the platform. Ultimately, the decision to utilize a framework comes down to whether or not you trust the code in the framework and those developing it to be able to support your desired use-case. No matter the technical capabilities of a framework, without trust users will look elsewhere. This is especially true of those not trained in software development or computational science.
Developing trust in a framework goes beyond utilizing "best practices" for the code developed, it is equally important that the framework itself is built upon tools that are trusted. For this reason, MOOSE relies on a well-established code base of libMesh and PETSc. The libMesh library provides foundational capability for the finite element method and provides interfaces to leading-edge numerical solution packages such as PETSc.
With these principles in mind, an open source, massively parallel, finite element, multiphysics framework has been conceived. MOOSE is an on-going project started in 2008 aimed toward a common platform for creation of new multiphysics tools. This document provides design details pertinent to application developers as well as framework developers.
Use Cases
The MOOSE Framework is targeted at two main groups of actors: Developers and Users. Developers are the main use case. These are typically students and professionals trained in science and engineering fields with some level of experience with coding but typically very little formal software development training. The other user group is Users. Those who intend to use an application built upon the framework without writing any computer code themselves. Instead they may modify or create input files for driving a simulation, run the application, and analyze the results. All interactions through MOOSE are primarily through the command-line interface and through a customizable block-based input file.
System Purpose
The Software Design Description provided here is description of each object in the system. The pluggable architecture of the framework makes MOOSE and MOOSE-based applications straightforward to develop as each piece of end-user (developer) code that goes into the system follows a well-defined interface for the underlying systems that those object plug into. These descriptions are provided through developer-supplied "markdown" files that are required for all new objects that are developed as part of the framework, modules and derivative applications. More information about the design documentation can be found in Documenting MOOSE.
System Scope
The purpose of this software is to provide several libraries that can be used to build an application based upon the framework. Additionally, several utilities are provided for assisting developers and users in end-to-end FEM analysis. A brief overview of the major components are listed here:
Component | Description |
---|---|
framework library | The base system from which all MOOSE-based applications are created |
module libraries | Optional "physics" libraries that may be used in an application to provide capability |
build system | The system responsible for creating applications for a series of libraries and applications |
test harness | The extendable testing system for finding, scheduling, running, and reporting regression tests |
"peacock" | The graphical user interface (GUI) for building input files, executing applications, and displaying results |
MooseDocs | The extendable markdown system for MOOSE providing common documentation and requirements enforcement |
"stork" | The script and templates for generating a new MOOSE-based application ready for building and testing |
examples | A set of complete applications demonstrating the use of MOOSE's pluggable systems |
tutorials | Step by step guides to building up an application using MOOSE's pluggable systems |
unit | An application for unit testing individual classes or methods of C++ code |
Dependencies and Limitations
The MOOSE platform has several dependencies on other software packages and has scope that is constantly evolving based upon funding, resources, priorities, and lab direction. However, the software is open-source and many features and even bugs can be offloaded to developers with appropriate levels of knowledge and direction from the main design team. The primary list of software dependencies is listed below. This list is not meant to be exhaustive. Individual operating systems may require specific packages to be installed prior to using MOOSE, which can be found on the Install MOOSE pages.
Software Dependency | Description |
---|---|
libMesh | Finite Element Library and I/O routines |
PETSc | Solver Package |
hypre | Multigrid Preconditioner |
MPI | A distributed parallel processing library (MPICH) |

Figure 1: A diagram of the MOOSE code platform.
References
Definitions and Acronyms
This section defines, or provides the definition of, all terms and acronyms required to properly understand this specification.
Definitions
- Pull (Merge) Request: A proposed change to the software (e.g. usually a code change, but may also include documentation, requirements, design, and/or testing). - Baseline: A specification or product (e.g., project plan, maintenance and operations (M&O) plan, requirements, or design) that has been formally reviewed and agreed upon, that thereafter serves as the basis for use and further development, and that can be changed only by using an approved change control process (NQA-1, 2009). - Validation: Confirmation, through the provision of objective evidence (e.g., acceptance test), that the requirements for a specific intended use or application have been fulfilled (24765:2010(E), 2010). - Verification: (1) The process of: evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase. (2) Formal proof of program correctness (e.g., requirements, design, implementation reviews, system tests) (24765:2010(E), 2010).
Acronyms
Acronym | Description |
---|---|
API | Application Programming Interface |
DOE-NE | Department of Energy, Nuclear Energy |
FE | finite element |
FEM | Finite Element Method |
GUI | graphical user interface |
HIT | Hierarchical Input Text |
HPC | High Performance Computing |
I/O | Input/Output |
INL | Idaho National Laboratory |
MOOSE | Multiphysics Object Oriented Simulation Environment |
MPI | Message Passing Interface |
PDEs | partial differential equations |
SDD | Software Design Description |
Design Stakeholders and Concerns
Design Stakeholders
Stakeholders for MOOSE include several of the funding sources including Department of Energy, Nuclear Energy (DOE-NE) and the INL. However, Since MOOSE is an open-source project, several universities, companies, and foreign governments have an interest in the development and maintenance of the MOOSE project.
Stakeholder Design Concerns
Concerns from many of the stakeholders are similar. These concerns include correctness, stability, and performance. The mitigation plan for each of these can be addressed. For correctness, MOOSE development requires either regression or unit testing for all new code added to the repository. The project contains several comparisons against analytical solutions where possible and also other verification methods such as MMS. For stability, MOOSE maintains multiple branches to incorporate several layers of testing both internally and for dependent applications. Finally, performance tests are also performed as part of the the normal testing suite to monitor code change impacts to performance.
System Design
The MOOSE framework itself is composed of a wide range of pluggable systems. Each system is generally composed of a single or small set of C++ objects intended to be specialized by a Developer to solve a specific problem. To accomplish this design goal, MOOSE uses several modern object-oriented design patterns. The primary overarching pattern is the "Factory Pattern". Users needing to extend MOOSE may inherit from one of MOOSE's systems to providing an implementation meeting his or her needs. The design of each of these systems is documented on the mooseframework.org wiki in the Tutorial section. Additionally, up-to-date documentation extracted from the source is maintained on the the mooseframework.org documentation site after every successful merge to MOOSE's stable branch. After these objects are created, the can be registered with the framework and used immediately in a MOOSE input file.
System Structure
The MOOSE framework architecture consists of a core and several pluggable systems. The core of MOOSE consists of a number of key objects responsible for setting up and managing the user-defined objects of a finite element simulation. This core set of objects has limited extendability and exist for every simulation configuration that the framework is capable of running.
Adaptivity
Adaptivity/Indicators
Adaptivity/Markers
AuxKernels
AuxKernels/MatVecRealGradAuxKernel
AuxKernels/MaterialVectorAuxKernel
AuxKernels/MaterialVectorGradAuxKernel
AuxScalarKernels
AuxVariables
AuxVariables/MultiAuxVariables
BCs
BCs/CavityPressure
BCs/CoupledPressure
BCs/InclinedNoDisplacementBC
BCs/Periodic
BCs/Pressure
Bounds
Closures
Components
Constraints
Contact
ControlLogic
Controls
CoupledHeatTransfers
Covariance
DGKernels
Dampers
Debug
Debug/MaterialDerivativeTest
DeprecatedBlock
DiracKernels
Distributions
DomainIntegral
Executioner
Executioner/Adaptivity
Executioner/Predictor
Executioner/Quadrature
Executioner/TimeIntegrator
Executioner/TimeStepper
Executors
FVBCs
FVInterfaceKernels
FVKernels
FluidPropertiesInterrogator
Functions
GeochemicalModelInterrogator
GlobalParams
GrayDiffuseRadiation
HeatStructureMaterials
ICs
ICs/PolycrystalICs
ICs/PolycrystalICs/BicrystalBoundingBoxIC
ICs/PolycrystalICs/BicrystalCircleGrainIC
ICs/PolycrystalICs/PolycrystalColoringIC
ICs/PolycrystalICs/PolycrystalRandomIC
ICs/PolycrystalICs/PolycrystalVoronoiVoidIC
ICs/PolycrystalICs/Tricrystal2CircleGrainsIC
InterfaceKernels
Kernels
Kernels/CHPFCRFFSplitKernel
Kernels/DynamicTensorMechanics
Kernels/HHPFCRFFSplitKernel
Kernels/PFCRFFKernel
Kernels/PolycrystalElasticDrivingForce
Kernels/PolycrystalKernel
Kernels/PolycrystalStoredEnergy
Kernels/PoroMechanics
Kernels/RigidBodyMultiKernel
Kernels/TensorMechanics
Materials
Mesh
Mesh/Partitioner
Modules
Modules/CompressibleNavierStokes
Modules/FluidProperties
Modules/HeatConduction
Modules/HeatConduction/ThermalContact
Modules/HeatConduction/ThermalContact/BC
Modules/IncompressibleNavierStokes
Modules/NavierStokesFV
Modules/Peridynamics
Modules/Peridynamics/Mechanics
Modules/Peridynamics/Mechanics/GeneralizedPlaneStrain
Modules/Peridynamics/Mechanics/Master
Modules/PhaseField
Modules/PhaseField/Conserved
Modules/PhaseField/DisplacementGradients
Modules/PhaseField/EulerAngles2RGB
Modules/PhaseField/GrainGrowth
Modules/PhaseField/GrandPotential
Modules/PhaseField/Nonconserved
Modules/PorousFlow
Modules/PorousFlow/BCs
Modules/TensorMechanics
Modules/TensorMechanics/CohesiveZoneMaster
Modules/TensorMechanics/DynamicMaster
Modules/TensorMechanics/GeneralizedPlaneStrain
Modules/TensorMechanics/GlobalStrain
Modules/TensorMechanics/LineElementMaster
Modules/TensorMechanics/Master
Modules/TensorMechanics/MaterialVectorBodyForce
MortarGapHeatTransfer
MultiApps
NodalKernels
NodalNormals
Outputs
PorousFlowBasicTHM
PorousFlowFullySaturated
PorousFlowUnsaturated
Postprocessors
Preconditioning
Problem
RayBCs
RayKernels
ReactionNetwork
ReactionNetwork/AqueousEquilibriumReactions
ReactionNetwork/SolidKineticReactions
Reporters
Samplers
ScalarKernels
SpatialReactionSolver
StochasticTools
Surrogates
ThermalContact
TimeDependentReactionSolver
TimeIndependentReactionSolver
Trainers
Transfers
UserObjects
Variables
Variables/CHPFCRFFSplitVariables
Variables/HHPFCRFFSplitVariables
Variables/PFCRFFVariables
Variables/PolycrystalVariables
VectorPostprocessors
XFEM
The MooseApp is the top-level object used to hold all of the other objects in a simulation. In a normal simulation a single MooseApp object is created and "run()". This object uses it's Factory objects to build user defined objects which are stored in a series of Warehouse objects and executed. The Finite Element data is stored in the Systems and Assembly object while the domain information (the Mesh) is stored in the Mesh object. A series of threaded loops are used to run parallel calculations on the objects created and stored within the warehouses.
MOOSE's pluggable systems are documented on the mooseframework.org wiki. Each of these systems has set of defined polymorphic interfaces and are designed to accomplish a specific task within the simulation. The design of these systems is fluid and is managed through agile methods and ticket request system on the Github.org website.
Data Design and Control
At a high level, the system is designed to process HIT input files to construct several objects that will constitute an finite element (FE) simulation. Some of the objects in the simulation may in turn load other file-based resources to complete the simulation. Examples include meshes or data files. The system will then assemble systems of equations and solve them using the libraries of the Code Platform. The system can then output the solution in one or more supported output formats commonly used for visualization.
Human-Machine Interface Design
MOOSE is a command-line driven program. All interaction with MOOSE and MOOSE-based codes is ultimately done through the command line. This is typical for HPC applications that use the MPI interface for running on super computing clusters. Optional GUIs may be used to assist in creating input files and launching executables on the command line.
System Design Interface
All external system interaction is performed either through file Input/Output (I/O) or through local Application Programming Interface (API) calls. Neither the framework, nor the modules are designed to interact with any external system directly through remote procedure calls. Any code to code coupling performed using the framework are done directly through API calls either in a static binary or after loading shared libraries.
Security Structure
The framework does not require any elevated privileges to operate and does not run any stateful services, daemons or other network programs. Distributed runs rely on the MPI library.
Requirements Cross-Reference
- reactor: MultiControlDrumFunction
- 12.1.1The system shall include a function that describes the rotation of multiple control drums
- using control_drum_id.
- without using control_drum_id.
Specification(s): test/multi_cd_func, test/multi_cd_func_noid
Design: MultiControlDrumFunction
Issue(s): #19100
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.1.2The function that describes control drums shall throw an error
- if start_angles and angular_speeds have different lengths.
- if angle_ranges and angular_speeds have different lengths.
- if input control drum parameters are not compatible with MeshMetaData.
- if rotation_end_time is smaller than rotation_start_time.
Specification(s): errors/err_diff_start_angles_size, errors/err_diff_angle_ranges_size, errors/err_diff_metadata_size, errors/err_end_before_start
Design: MultiControlDrumFunction
Issue(s): #19100
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- reactor: AssemblyMeshGenerator
- 12.2.1The system shall generate a 3D square assembly mesh from 2 pin types
Specification(s): square
Design: AssemblyMeshGenerator
Issue(s): #19949
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.2The system shall generate a 3D hexagonal assembly mesh with duct regions with assigned IDs
Specification(s): hex_ductIDs
Design: AssemblyMeshGenerator
Issue(s): #19949
Collection(s): FUNCTIONAL
Type(s): Exodiff
- reactor: AzimuthalBlockSplitGenerator
- 12.2.3The system should modify the azimuthal blocks
- (without the external block) based on the given angle range.
- (with the external block) based on the given angle range.
- (based on block names) based on the given angle range.
Specification(s): test/block_id_in, test/block_id_ext, test/block_name_in
Design: AzimuthalBlockSplitGenerator
Issue(s): #19100
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.4The system shall throw an error
- if old_blocks given as block ids and new_block_ids have different sizes.
- if old_blocks given as block names and new_block_ids have different sizes.
- if new_block_names and new_block_ids have different sizes.
- if old_blocks contains blocks that do not exist in the input mesh.
- if the circular region is overlapped with background region after radius correction.
- if the mesh is too corase for the absorber.
Specification(s): errors/err_diff_block_size_id, errors/err_diff_block_size_name, errors/err_diff_new_block_name_id, errors/err_non_exist_block_name, errors/err_overlapped_circular_regions, errors/err_too_coarse_input_mesh
Design: AzimuthalBlockSplitGenerator
Issue(s): #19100
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- reactor: CoarseMeshExtraElementIDGenerator
- 12.2.5The system shall include the ability to assign coarse element IDs based on a coarse mesh for elements of a fine mesh.
Specification(s): coarse_element_id_test
Design: CoarseMeshExtraElementIDGenerator
Issue(s): #19297
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.6The system shall include the ability to assign extra element IDs based on the subdomain ID of a coarse mesh for elements of a fine mesh.
Specification(s): coarse_element_subdomain_id_test
Design: CoarseMeshExtraElementIDGenerator
Issue(s): #19297
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.7The system shall include the ability to assign extra element IDs based on an extra element ID of a coarse mesh for elements of a fine mesh.
Specification(s): coarse_element_extra_elem_id_test
Design: CoarseMeshExtraElementIDGenerator
Issue(s): #19297
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.8The system shall return an error if
- the coarse mesh extra element id used for assigning does not exist
- the input mesh is not nested in the coarse mesh in CoarseMeshExtraElementIDGenerator
- the fine mesh lies beyond the extent of the coarse mesh
- any node of the fine mesh lies beyond the extent of the coarse mesh
Specification(s): errors/unknown_extra_elem_id, errors/mesh_not_embedded_despite_request, errors/mesh_element_centroid_outside_coarse_mesh, errors/mesh_element_node_outside_coarse_mesh
Design: CoarseMeshExtraElementIDGenerator
Issue(s): #19297
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- reactor: CoreMeshGenerator
- 12.2.9The system shall generate a full 3D square core mesh with 3 pin types and 2 assembly types
Specification(s): square
Design: CoreMeshGenerator
Issue(s): #19949
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.10The system shall generate a 3D square core mesh with empty lattice positions
Specification(s): empty
Design: CoreMeshGenerator
Issue(s): #19949
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.11The system shall generate a 3D hexagonal core mesh with empty lattice positions
Specification(s): hex
Design: CoreMeshGenerator
Issue(s): #19949
Collection(s): FUNCTIONAL
Type(s): Exodiff
- reactor: ExtraElementIDCopyGenerator
- 12.2.12The system shall include the ability to copy an element ID to other element IDs.
Specification(s): copy_element_id_test
Design: ExtraElementIDCopyGenerator
Issue(s): #19297
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.13The system shall return an error if the requested source element ID does not exist on the mesh.
Specification(s): unknown_source_id
Design: ExtraElementIDCopyGenerator
Issue(s): #19297
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- reactor: HexagonConcentricCircleAdaptiveBoundaryMeshGenerator
- 12.2.14The system shall generate a hexagon mesh that adapts one boundary of the mesh saved in the exodus file.
Specification(s): back_only
Design: HexagonConcentricCircleAdaptiveBoundaryMeshGenerator
Issue(s): #18628
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.15The system shall generate a non-adaptive hexagon mesh when inputs and sides_to_adapt are not provided.
Specification(s): empty_inputs
Design: HexagonConcentricCircleAdaptiveBoundaryMeshGenerator
Issue(s): #18628
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.16The system shall throw an error if sides_to_adapt and inputs have different sizes.
Specification(s): err_sides_to_adpat_size
Design: HexagonConcentricCircleAdaptiveBoundaryMeshGenerator
Issue(s): #18628
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- reactor: PatternedHexMeshGenerator
- 12.2.17The system shall stitch hexagon meshes to form a large mesh with hexagon boundary.
Specification(s): hexagon_boundary
Design: PatternedHexMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.18The system shall stitch hexagon meshes to form a large mesh without extra boundary.
Specification(s): none_boundary
Design: PatternedHexMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.19The system shall stitch hexagon meshes twice to form a larger mesh.
Specification(s): patterned_pattern
Design: PatternedHexMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.20The system shall stitch hexagon meshes twice to form a larger mesh with a control drum.
Specification(s): patterned_pattern_cd
Design: PatternedHexMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.21The system shall throw a reasonable error when generating patterned hexagon mesh if one of the input meshes has a flat side facing up.
Specification(s): err_input_flat_side_up
Design: PatternedHexMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.22The system shall throw an error if the input meshes contain different block ids that share the same block name.
Specification(s): err_block_name_conflict
Design: PatternedHexMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.23The system shall throw an error if the layer number of pattern is not odd.
Specification(s): err_pattern_layer
Design: PatternedHexMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.24The system shall throw an error if the layer number of pattern is zero or unity.
Specification(s): err_pattern_unity
Design: PatternedHexMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.25The system shall throw an error if the pattern does not represent a hexagonal pattern.
Specification(s): err_pattern_shape
Design: PatternedHexMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.26The system shall throw an error if the pattern includes input mesh indices that exceed number of elements of inputs.
Specification(s): err_out_of_range_pattern
Design: PatternedHexMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.27The system shall throw an error if background_block_id and duct_block_ids are not provided simultaneously if the mesh has ducts.
Specification(s): err_block_id
Design: PatternedHexMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.28The system shall throw an error if background_block_name and duct_block_names are not provided simultaneously if the mesh has ducts.
Specification(s): err_block_name
Design: PatternedHexMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.29The system shall throw an error if length of duct_block_ids is not consistent with number of ducts.
Specification(s): err_duct_ids
Design: PatternedHexMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.30The system shall throw an error if length of duct_block_names is not consistent with number of ducts.
Specification(s): err_duct_names
Design: PatternedHexMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.31The system shall throw an error if background_block_name or background_block_id are provided when pattern_boundary is none.
Specification(s): err_non_background
Design: PatternedHexMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.32The system shall throw an error if no hexagon size is provided when pattern_boundary is hexagon.
Specification(s): err_no_hexagon_size
Design: PatternedHexMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.33The system shall throw an error if not all the meshes provided in inputs are used in pattern.
Specification(s): err_missing_input_meshes_in_pattern
Design: PatternedHexMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.34The system shall throw an error if no pitch meta data can be obtained from the input mesh.
Specification(s): err_no_appropriate_pitch_meta
Design: PatternedHexMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.35The system shall throw an error if no pattern pitch meta data can be obtained from the input mesh.
Specification(s): err_no_appropriate_pattern_pitch_meta
Design: PatternedHexMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.36The system shall throw an error if input meshes have different pattern pitch meta data.
Specification(s): err_different_pattern_pitch_meta
Design: PatternedHexMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- reactor: PatternedHexPeripheralModifier
- 12.2.37The system shall generate a hexagonal assembly mesh then modify the peripheral region to facilitate further stitching.
Specification(s): single_hex
Design: PatternedHexPeripheralModifier
Issue(s): #20641
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.38The system shall generate a hexagonal assembly mesh with modified peripheral region and retain the specified reporting id.
Specification(s): single_hex_pin_id
Design: PatternedHexPeripheralModifier
Issue(s): #20641
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.39The system shall generate a hexagonal assembly mesh with modified peripheral region and assign new values to the specified reporting id.
Specification(s): single_hex_pin_id_new
Design: PatternedHexPeripheralModifier
Issue(s): #20641
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.40The system shall generate hexagonal assembly meshes with peripheral regions modified in order to stitch them together to form a core mesh.
Specification(s): hex_pattern
Design: PatternedHexPeripheralModifier
Issue(s): #20641
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.41The system shall throw an error if the size of specificed reporting id values does not match size of specified reporting id names.
Specification(s): err_different_id_sizes
Design: PatternedHexPeripheralModifier
Issue(s): #20641
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.42The system shall throw an error if the specified reporting id to be modified does not exist on the input mesh.
Specification(s): err_nonexist_reporting_id
Design: PatternedHexPeripheralModifier
Issue(s): #20641
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.43The system shall throw an error if the input mesh to the hexagonal mesh boundary modifier is generated by an incompatible mesh generator.
Specification(s): err_incompatible_input
Design: PatternedHexPeripheralModifier
Issue(s): #20641
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- reactor: PeripheralRingMeshGenerator
- 12.2.44The system shall add a peripheral ring to to the input mesh without preserving volumes due to polygonization.
Specification(s): core_peripheral_ring_nonpreserved
Design: PeripheralRingMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.45The system shall be able to add a peripheral ring to the input mesh and preserve volumes even with polygonization.
Specification(s): core_peripheral_ring_preserved
Design: PeripheralRingMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.46The system shall be able to add a peripheral ring with radial biasing to the input mesh and preserve volumes even with polygonization.
Specification(s): core_peripheral_ring_biased
Design: PeripheralRingMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.47The system shall be able to add a peripheral ring with boundary layers to the input mesh and preserve volumes even with polygonization.
Specification(s): core_peripheral_ring_boundary_layers
Design: PeripheralRingMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.48The system shall throw an error if the specified inner and outer boundary layers are overlapped.
Specification(s): err_overlapped_boundary_layers
Design: PeripheralRingMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.49The system shall throw an error if a non-2D mesh is given as the input mesh.
Specification(s): err_non_2d_mesh
Design: PeripheralRingMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.50The system shall throw an error if the given boundary of the input mesh has two or more segments.
Specification(s): err_invalid_boundary_type_1
Design: PeripheralRingMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.51The system shall throw an error if the given boundary of the input mesh is an open curve.
Specification(s): err_invalid_boundary_type_2
Design: PeripheralRingMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.52The system shall throw an error if the consecutive nodes of the given boundary of the input mesh do not change monotonically.
Specification(s): err_invalid_boundary_type_3
Design: PeripheralRingMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.53The system shall throw an error if the given peripheral ring radius is not enough to cover the input mesh.
Specification(s): err_small_radius
Design: PeripheralRingMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.54The system shall throw an error if the given external boundary is actually an internal boundary of the input mesh.
Specification(s): err_internal_boundary
Design: PeripheralRingMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- reactor: PeripheralTriangleMeshGenerator
- 12.2.55The system shall generate a triangulation without any Steiner points, given an inner boundary name.
Specification(s): no_steiner_points_inner_boundary_name
Design: PeripheralTriangleMeshGenerator
Issue(s): #18628
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.56The system shall generate a triangulation without any Steiner points, given an inner boundary id.
Specification(s): no_steiner_points_inner_boundary_id
Design: PeripheralTriangleMeshGenerator
Issue(s): #18628
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.57The system shall generate a triangulation with Steiner points.
Specification(s): steiner_points
Design: PeripheralTriangleMeshGenerator
Issue(s): #18628
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.58The system shall throw an error if extra_circle_radii and extra_circle_num_segments are not compatible.
Specification(s): err_steiner_input_length
Design: PeripheralTriangleMeshGenerator
Issue(s): #18628
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.59The system shall throw an error if both inner_boundary_name and inner_boundary_id are both provided.
Specification(s): err_inner_mesh_both_boundary
Design: PeripheralTriangleMeshGenerator
Issue(s): #18628
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.60The system shall throw an error if neither inner_boundary_name and inner_boundary_id are provided.
Specification(s): err_inner_mesh_no_boundary
Design: PeripheralTriangleMeshGenerator
Issue(s): #18628
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.61The system shall throw an error if inner_boundary_name is not defined on the input mesh.
Specification(s): err_inner_mesh_name_not_found
Design: PeripheralTriangleMeshGenerator
Issue(s): #18628
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.62The system shall throw an error if inner_boundary_id is not defined on the input mesh.
Specification(s): err_inner_mesh_id_not_found
Design: PeripheralTriangleMeshGenerator
Issue(s): #18628
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- reactor: PinMeshGenerator
- 12.2.63The system shall generate a 2D square pin mesh with fuel, gap, clad, background regions
Specification(s): square
Design: PinMeshGenerator
Issue(s): #19949
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.64The system shall generate a 3D square pin mesh with ring and background region and tri center elements
Specification(s): tri
Design: PinMeshGenerator
Issue(s): #19949
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.65The system shall throw an error when trying to generate a pin mesh with more than 1 radial region and tri center elements
Specification(s): tri_error
Design: PinMeshGenerator
Issue(s): #19949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.66The system shall generate a 2D hexagonal pin mesh with 2 radial regions
Specification(s): hex
Design: PinMeshGenerator
Issue(s): #19949
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.67The system shall generate a 3D hexagonal pin mesh with radial, background, and duct regions
Specification(s): complex
Design: PinMeshGenerator
Issue(s): #19949
Collection(s): FUNCTIONAL
Type(s): Exodiff
- reactor: PolygonConcentricCircleMeshGenerator
- 12.2.68The system shall generate a hexagon mesh without rings and ducts.
Specification(s): back_only
Design: PolygonConcentricCircleMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.69The system shall generate a hexagon mesh without rings and ducts with one of its flat side facing up.
Specification(s): back_only_flat_up
Design: PolygonConcentricCircleMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.70The system shall generate a hexagon mesh with only one radial layer of elements without rings and ducts.
Specification(s): back_only_one_layer
Design: PolygonConcentricCircleMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.71The system shall generate a hexagon mesh with rings.
Specification(s): rings
Design: PolygonConcentricCircleMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.72The system shall generate a hexagon mesh with ducts.
Specification(s): ducts
Design: PolygonConcentricCircleMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.73The system shall generate a hexagon mesh with rings and ducts.
Specification(s): full
Design: PolygonConcentricCircleMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.74The system shall generate a radially biased hexagon mesh with rings and ducts.
Specification(s): full_biasing
Design: PolygonConcentricCircleMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.75The system shall generate a hexagon mesh with rings and ducts including boundary layers.
Specification(s): full_boundary_layers
Design: PolygonConcentricCircleMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.76The system shall generate a hexagon mesh with rings, ducts and quad central elements.
Specification(s): full_quad
Design: PolygonConcentricCircleMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.77The system shall generate a hexagon mesh with rings, ducts and quad central elements with custom center quad factor.
Specification(s): full_quad_custom
Design: PolygonConcentricCircleMeshGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.78The system shall throw an error if
- num_sectors_per_side and quad_center_elements are not compatible.
- interface_boundary_names has an incorrect length.
- background_block_ids has more than one element when the mesh has ring(s).
- background_block_names has more than one element when the mesh has ring(s).
- background_block_ids has a length other than zero or two when the mesh does not have rings and background_intervals does not equal one.
- background_block_names has a length other than zero or two when the mesh does not have rings and background_intervals does not equal one.
- multiple block ids share a single block name.
- size of num_sectors_per_side is not num_sides.
- num_sectors_per_side elements are not all even.
- ring_radii and ring_intervals have different sizes.
- ring_radii and ring_radial_biases have different sizes.
- ring_block_ids size is not consistent with number of rings in the mesh.
- ring_block_names size is not consistent with number of rings in the mesh.
- ring_radii is not strictly ascending.
- rings are bigger than the polygon.
- duct_sizes and duct_intervals have different sizes.
- duct_sizes and duct_radial_biases have different sizes.
- duct_block_ids size is not consistent with the number of ducts in the mesh.
- duct_block_names size is not consistent with the number of ducts in the mesh.
- duct_sizes is not strictly ascending.
- duct_sizes is non-positive or is low enough to be overlapped with rings.
- duct_sizes is bigger than the polygon.
- boundary layers in background region of a hexagonal cell are overlapped.
- inner and outer ring boundary layer parameters have inconsistent size.
- ring's inner boundary layer has zero interval but non-zero thickness.
- ring's inner boundary layer has nonzero intervals but zero thickness.
- ring's outer boundary layer has zero interval but non-zero thickness.
- ring's outer boundary layer has nonzero intervals but zero thickness.
- ring's boundary layers are thicker than the ring itself.
- inner and outer duct boundary layer parameters have inconsistent size.
- duct's inner boundary layer has zero interval but non-zero thickness.
- duct's inner boundary layer has nonzero intervals but zero thickness.
- duct's outer boundary layer has zero interval but non-zero thickness.
- duct's outer boundary layer has nonzero intervals but zero thickness.
- duct's boundary layers are thicker than the ring itself.
- center_quad_factor is provided for triangular center elements.
Specification(s): exceptions/err_quad_diff_sector_nums, exceptions/err_interface_ids_length, exceptions/err_background_block_ids_1, exceptions/err_background_block_names_1, exceptions/err_background_block_ids_2, exceptions/err_background_block_names_2, exceptions/err_block_ids_with_one_name, exceptions/err_num_sectors_per_side_size, exceptions/err_odd_num_sectors_per_side, exceptions/err_ring_radii_length_1, exceptions/err_ring_radii_length_2, exceptions/err_ring_block_ids, exceptions/err_ring_block_names, exceptions/err_descend_ring_radii, exceptions/err_oversize_ring_radii, exceptions/err_duct_sizes_length_1, exceptions/err_duct_sizes_length_2, exceptions/err_duct_block_ids, exceptions/err_duct_block_names, exceptions/err_descend_duct_sizes, exceptions/err_undersize_duct_sizes, exceptions/err_oversize_duct_sizes, exceptions/err_overlapped_background_boundary, exceptions/err_ring_boundary_layer_param_size, exceptions/err_ring_inner_boundary_layer_zero_interval, exceptions/err_ring_inner_boundary_layer_nonzero_interval, exceptions/err_ring_outer_boundary_layer_zero_interval, exceptions/err_ring_outer_boundary_layer_nonzero_interval, exceptions/err_ring_boundary_layers_oversize, exceptions/err_duct_boundary_layer_param_size, exceptions/err_duct_inner_boundary_layer_zero_interval, exceptions/err_duct_inner_boundary_layer_nonzero_interval, exceptions/err_duct_outer_boundary_layer_zero_interval, exceptions/err_duct_outer_boundary_layer_nonzero_interval, exceptions/err_duct_boundary_layers_oversize, exceptions/err_center_quad_factor_for_tri_elems
Design: PolygonConcentricCircleMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- reactor: CartesianIDPatternedMeshGenerator
- 12.2.79The system shall support the generation of reporting IDs for Cartesian assemblies assigned
- in sequential order for each components in the lattice
- based on the ID of the input pattern tiles
- based on user-defined mapping
Specification(s): assembly/cell, assembly/pattern, assembly/manual
Design: CartesianIDPatternedMeshGenerator
Issue(s): #19217
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.80The system shall support the generation of assembly and pin reporting IDs for Cartesian cores
- with regular square core boundary
- with zagged core boundary formed by removal of certain assemblies on periphery
Specification(s): core/regular_boundary, core/zigzag_boundary
Design: CartesianIDPatternedMeshGenerator
Issue(s): #19217
Collection(s): FUNCTIONAL
Type(s): Exodiff
- reactor: DepletionIDGenerator
- 12.2.81The system shall support the generation of depletion IDs for a 2D reactor core
Specification(s): 2dcore
Design: DepletionIDGenerator
Issue(s): #19617
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.82The system shall support the generation of plane depletion IDs for 2D reactor cores with skipped materials
Specification(s): 2dcore_exclude_material_id
Design: DepletionIDGenerator
Issue(s): #19617
Collection(s): FUNCTIONAL
Type(s): Exodiff
- reactor: HexIDPatternedMeshGenerator
- 12.2.83The system shall support the generation of reporting IDs for hexagonal assemblies assigned
- in sequential order for each components in the lattice
- based on the ID of the input pattern tiles
- based on user-defined mapping
Specification(s): assembly/cell, assembly/pattern, assembly/manual
Design: HexIDPatternedMeshGenerator
Issue(s): #19217
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.84The system shall support the generation of reporting IDs for hexagonal cores
Specification(s): core_base
Design: HexIDPatternedMeshGenerator
Issue(s): #19217
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.85The system shall support the generation of reporting IDs for hexagonal cores with removal of certain assemblies on periphery
Specification(s): core_exclude_id
Design: HexIDPatternedMeshGenerator
Issue(s): #19217
Collection(s): FUNCTIONAL
Type(s): Exodiff
- reactor: SimpleHexagonGenerator
- 12.2.86The system shall include the ability to create a simple hexagon mesh
- with TRI elements
- with QUAD elements
Specification(s): test/tri, test/quad
Design: SimpleHexagonGenerator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- reactor: SubdomainExtraElementIDGenerator
- 12.2.87The system shall include the ability to assign element IDs based on mesh subdomain IDs or names.
Specification(s): subdomain_element_ids_test
Design: SubdomainExtraElementIDGenerator
Issue(s): #19297
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.88The system shall return an error if
- the subdomain vector to use for assigning extra element IDs is empty
- a subdomain is listed more than once when assigning extra element IDs
- the subdomain ids and the extra element id names arent vectors of the same size
- the subdomain ids and the extra element ids to set arent vectors of the same size
- the default extra element IDs arent specified for each extra element id
Specification(s): errors/no_subdomain, errors/same_subdomain, errors/diff_size1, errors/diff_size2, errors/diff_size3
Design: SubdomainExtraElementIDGenerator
Issue(s): #19297
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- reactor: TriPinHexAssemblyGenerator
- 12.2.89The system shall be able to generate a tri-pin hexagonal assembly mesh.
Specification(s): tri_pin
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.90The system shall be able to generate a tri-pin assembly mesh by specifying the apothem size.
Specification(s): tri_pin_apothem
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.91The system shall generate a tri-pin assembly mesh with three identical pins.
Specification(s): tri_pin_dup
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.92The system shall be able to generate a dummy core mesh containing a tri-pin assembly.
Specification(s): dummy_core
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 12.2.93The system shall throw an error if the number of rings radii specified does not match either one or the number of pins
Specification(s): err_ring_radii_size
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.94The system shall throw an error if the largest ring specified exceeds the assembly boundary.
Specification(s): err_ring_radii_oversize
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.95The system shall throw an error if the parameter specifying the radial intervals of ring regions does not have appropriate size.
Specification(s): err_ring_intervals_size
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.96The system shall throw an error if the parameter specifying the block ids of ring regions does not have appropriate size.
Specification(s): err_ring_block_ids_size
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.97The system shall throw an error if the parameter specifying the radial intervals of ring regions is inconsistent with the parameter specifying the sizes of ring regions.
Specification(s): err_ring_intervals_consistency
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.98The system shall throw an error if the parameter specifying the block ids of ring regions is inconsistent with the parameter specifying the sizes of ring regions (case 1).
Specification(s): err_ring_block_ids_consistency_1
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.99The system shall throw an error if the parameter specifying the block ids of ring regions is inconsistent with the parameter specifying the sizes of ring regions (case 2).
Specification(s): err_ring_block_ids_consistency_2
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.100The system shall throw an error if the parameter specifying the block names of ring regions is inconsistent with the parameter specifying the sizes of ring regions (case 1).
Specification(s): err_ring_block_names_consistency_1
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.101The system shall throw an error if the parameter specifying the block names of ring regions is inconsistent with the parameter specifying the sizes of ring regions (case 2).
Specification(s): err_ring_block_names_consistency_2
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.102The system shall throw an error if the parameter specifying the block names of ring regions is inconsistent with the parameter specifying the block ids of ring regions.
Specification(s): err_ring_block_names_consistency_3
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.103The system shall throw an error if the size of the parameter specifying the block ids of background region is not one when all the three sections have rings.
Specification(s): err_background_block_ids_consistency_1
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.104The system shall throw an error if the size of the parameter specifying the block names of background region is not one when all the three sections have rings.
Specification(s): err_background_block_names_consistency_1
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.105The system shall throw an error if the size of the parameter specifying the block ids of background region is not two when ring-free section exists.
Specification(s): err_background_block_ids_consistency_2
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.106The system shall throw an error if the size of the parameter specifying the block names of background region is not two when ring-free section exists.
Specification(s): err_background_block_names_consistency_2
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.107The system shall throw an error if the size of the parameter specifying the block ids of background region is not one when all the sections are ring-free and background_intervals is 1.
Specification(s): err_background_block_ids_consistency_3
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.108The system shall throw an error if the size of the parameter specifying the block names of background region is not one when all the sections are ring-free and background_intervals is 1.
Specification(s): err_background_block_names_consistency_3
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.109The system shall throw an error if extra element integer values of the pins are provided without specifying extra element integer names.
Specification(s): err_no_pin_id_name
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.110The system shall throw an error if extra element integer values specified do not have the correct size.
Specification(s): err_wrong_pin_id_values
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 12.2.111The system shall throw an error if the offset of the ring region center moves the center of the ring out of the hexagon assembly region.
Specification(s): err_over_offset
Design: TriPinHexAssemblyGenerator
Issue(s): #20949
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException