Skip to content

Add implementation of generate_mesh_input in PyGriffinConnect

Kumar, Shikhar requested to merge pygriffin_meshgen into pygriffin_initial

This MR adds functionality for generate_mesh_input in PyGriffinConnect which takes the SON-defined geometry and MOOSE mesh input parameters and builds the associated MOOSE mesh input file.

A few notes:

  • Currently dummy assemblies are not implemented in logic (needs discussion)
  • Instead of assigning a max radial mesh size, radial discretizations are set as either tri (6 trianges per hexagon) or quad (2 quadrilaterals per hexagon)
  • All assemblies defined in SON geometry are defined MOOSE mesh input regardless of whether they are used in the core or not. The input file will be cleaner if only the assemblies actually used in the core are defined in the mesh input. Is there a Geometry-related variable that stores this information or would the best way to do this is to iterate through each assembly in the core geometry?
  • Some variables such as mapping of assemblies to block id's should probably be stored a member variable of UserObject or as a global variable so that downstream functions such as material-mesh assignment can use this information later on

Merge request reports