Upcoming:Datamesh Dataifc

From Serpent Wiki
Revision as of 15:41, 8 February 2021 by Ville Valtavirta (Talk | contribs)

Jump to: navigation, search
This page describes an upcoming feature being developed for Serpent 2, which is not yet available in the publicly distributed version.

datamesh (general mesh definition)


Defines a structured mesh that can be used in many places. If the same mesh is used for multiple purposes, the mesh search typically has to be done only once.

NAME  : name of the mesh
TYPE  : mesh type (1 - cartesian, 2 - cylindrical, 3 - spherical, 4 - hexx, 5 - hexy, 6 -irreqularly spaced Cartesian, 7 - irregularly spaced Cyclindrical, 9 - nested mesh with regular structure)
LC  : flag to use local coordinates (lowest universe) for mesh-index search instead of global (0/1/yes/no)
MINn MAXn Nn  : boundaries of the mesh and number of bins in each direction


  • Support for irregular structured meshes will most likely be added at some point.
  • Similar input for unstructured meshes will most likely be added at some point.

dataifc (general interface definition)


Defines an interface providing some data to Serpent on some mesh. The data can be updated during runtime. Currently only used for bringing in atomic densities.

MESHNAME  : name of the mesh that the data lies on
DATAFILE  : path to file containing the data (one value for each mesh cell). Atomic densities use the default unit 1024/cm3.
ZAI  : the ZAI of the nuclide for which the atomic density is supplied (e.g. 50100 for B-10)
MATERIAL  : name of the material for which to apply the atomic density


  • Input syntax will probably undergo big changes.
  • The material must already contain the nuclide for which the atomic density is being linked.
  • If the material contains more than one instance of the nuclide (can happen with mixtures), the data will most likely not be applied properly.
  • One should be able to supply the atomic density of ZAI to more than one material with the same interface by simply supplying a (space separated) material name list instead of a single material name. hasn't been tested
  • Will most likely not work properly with burnable materials.
  • Has only been tested with optimization mode 4, might yield strange results or crash for other optimization modes.
  • Has not been tested with multi-physics interfaces, might yield strange results or crash.