Reactor models sorted by input file features

While every advanced reactor has unique characteristics, with different coolants, fuel shapes or control mechanisms, most NEAMS tools are at their core rather reactor-agnostic and thus there are many similarities in the input files. The reader may find below an index of the features that are present in the input files of the virtual test bed. If the exact feature is not present for the reactor you wish to see it for, the inputs for another reactor type will likely help creating it.

Mesh treatment

In-MOOSE basic mesh generation

In-MOOSE reactor module mesh generation

Cubit mesh generation

The mesh generation scripts using external software are not included in the input file, but generally reside in the same folder in the repository.

Coupling through MultiApps

Multiphysics but same spatial scale simulations

Multiphysics and multiscale simulations

Restarting from a previous simulation

Transient simulations are often started from stable steady state initializations rather than uniform power, temperature, flux, etc distributions. This can be done in numerous ways:

Checkpoint

Documentation for the Checkpoint system

Binary restart

Binary restart is only used by Griffin. It is only used to restart the neutronics simulation. Any MultiApps has to be initialized using another restart solution. For Checkpoint, the additional Problem/force_restart=true must be specified. The MRAD and PBMR-400 models listed below are an example of this.

Restarting from Exodus simulation files

Mixed Exodus/Checkpoint Multiapp restart

Computing requirements

Runs on a laptop or workstation

HPC required

GPU-enabled

commentnote

If there is a feature which you would find useful to be highlighted, please reach out to VTB team

commentnote

The input file links are not automatically checked by the VTB automated testing. If you hit a broken link please report it to the VTB team