External Interfaces (Plugins)

The current analysis codes with established rapyds interfaces are listed below.

Codes with a defined rapyds interface

Analysis Code	Supported Versions	Area	Notes
Serpent [1]	2.1.23 to 2.1.29	Neutronics (Monte Carlo)
MCNP [1]	5.1, 6.1, 6.2	Neutronics, Particle Transport (Monte Carlo)
MGRAC [2]	1.x, 2.x	Neutronics (Nodal Diffusion) [3]
COGENT [2]	0.x	Neutronics, Particle Transport (Monte Carlo)	Both the code and the interface is still under heavy development.
DeCART2D [1]	1.x	Neutronics (2D MOC)	Current version of interface restricted to prismatic HTR designs.
CAPP [1]	1.x	Neutronics (Finite Element Diffusion) [3]	Limited to analysis of prismatic HTR designs.
RELAP [1]	5.x	Thermal Hydraulics (System) [4]	Limited to the passing of neutronics parameters, and some basic output processing.
GAMMA+ [1]		Thermal Hydraulics (System) [4]	See above.

[1] (1,2,3,4,5,6)

Externally developed code, which is distributed and licensed separately. Only interfaces are available.

[2] (1,2)

In house developed analysis code.

[3] (1,2)

Also supports embedded thermal hydraulic solvers, if available.

[4] (1,2)

Application level interface only, as the rapyds data model does not contain all the required elements.

See also Plugin Data Model and Application Support for more information on the capabilities of these plugins.

Adding Interfaces

Interfaces are developed using a common API, and can be added without access to, or modification of the base rapyds source. This system uses a template engine, which is used to produce input from the various rapyds data elements and application parameters. The plugin interface is illustrated below.

Schematic illustration of the RAPYDS plugin interface.

Regions in blue denote system elements, while red regions denote parts specific to the plugin.

The only requirement for the functionality of a plugin, is the implementation of application input templates, for all application modes the target code should support, as well as the associated recipe(s), which is used to process output into a standardized data object. To avoid a lot of duplication in these templates, templates can also be developed at the data element level.