]>
Logging level of the Richards solver.
info
trace, debug, info, warning, error, critical
Path to the directory where most of the outputs are stored.
DORiE will attempt to create it if it does not exist.
./
path
Base file name for VTK output.
string
Plot vertex based (``true``) or cell-centered (``false``)
data into VTK files. Vertex based data might render sharp
parameterization boundaries inappropriately.
System tests and plotting functions (``dorie plot``) require
cell-centered data.
true, false
true
Policy to write the data.
endOfRichardsStep
endOfTransportStep, endOfRichardsStep, none
Defines whether VTK files should include the hydrodynamic
dispersion tensor. Tensors are written in 3D and have 9 componentents
independently of the world dimension. This can be easily be visualizated
in Paraview with the ``Tensor Glyph`` filter.
true, false
false
Plot VTK files with virtually refined grids. VTK only
supports bilinear triangulations and displays higher-order solutions
inappropriately. Use level 0 for order 1, and level N for order N.
For level > 0, the printed grid does not resemble the actual grid.
This parameter defaults to 0 if not given in the config file. Notice
that subsampling significantly increases the output file size!
int
0
Defines whether VTK files should be written as ASCII (``true``)
or binary (``false``). ASCII is easier to parse in case you want to write
your own post-processing, but takes a lot more space on your hard drive.
true, false
false
Path to the boundary condition file.
path
Type of spatial segmentation of the boundaries specified in the BC file
rectangularGrid
rectangularGrid
Choose type of boundary segmentation: rectangularGrid
Whether to interpolate between the boundary conditions
at different times linearly (``true``) or not at all (``false``). May require
different boundary condition files.
true, false
false
Type of the input value for the dirichlet condition.
soluteConcentration, totalSolute
soluteConcentration
The data type representing the initial condition. Either an
HDF datafile (``data``), or analytic equations (``analytic``).
data, analytic
analytic
Choose initial condition type: data, analytic
The physical quantity represented by the initial condition
data.
soluteConcentration
soluteConcentration
Choose quantity represented: soluteConcentration
Equation for the initial condition
equation [x,y,z,h]
0
Path to the initial condition data file
(``data`` type only). DORiE currently only supports H5 files with
file extension ``.h5``.
path
Dataset to use as initial condition (``data`` type only).
string
Interpolation type used for the data (``data`` type only).
nearest
nearest
Starting time in seconds.
float
0
Ending time in seconds.
float
1E6
Minimum time step that is allowed before DORiE stops running.
with an error, in seconds.
float
0.1
Value of the first time step in seconds.
float
10
Largest allowed time step in seconds. Use this to control the
density of your output.
float
1E5
Minimum number of Newton iterations of the solver per
time step. At maxTimestep, the Newton solver is not allowed to calculate more
than this number of iterations.
int
1
Maximum number of Newton iterations of the solver per
time step. At minTimestep, the Newton solver is not allowed to calculate more
than this number of iterations.
int
12
Factor the current time step is multiplied with when increasing
the time step.
float > 1
1.5
Factor the current time step is multiplied with when decreasing
the time step.
float < 1
0.5
YAML file containing the parameter definitions.
path
transport_param.yml
Numerical scheme to perform time steps in the simulation.
``alex2`` and ``implicit_euler`` are implicit methods.
``explicit_euler`` is a explicit method.
explicit_euler, implicit_euler, alex2
alex2
Courant number for explicit methods. It is a scale for the
maximum stable time step according to the CFL condition. The CFL
condition penalizes high velocities, low dispersion coefficients, and
small grid elements. Hence, Courant numbers near to 1 tend to be more
instable while numbers near to 0 tend to considerably limit the
maximum time step.
0 < float < 1
0.8
Order of the finite element method used.
0
0
Apply the flux reconstruction method to the solved solute
concentration and obtain conservative fluxes.
true
true, false
Check that flux reconstruction engine is creating conforming
normal fluxes up to ``jumpTol``. ProTip: Setting warnings together
with a very low tolerance will let you track the changes on the
quality of the flux reconstruction.
none
none, warn, error
Whenever ``checkJumps`` is activated, it check that flux
reconstruction engine is creating conforming normal fluxes up to ``jumpTol``.
float > 0
1E-10
Required relative defect reduction.
Reduce this value to increase precision.
1E-6
float
Minimum absolute defect at which linear solver stops.
Reduce this value to increase precision.
1E-20
float