Input Manual RELAP7
Input Manual RELAP7
March 2018
March 2018
http://www.inl.gov
Gregg Swindlehurst
David Andrs
Joshua Hansel
Russell Johns
Richard Martineau
March 2018
March 2018
http://www.inl.gov
5
SUMMARY
The RELAP-7 code is the next generation nuclear reactor system safety analysis code being
developed at the Idaho National Laboratory (INL). The code is based on the INL’s modern
scientific software development framework, MOOSE (Multi-Physics Object Oriented Simulation
Environment). The overall design goal of RELAP-7 is to take advantage of the previous thirty
years of advancements in computer architecture, software design, numerical integration
methods, and physical models. The end result will be a reactor systems analysis capability that
retains and improves upon RELAP5’s capability and extends the analysis capability for all reactor
system simulation scenarios.
RELAP-7 will be the next generation tool in the RELAP reactor safety/systems analysis
application series. The key to the success of RELAP-7 is the simultaneous advancement of
physical models, numerical methods, and software design while maintaining a solid user
perspective. Physical models include both PDEs (Partial Differential Equations) and ODEs
(Ordinary Differential Equations) and experimental based closure models. RELAP-7 utilizes well-
posed governing equations for compressible two-phase flow, which can be strictly verified in a
modern verification and validation effort. Closure models used in the TRACE code have been
selected to reflect the progress made during the past three decades. RELAP-7 uses modern
numerical methods, which allow implicit time integration, second-order schemes in both time
and space, and strongly coupled multi-physics.
RELAP-7 is written with object oriented programming language C++. By using the MOOSE
development environment, the RELAP-7 code is developed by following the same modern
software design paradigms used for other MOOSE development efforts. The code is easy to
read, develop, maintain, and couple with other codes. Most importantly, the modern software
design allows the RELAP-7 code to evolve efficiently with time. MOOSE is an HPC development
and runtime framework for solving computational engineering problems in a well planned,
managed, and coordinated way. By leveraging millions of lines of open source software
packages, such as PETSc (a nonlinear solver developed at Argonne National Laboratory) and
LibMesh (a Finite Element Analysis package developed at University of Texas), MOOSE reduces
the expense and time required to develop new applications. MOOSE provides numerical
integration methods and mesh management for parallel computation. Therefore RELAP-7 code
developers have been able to focus more upon the physics and user interface capability. There
are currently over 20 different MOOSE based applications ranging from 3-D transient neutron
transport, detailed 3-D transient fuel performance analysis, to long-term material aging. Multi-
physics and multi-dimensional analysis capabilities, such as radiation transport and fuel
performance, can be obtained by coupling RELAP-7 and other MOOSE-based applications
through MOOSE and by leveraging with capabilities developed by other DOE programs. This
allows restricting the focus of RELAP-7 to systems analysis type simulations and gives priority to
retain and significantly extend RELAP5’s capabilities.
6
This RELAP-7 Input Manual provides the users with a description of the input parameters for
which character strings or numerical values are provided to build a RELAP-7 input file. Some of
the input parameters are required for any RELAP-7 input file, and many others represent
optional input file parameters that can be provided at the discretion of the user. Some of the
input parameters have default values that can be superseded by user specified values.
The RELAP-7 Theory Manual describes the theoretical basis, the development of the equations
and models used in the simulation, and the numerical solution methods. The RELAP-7 User’s
Guide focuses on assisting users in developing input models by use of a progression of sample
problems of increasing complexity. These two manuals, in concert with this RELAP-7 Input
Manual, provide the necessary information to apply the RELAP-7 code to system thermal-
hydraulic analysis.
7
1.0 INPUT FILE DESCRIPTION
RELAP-7 uses a block-structured input file syntax, with each block having a standard name to indicate
the required and optional input data. Each block name is identified with brackets (“[standard name]“)
at the beginning of the block, and empty brackets (“[ ]”) at the end.
Some input file blocks may contain sub-blocks identified similarly with (“[./name]”at the beginning of
the sub-block and “[../]”) at the end. Each sub-block must have an unique name (i.e. cannot use
reserved names such as ‘pipe’ – e.g. need to use ‘pipeXX”) when compared with all other subblocks in
each specified block. Each sub-block also has a standard type identified with (“type = standard name”)
to indicate the sub-block specific input file parameters.
Input files are generally specified using syntax that consists of parameter and value pairs with an “equal
sign” between them. The parameter is a block-specific and sub-block-specific standard string, and the
value may be a string, an integer, a real number, or a list of strings, integers, or real numbers. Lists are
given in single quotes and are separated by whitespace.
If a “parameter = value” pair is repeated in the input file, then the last appearance will be used.
The open source “Atom” editor (https://atom.io) is recommended for editing RELAP-7 input files as it
has plugins that assist with input file creation and editing. Drop-downs of parameter lists show the
available parameters, the required parameters, default values, and parameter descriptions.
The following report sections have detailed descriptions of input file parameters for each input file
block, and for commonly used sub-blocks. Additional parameters that are not commonly used are not
included in the table. A file with a complete list of RELAP-7 input file parameters can be obtained via the
command (“./relap-7-opt –dump >filename”).
8
2.0 GLOBAL PARAMETERS
The global parameters [GlobalParams] block includes those input parameters used by RELAP-7 that can
specified generically, such as the choice of stabilization scheme to be used in the numerical solution, and
the initial values of pressure , velocity, and temperature of the system being modeled. The generic
parameter values specified in the global parameters block are used throughout the model unless they
are superseded by specifying those same parameters in any block or subblock. None of the parameters
are required. Typically, any input that can be specified generically or mostly generically are included in
the [GlobalParams] block to reduce the volume of the input file.
In the following table the input file parameters for the [GlobalParams] block are listed.
9
phase fluid properties used
initial_p_liquid Initial pressure for liquid
10
3.0 STABILIZATIONS
The stabilizations [Stabilizations] block creates the stabilization options that can be selected by the
GlobalParams block or by Pipe components to stabilize the numerical solution method used in RELAP-7.
The stabilization options can differ with regard to the applicability to single-phase or two-phase
conditions. More than one option can be created for subsequent selection in the same input file.
Other stabilization options are included in RELAP-7 but are not specified here.
In the following sections the input file parameters that typically require values to be entered (e.g.
required and no default values) for each of the [Stabilizations] sub-blocks are listed.
3.2 Lapidus
3.3 SUPG
3.4 Pressure
13
4.0 FLUID PROPERTIES
The fluid properties [FluidProperties] block creates sub-blocks of various fluid properties coded in RELAP-
7 (e.g. water, air/water, helium, or nitrogen) that can then be referencedin other blocks by components
including fluid. For water the IAPWS 95 water properties are used. In addition, if only the liquid or
steam phase is present, the IAPWS 95 water properties for either single phase can be specified for
computational efficiency, but are not necessary.
Properties for other fluids, such as sodium or an ideal gas, are included in RELAP-7 but are not specified
here.
In the following table the input file parameters for the [FluidProperties] sub-blocks are listed.
15
5.0 PRECONDITIONING
The preconditioning block [Preconditioning] specifies the preconditioner to be used by the RELAP-7
code. The single matrix preconditioner (SMP) is the recommended option.
Other preconditioners and options are included in RELAP-7 but are not specified here.
In the following table the Input File Parameters for the SMP preconditioner sub-blocks is listed.
16
6.0 OUTPUTS
The outputs [Outputs] block specifies the RELAP-7 output files that are generated for run-time or post-
processing applications.
Other output options are included in RELAP-7 but are not specified here.
In the following sections the output file format options and parameters for the[Outputs] sub-blocks are
listed.
6.2 Exodus
The primary use of the exodus output file is for use by the Paraview post-processor.
6.3 Console
The console output format is viewable on the computer screen.
18
are forced to occur
show Times at which the output and
solution are forced to occur
sync_only Only export results at sync times
19
7.0 POSTPROCESSORS
The post-processor [Postprocessors] block specifies sub-blocks that calculate values that are used for
run-time or post-processing applications.
Other post-processor options are included in RELAP-7 but are not specified here.
In the following sections the input file parameters for the [Postprocessors] sub-blocks are listed.
Post-processors that include the “boundary” parameter refers to [Inlet] and [Outlet] components and to
two-dimensional [HeatStructure] components.
Vector post-processors exist in RELAP-7 for applications such as fluid temperatures along the length of a
pipe. These are not specified here.
Commonly used post-processors are the [PointValue] that outputs the value of a parameter at a specific
location (x, y, z), the [ElementExtremeValue] that outputs a maximum or minimum value of a
component parameter, and the [TimeStepSize] that outputs the time step size.
20
[Outputs] will be used.
22
7.5 Difference
The difference post-processor [DifferencePostprocessor] sub-block computes the difference between
two post-processors.
23
(nonlinear|linear|timestep_end|ti
mestep_begin|custom) to execute
only at that moment
outputs The output names (i.e. console,
csv, exodus) for this post-
processor. If none provided then
all specified in [Outputs] will be
used.
25
mestep_begin|custom) to execute
only at that moment
outputs The output names (i.e. console,
csv, exodus) for this post-
processor. If none provided then
all specified in [Outputs] will be
used.
value_type max Type of extreme value to return:
'max returns the maximum value;
'min' returns the minimum value;
'abs_max' returns the maximum
absolute value; 'abs_min' returns
the minimum absolute value.
26
7.11 Linear Combination
The linear combination post-processor [LinearCombinationPostprocessor] sub-block calculates the sum
of pairs of post-processor output values (input to this post-processor) multiplied by coefficients
(parameter values specified in this postprocessor), plus a constant value (specified in this post-
processor).
27
arhouA Product of void fraction * density
*velocity*area
boundary The unique name(s) of a boundary
condition component(s) (e.g.
InletXX).
execute_on timestep_end Set to
(nonlinear|linear|timestep_end|ti
mestep_begin|custom) to execute
only at that moment
outputs The output names (i.e. console,
csv, exodus) for this post-
processor. If none provided then
all specified in [Outputs] will be
used.
vel Velocity
28
processor. If none provided then
all specified in [Outputs] will be
used.
30
7.17 Number of Elements
The number of elements post-processor [NumElems] sub-block provides the total number of elements
in the simulation model.
31
7.19 Number of Nodes
The number of nodes post-processor [NumNodes] sub-block outputs the number of nodes.
32
7.21 Number of Residual Evaluations
The number of residual evaluations post-processor [NumResidualEvaluations] sub-block outputs the
number of residual evaluations at each time step.
7.32 Sum
The sum post-processor [SumPostprocessor] computes the sum of two post-processors.
40
8.0 EXECUTIONER
The executioner [Executioner] block specifies either the input file as either a transient [Transient] or a
control logic [ControlLogic] execution, and includes parameters and values related to time step selection
and solver tolerances.
Other executioners and options are included in RELAP-7 but are not specified here.
In the following sections the input file parameters for the [Executioner] blocks and sub-blocks are listed.
8.1 Transient
The transient [Transient] sub-block specifies most of the parameters that control a transient execution.
8.1.2 Quadrature
The quadrature [Quadrature] sub-block specifies the type of numerical integration (quadrature) with the
two options being trapezoidal and Gaussian (recommended), and the order of the numerical integration
with the options being first and second (recommended). For some problems that have stability issues
with the recommended quadrature the other option (TRAP/FIRST) may have some benefit.
43
9.0 FUNCTIONS
The functions block [Functions] provides any functions used by RELAP-7 code such as reactor power as a
function of time, pipe flow area as a function of length, or a pressure boundary condition as a function
of time. Specific functions are available for selection as sub-blocks.
Other functions are included in RELAP-7 but are not specified here.
In the following sections the input file parameters for the [Functions] sub-blocks are listed.
9.1 Constant
The constant function [ConstantFunction] returns a constant value.
9.2 Linear
The linear function [LinearFunction] calculates the value from a linear equation (a+b*x) given constant
values of ‘a’ and ‘b’, and a function ‘x”.
44
9.3 Parsed
The parsed function calculates a value from a user-defined function consisting of variable/value pairs,
numerical values, generic parameters (e.g. “t” (time), “x, y, z” (coordinates), “pi” (π), and mathematical
functions (e.g. “sin’ for sine). Refer to
http://warp.povusers.org/FunctionParser/fparser.html#functionsyntax for a complete list of syntax.
46
9.6 Piece-Wise Linear
The piece-wise linear function [PiecewiseLinear] linearly interpolates between values of (x, y) data pairs.
47
10.0 HEAT STRUCTURE MATERIALS
The heat structure materials [HeatStructureMaterials] block specifies the RELAP-7 parameters
necessary to describe the physical properties of solid materials such as ceramics and metals.
The input is specified in solid materials properties [SolidMaterialProperties} sub-blocks for each
material type.
In the following table the input file parameters for the [SolidMaterialPropertiess] sub-blocks are listed.
k Thermal conductivity
rho Density
48
11.0 CONTROLS
The controls [Controls] block specifies the modeling of control systems in RELAP-7 input files. A set of
sub-blocks describe specific control system parameters.
All of the controls that are included in RELAP-7 are specified here.
Some of the parameters that are not typically used are not included.
In the following sections the input file parameters for the [Controls] sub-blocks are listed.
49
Input File Parameters Parameter Values
Description
(Note: Required are bolded) (Note: Defaults are bolded)
[./name] Unique name Designates sub-block control name
type PIDControl Designates control is a PID control
initial_value The initial value for the integral
part
input The name of the control data that
is the input
K_d The coefficient for the derivative
term
K_i The coefficient for the integral
term
K_p The coefficient for the proportional
term
set_point The name of the control data with
the set point
50
the control that returns the value of the parameter.
11.6 Terminate
This control [TerminateControl] terminates the simulation when the ‘output’ value of the parameter
‘threshold’ in a UnitTripContol reaches the specified threshold value.
The auxiliary kernels [AuxKernels] block includes a variety of sub-blocks that are used to calculate
52
specific quantities of interest using component parameter output values as inputs, along with constants
specified as sub-block inputs. The auxiliary kernel output values can then be used for a variety of
purposes.
Other auxiliary kernels are included in RELAP-7 but are not specified here.
In the following sections the input file parameters for the [AuxKernels] sub-blocks are listed.
12.1 Constant
The constant auxiliary kernel [ConstantAux] sub-block specifies an input numerical value that is assigned
as a component parameter value or a component boundary parameter value in the simulation model.
12.2 Function
The function auxiliary kernel [FunctionAux] sub-block samples a function output value in space and time,
as applicable, and assigns it as a component parameter value or a component boundary parameter
value in the simulation model.
54
block The list of component names to be
included in the calculation
execute_on linear Set to
(nonlinear|linear|timestep_end|ti
mestep_begin|custom) to execute
only at that moment
58
13.0 COMPONENTS
The components [Components] block specifies within sub-blocks the parameters used for each of the
component types used in RELAP-7 simulation models. In RELAP-7 the terminology ‘component’ refers to
a zero, one, or two-dimensional element of a fluid system simulation model. A component can
represent a physical structure such as a pipe, valve, pump, or heat exchanger. A component can also be
a boundary condition such as a pressure sink or a mass flowrate. A network of components is specified
to represent the system being simulated using a three-dimensional mesh.
For each component type most of the parameters are required to fully describe the component,
although the list of parameters can vary significantly depending on the component type. Parameter
values specified generically in the [GlobalParams] block are superseded by specifying component-
specific values.
The input file parameters for each component type are listed in the following sections. Some
component parameters that are not typically used are not included.
volume Volume
60
is_actuated_by_pressure_diff ‘true’ if the valve is actuated by Δp;
erence ‘false’ if actuation is by inlet
pressure
K Forward flow form loss coefficients
at the inlet and at the outlet
outputs Name of the 1D component at the
outlet (e.g. ‘PipeXX(in))
response_time_close Response time to close
volume Volume
61
type CoreChannel Designates component is a core
channel
A Area of coolant channel
62
coefficient. Normally this is not
specified and the closures (boiling
curve) are used.
PoD 1 Pitch to diameter ratio for fuel rod
lattice
depth Thickness of plate fuel
13.4 Downcomer
The BWR downcomer [Downcomer] component connects the feedwater pipe, the separator dryer
discharge, the steam dome, and the downcomer outlet. The downcomer is separated into a vapor
region above the mixture level, and a liquid region below the mixture level. During a transient the
mixture level is tracked. The vapor pressure is the steam dome pressure. The downcomer component
is a junction component with volume.
64
dome_component Steam dome component name to
provide the vapor pressure
initial_level Initial iquid level
volume Volume
f Wall friction
66
initial_vel_vapor Initial velocity for the vapor phase
67
type HXConnector Designates component is a heat
exchanger connector
hs The name of the heat structure
component
hs_side The side of the heat structure
69
13.10 Ideal Pump
The ideal pump [IdealPump] component is a junction component that provides a mass flow rate
boundary condition between two pipe components.
13.11 Inlet
The inlet [Inlet] component provides a flow boundary condition to the inlet of a pipe component.
Various combinations of parameters options are available to specify the fluid state. Selection of the
parameter combinations need to avoid over-specification.
p Pressure
13.12 Junction
The junction [Junction] component can connect multiple pipes at the inlet and outlet but is restricted to
single-phase fluids.
13.13 Outlet
The outlet [Outlet] component provides a backpressure boundary condition to the outlet of a pipe
component. An example would be a pressure sink for a relief valve. There is an option for a reversible
outlet with flow at the outlet conditions from the outlet component into the pipe component.
13.14 Pipe
The pipe [Pipe] component is the fundamental 1D component for modeling a volume of fluid in space. A
pipe component connects to only one other 1D component at each end of the pipe via one of several
junction components.
f Wall friction
74
initial_vel Initial velocity for single-phase
76
used.
initial_T Initial temperature for single-phase
77
13.16 Point Kinetics
The point kinetics [PointKinetics] component solves the point kinetics equations to determine the
change in reactor power. Moderator density or temperature reactivity feedback, and fuel temperature
(Doppler) reactivity feedback are included via the [ReactivityFeedback] component. An additional
reactivity component, such as control rod reactivity as a function of time can be included.
78
lam_U239 0.000491 U-239 decay constant
79
13.18 Pump
The pump [Pump] component is a junction that increases the pressure (head) by a user-specified value,
or by connection to a turbine component that provides shaft work.
A_ref Area
81
13.20 Simple Junction
The simple junction [SimpleJunction] component is a junction that is only applicable when the two
connecting pipes have the same area. This is the only junction that currently can model two-phase flow.
13.22 Turbine
The turbine [Turbine] component is a simplified turbine junction component applicable to a Terry
turbine, and not for a large power generation turbine.
82
initial_p Initial pressure
13.23 Valve
The valve [Valve] component is a junction component connecting two pipe components that opens or
closes at a specified time with a specified stroke time.
A_ref Area
84
13.25 Wet Well
The wet well [WetWell] component is a simplified junction component with a specified gas (e.g. air or
nitrogen) over a liquid water pool in a rectangular (cubic) volume representation. The major design
features of a BWR wet well suppression pool are included. An example application is to condense the
exhaust steam from a Terry turbine. The model is not suitable for large steam flowrates such as a LOCA
blowdown.
Parameter Values
Input File Parameters
Description
(Note: Defaults are
(Note: Required are bolded)
bolded)
[./name] Unique name Designates sub-block component name
86