- heated_lengthHeated length [m]
C++ Type:double
Unit:(no unit assumed)
Controllable:No
Description:Heated length [m]
- inputThe corresponding subchannel mesh
C++ Type:MeshGeneratorName
Controllable:No
Description:The corresponding subchannel mesh
- n_cellsThe number of cells in the axial direction
C++ Type:unsigned int
Controllable:No
Description:The number of cells in the axial direction
- nringsNumber of fuel Pin rings per assembly [-]
C++ Type:unsigned int
Controllable:No
Description:Number of fuel Pin rings per assembly [-]
- pitchPitch [m]
C++ Type:double
Unit:(no unit assumed)
Controllable:No
Description:Pitch [m]
SCMTriPinMeshGenerator
Creates a mesh of 1D fuel pins in a triangular lattice arrangement
Overview
This mesh generator creates the mesh were the SCM
solution variables associated with the pins live. The user needs to provide the "nrings" parameter which defines the number of fuel pin rings. For triangular sub-assemblies, one nring means that there is one central pin in the (0 0 0) position and six neighboring ones on the the vertices of a normal hexagon. The number of cells in the -z direction is given by "n_cells". The distance of the pins from eachother is given by the "pitch" parameter and the total length of the pins in the -z direction is defined by the parameters: "heated_length","unheated_length_entry","unheated_length_entry". Last, "input" is a parameter that takes the name of an object of type SCMTriSubChannelMeshGenerator so the user must be careful to define consistent parameters across both MeshGenerators
. The center of the mesh is the origin.
Example Input File Syntax
[TriSubChannelMesh<<<{"href": "../../syntax/TriSubChannelMesh/index.html"}>>>]
[subchannel]
type = SCMTriSubChannelMeshGenerator<<<{"description": "Creates a mesh of 1D subchannels in a triangular lattice arrangement", "href": "SCMTriSubChannelMeshGenerator.html"}>>>
pin_diameter<<<{"description": "Rod diameter [m]"}>>> = 0.01
dwire<<<{"description": "Wire diameter [m]"}>>> = 0.002
hwire<<<{"description": "Wire lead length [m]"}>>> = 0.0833
spacer_z<<<{"description": "Axial location of spacers/vanes/mixing_vanes [m]"}>>> = '0'
spacer_k<<<{"description": "K-loss coefficient of spacers/vanes/mixing_vanes [-]"}>>> = '5.0'
[]
[duct]
type = SCMTriDuctMeshGenerator<<<{"description": "Creates a mesh of 1D duct cells around a triangular lattice subassembly", "href": "SCMTriDuctMeshGenerator.html"}>>>
input<<<{"description": "The corresponding subchannel mesh"}>>> = subchannel
[]
[]
(moose/modules/subchannel/test/tests/problems/SFR/sodium-19pin/test19_monolithic.i)Input Parameters
- block_id1Domain Index
Default:1
C++ Type:unsigned int
Controllable:No
Description:Domain Index
- unheated_length_entry0Unheated length at entry [m]
Default:0
C++ Type:double
Unit:(no unit assumed)
Controllable:No
Description:Unheated length at entry [m]
- unheated_length_exit0Unheated length at exit [m]
Default:0
C++ Type:double
Unit:(no unit assumed)
Controllable:No
Description:Unheated length at exit [m]
Optional Parameters
- enableTrueSet the enabled status of the MooseObject.
Default:True
C++ Type:bool
Controllable:No
Description:Set the enabled status of the MooseObject.
- save_with_nameKeep the mesh from this mesh generator in memory with the name specified
C++ Type:std::string
Controllable:No
Description:Keep the mesh from this mesh generator in memory with the name specified
Advanced Parameters
- nemesisFalseWhether or not to output the mesh file in the nemesisformat (only if output = true)
Default:False
C++ Type:bool
Controllable:No
Description:Whether or not to output the mesh file in the nemesisformat (only if output = true)
- outputFalseWhether or not to output the mesh file after generating the mesh
Default:False
C++ Type:bool
Controllable:No
Description:Whether or not to output the mesh file after generating the mesh
- show_infoFalseWhether or not to show mesh info after generating the mesh (bounding box, element types, sidesets, nodesets, subdomains, etc)
Default:False
C++ Type:bool
Controllable:No
Description:Whether or not to show mesh info after generating the mesh (bounding box, element types, sidesets, nodesets, subdomains, etc)