Input Instructions

To run RW3D, a single parameter file has to be provided.

Type of inputs

In the Parameter file, input parameters can be specified following these different formats:

  • logical: T for True; F for False

  • string

  • integer

  • real

  • time_function: A text file describing the temporal evolution of a non-array parameter.

  • array: The parameter is potentially spatially and/or temporally variable and can be read from a file. The following information have to be provided in a single line: file name multiplier ivar flag (see specifications in the Table below). In some specific cases, one or two additional parameters (options) must also be provided.

Required inputs for an Array-type parameter

Variable

Type

Description

file name

string

name of the file. Put some text even if no file is used

multiplier

real

Fixed parameter values (for flag = 0), or multiplier of the variable

ivar

integer

variable index of the variable in the gslib array

flag

integer

way to read the values of the parameter:

  • 0: spatially and temporally constant parameter, defined as the multiplier

  • 1: read from the ascii file specified in file name

  • 2: read from a MODFLOW type file (only for fluxes)

  • 3: read from a DFS file

  • 4: read from a NetCDF file

File format for a parameter of type array

A parameter of type array can be read from a file (with name file name) using a flag integer other than 0. The file can be an text file, a DFS file, or a NetCDF file.

  • Text file

A text file (flag set to 1) must follow the following format:

Ascii file format

Line

Variable

Type

Description

1

header

string

header line (not used by the code)

2

nvar

integer

number of variables

repeat the following line nvar times:

3

nvar_name

string

name of the variable (not used by the code)

repeat the following line \(nx \times ny \times nz\) times:

4

values

real

variable values

A single file can contain information about multiple (nvar) variables. The values of each variable is defined in space separated columns. The file must contain \(nx \times ny \times nz\) rows, where \(ni\) is the number of cells in the i-th dimension. All values are corrected by multiplying the read values by multiplier.

The values of the variable with index ivar are read as follow:

do k=1,nz
    do j=1,ny
        do i=1,nx
            read(iunit,*) (aline(jcol),jcol=1,nvar)    ! read all columns, i.e., all variables values, corresponding to the location (i,j,k)
            values(i,j,k) = aline(ivar) * multiplier   ! values of the selected variable (corresponding to the column ivar), corrected by a user-defined constant (multiplier)
        end do
    end do
end do

To read a parameter from a text file, use the usual inputs for an array parameter: file name multiplier ivar flag:

  • file name (string) is the name of the DFS file;

  • multiplier (real) is a number multiplying all values;

  • ivar (integer) is the column index to be used (set to 1 for a unique column of values in the text file);

  • flag (integer) is set to 1.

  • DFS file

RW3D supports reading input data from DFS files (flag set to 3). The DFS (Data File System) is a binary data file format typically used in the MIKE Powered by DHI software.

For an extensive description of what DFS files are, follow the link https://docs.mikepoweredbydhi.com/core_libraries/dfs/dfs-file-system/

To read a parameter from a DFS file, use the usual inputs for an array parameter: file name multiplier ivar flag:

  • file name (string) is the name of the DFS file;

  • multiplier (real) is a number multiplying all values;

  • ivar (integer) is the item index to be used (set to 1 for a unique item in the DFS file);

  • flag (integer) is set to 3.

Note that for the moment, the geometry of the DFS files must match the grid specified in the parameter file (Geometry) (i.e., same domain and spatial discretization). The same applies to the time discretization, which must correspond to the discretization specified in the parameter file (Time). A more flexible approach will be developed soon.

  • NetCDF file

RW3D supports reading input data from NetCDF files (flag set to 4). NetCDF (Network Common Data Form) is a widely used, self-describing binary file format designed for storing array-oriented scientific data. For more information on the NetCDF format, see the official documentation: https://www.unidata.ucar.edu/software/netcdf/

The NetCDF file must follow a specific format. It must contain 4 dimensions (t, x, y, z) that fits the temporal and spatial discretizations of the model, even for time-invariant and 1D/2D parameters. Also, the NetCDF dataset must contain only one variable (i.e., the parameter to be specified). The name of the variable that the code read and use is recalled in the log file.

Note that the NetCDF format of the file will have to follow the specifications of your instalation of the NetCDF library.

To read a parameter from a NetCDF file, use the usual inputs for an array parameter: file name multiplier ivar flag:

  • file name (string) is the name of the NetCDF file;

  • multiplier (real) is a number multiplying all values;

  • ivar (integer) has to be specified but will not be used;

  • flag (integer) is set to 4.

File format for time function

This file is a plain text file used to define a time-dependent function. It provides a sequence of time-value pairs that describe how a quantity evolves over time. The file is read when flag == 1.

File Structure

The file must follow this structure:

  1. Heading line (ignored by the subroutine).

  2. Name line: a string that will be stored in func%name.

  3. Number of time points: an integer value nt.

  4. Time-function data: nt lines, each containing: - A real number representing the time value. - A real number representing the corresponding function value.

Ensure that the number of time-value pairs matches the integer specified in line 3.

Example

# Time function data for simulation
MyTimeFunction
4
0.0  1.0
1.0  2.0
2.0  1.5
3.0  0.5

Parameter file

The parameter file consists in a text file. The following blocks of information has to be sequentially provided.

Warning

Note that 3 header lines has to be written before each block.

General setup

Line

Variable

Type

Description

4

path_outputs

string

path_outputs: path to the output files

5

base_outputs

string

base_outputs: base name for all output files

Note

The line number in each table is reset for each block to simplify the description of the inputs. Each block is to be filled up sequentially, so the absolute line number will be different.

Species and Phases

Line

Variable

Type

Description

4

nspe_aq nspe_min

integer

nspe_aq: number of aqueous (i.e., mobile) species

nspe_min: number of aqueous (i.e., immobile) species

5

name_aq

string

name_aq: name(s) of aqueous (i.e., mobile) species

6

name_min

string

name_min: name(s) of aqueous (i.e., immobile) species

Time

Line

Variable

Type

Description

4

t_sim

real

t_sim: simulation time

5

transient_flag

logical

transient_flag: True if transient conditions

if transient_flag == F, go to Geometry; if transient_flag == T, fill up the following:

6

read_dt_from_file loop_dt

logical

read_dt_from_file: True if the time steps are read from a text file

if read_dt_from_file == T:

7

dt_file

string

dt_file: name of the text file listing the time steps

if read_dt_from_file == T, go to Geometry; if read_dt_from_file == F:

8

n_dt

integer

n_dt: number of time steps

to be repeated \(n_{dt}\) times:

9 …

dt

real

dt: time step

Example: A problem involving 2 aqueous chemical species (named A and B) and 0 mineral species. The simulation will run for 150.0 time units with transient parameters. The temporal discretization of the transient parameters is specified in the file time_discretization.dat and the transient paramters are set to be looped in time until the end of the simulation. The first first blocs of the input file would look like that:

-----------------------------------------------------------------
 General Setup
-----------------------------------------------------------------
C:\Path\To\Ouputs                   !... path_outputs
test_case                           !... basename_outputs
-----------------------------------------------------------------
 Species and Phases
-----------------------------------------------------------------
2   0                               !nspe_aq; nspe_min
A   B                               !name_aq
-                                   !name_min
-----------------------------------------------------------------
 Time
-----------------------------------------------------------------
150.0                               !t_sim
T                                   !transient_flag
T   T                               !read_dt_from_file; loop_dt
time_discretization.dat             !dt_file

Geometry

Line

Variable

Type

Description

4

nx ny nz

integer

nx: number of cell in the x direction (i.e., columns)

ny: number of cell in the y direction (i.e., rows)

nz: number of cell in the z direction (i.e., layers)

5

dx

array

dx: cell size in the x direction

6

dy

array

dy: cell size in the y direction

7

dz

array, 1 option

dz: cell size in the z direction

option: Constant layer thickness

  • logical: T if constant layer thickness, F if variable layer thickess

8

topography

array

topography: topography elevation

9

inactive_cell

array, 1 option

inactive_cell: binary characteriztion of active/inactive cells

values: 0: active; 1: inactive

option: Particle in inactive cells are killed

  • logical: T particles are killed, F particles bounce at the boundary

10

ib(1,1) ib(1,2) ib(2,1) ib(2,2) ib(3,1) ib(3,2)

integer

Defines the particle behaviour if a domain boundary is reached.

ib(1,1): left boundary, defined by x_min

ib(1,2): right boundary, defined by x_max

ib(2,1): front boundary, defined by y_min

ib(2,2): back boundary, defined by y_max

ib(2,1): bottom boundary, defined by z_min

ib(2,2): top boundary, defined by z_max

values:

  • 0: The particle is killed

  • 1: The particle bounces at the boundary

  • 2: The particle is sent to the opposite side of the domain

8

write_vtu

logical

T Write the grid, (in)active cells and topography in a vtu file, F otherwise

Example: The domain is discretized in 1200 cells in the x-direction, 1400 cells in the y-direction and 11 cells in the z-direction. The cell size in x and y is fixed to 100 space units. The cell size in the z-direction is variable in space and specified in the first column of the text file dz.dat. The top elevation of the domain (topography) is also variable in space and specified in the text file topography.dat. The location of inactive cells is provided in the text file InactCell.dat and particles reaching an inactive cell will be killed. No multipliers are to be used (all set to 1.0). Finally, particles reaching the boundary of the domain will be killed, expect at the top of the domain, where particles will bounce. We would also like to produce a vtu file to visualize the grid, the active/innactive cells and the topography elevation in Paraview.

---------------------------------------------------------------
 Geometry
---------------------------------------------------------------
1200    1400    11                               !nx; ny; nz
not_used             100.0    1    0             !dx
not_used             100.0    1    0             !dy
dz.dat               1.0      1    1    F        !dz
topography.dat       1.0      1    1             !topography
InactCell.dat        1.0      1    1    T        !inactive_cell
0   0   0   0   0   1                            !ib(1,1); ib(1,2); ib(2,1); ib(2,2); ib(3,1); ib(3,2)
T                                                !write_vtu

Time step

Line

Variable

Type

Description

4

dt_method

string

Defines the way time steps are computed

values: description provided in section Time discretization

  • constant_dt

  • constant_move

  • optimum_dt

5

dt mult_adv mult_disp mult_kf mult_kd mult_mt

real

Time step restrictors, as defined in section Time discretization

6

dt_relax

real

Time step relaxation factor, as defined in section Time discretization

Example: The time step is determined from the advective characteristic times only. The time step restrictors have to be provided, but only mult_adv will be used. It is fixed to 0.5. The time step relaxation factor is set to 0.99, meaning that the 1% more restrictive characteristic times (1% fastest particles) will be disregarded in the time step determination.

-----------------------------------------------------------------
 Time discretization
-----------------------------------------------------------------
constant_move                                           !... dt_method
1.0  0.5  0.2  0.1  0.1  0.1                            !... dt, mult_adv, mult_disp, mult_kf, mult_kd, mult_mt
0.99                                                    !... time step relaxation

Advection

Line

Variable

Type

Description

4

advection_action

logical

True if the package is activated

5

advection_method

logical

Method for advective motion of particles, as defined in Advective Motion

values:

  • exponential

  • eulerian

6

q_x

array, 2 option

flow/flux in the x direction

option 1: transient conditions

  • logical: T transient field, F steady-state field

option 2: flow to flux

  • logical: T if flows are provided and need to be converted into fluxes, F if fluxes are provided

7

q_y

array, 2 option

flow/flux in the y direction

option 1: transient conditions

  • logical: T transient field, F steady-state field

option 2: flow to flux

  • logical: T if flows are provided and need to be converted into fluxes, F if fluxes are provided

8

q_z

array, 2 option

flow/flux in the z direction

option 1: transient conditions

  • logical: T transient field, F steady-state field

option 2: flow to flux

  • logical: T if flows are provided and need to be converted into fluxes, F if fluxes are provided

9

porosity

array, 1 option

porosity (or water content)

option 1: transient conditions

  • logical: T if flows are provided and need to be converted into fluxes, F if fluxes are provided

Example: Advective displacements are simulated. The Eulerian scheme is used to interpolate velocities. Darcy flows in x, and y directions are provided in a respective netcdf file. Flows will then have to be converted into fluxes within RW3D. The fluxes in z are directly provided, also in a netcdf file. All flows and fluxes are transient. The fluxes in z are to be multiplied by a factor of 2.0. The porosity field does not change in time and its spatial distribution is defined in a text file.

-----------------------------------------------------------------
 Advection
-----------------------------------------------------------------
T                                                                              !... advection_action
Eulerian                                                                       !... advection_method
qx_DK1.nc                            1.0   1   4   T   T                       !... qx array
qy_DK1.nc                            1.0   1   4   T   T                       !... qy array
qz_DK1.nc                            2.0   1   4   T   T                       !... qz array
porosity_DK1.dat                     1.0   1   1   F                           !... porosity array

Heads

Line

Variable

Type

Description

4

heads_action

logical

True if the package is activated

5

heads

array, 1 option

cell-by-cell head elevation

option: transient conditions

  • logical: T transient field, F steady-state field

6

heads_threshold

real

maximum head elevation for the cell to be considered dry

Example: Hydrualic heads are accounted for to track particles reaching the water table. Heads are provided in a netcdf file. A cell will be considered dry if heads are below 0.05 (space unit).

--------------------------------------------------------------------------------------------
 Heads
--------------------------------------------------------------------------------------------
T                                                                              !... heads_action
heads_DK1.nc                        1.0   1    4   F                           !... heads
0.05                                                                           !... heads_threshold

Sinks

Line

Variable

Type

Description

4

sinks_action

logical

True if the package is activated

5

n_sinks

integer

number of sink

to be repeated \(n_{sinks}\) times:

6…

sink_name Q_sink

string array, 2 option

sink_name: name of the sink

Q_sink: flow going into the sink (\(L^3/T\))

option 1: transient conditions

  • logical: T transient field, F steady-state field

option 2: print_BTC

  • logical: T BTC is printed, F BTC not printed

Example: 4 types of cell sinks are considered: river, drain, uz, well. All sinks are read from a respective a netcdf file. Breakthrough curves for all sinks will be saved, expect for the well sink. All sink fluxes are temporally variable.

--------------------------------------------------------------------------------------------
 Sinks
--------------------------------------------------------------------------------------------
T                                                                              !... sink_action
4                                                                              !... number of sink
river     Qriver_DK1.nc          1.0   1   4   T   T                           !... name, qsink array
drain     Qdrain_DK1.nc          1.0   1   4   T   T                           !... name, qsink array
uz        Q_uz_DK1.nc            1.0   1   4   T   T                           !... name, qsink array
well      Qwell_DK1.nc           1.0   1   4   T   F                           !... name, qsink array

Dispersion / Diffusion

Line

Variable

Type

Description

4

dispersion_action

logical

True if the package is activated

5

dispersivity_L

array, 1 option

dispersivity in the longitudinal direction

option: transient conditions

  • logical: T transient field, F steady-state field

6

dispersivity_TH

array, 1 option

dispersivity in the transverse horizontal direction

option: transient conditions

  • logical: T transient field, F steady-state field

7

dispersivity_TV

array, 1 option

dispersivity in the transverse vertical direction

option: transient conditions

  • logical: T transient field, F steady-state field

8

diffusion_L

array, 1 option

effective molecular diffusion in the longitudinal direction

option: transient conditions

  • logical: T transient field, F steady-state field

9

diffusion_TH

array, 1 option

effective molecular diffusion in the transverse horizontal direction

option: transient conditions

  • logical: T transient field, F steady-state field

10

diffusion_TV

array, 1 option

effective molecular diffusion in the transverse vertical direction

option: transient conditions

  • logical: T transient field, F steady-state field

11

dispersivity_factor (repeat nspe_aq times)

real

Species dependent multiplier for the dispersivity coefficients

for each aqueous species, the effective dispersivity coefficients is multiplied by the given factor

12

diffusion_factor (repeat nspe_aq times)

real

Species dependent multiplier for the diffusion coefficients

for each aqueous species, the effective diffusion coefficient is multiplied by the given factor

Example: Dispersion and diffusion processes are simulated. All parameters are considered spatially homogeneous. Longitudinal, transverse horizonal, and transverse vertical dispersivities are set to 5.0, 5.0 and 0.1, respectively. Diffusion coefficients in all directions are set to 0.01. Two single aqueous species were considered. Diffusion coefficients for the second specie are two times larger than the set values (diffusion_factor set to 2.0). Set dispervities and diffusion coefficients are used otherwise (dispersivity_factor and diffusion_factor set to 1.0).

--------------------------------------------------------------------------------------------
 Dispersion / diffusion
--------------------------------------------------------------------------------------------
T                                                                              !... dispersion_action
not_used                             5.0   1   0                               !... alpha_L array
not_used                             5.0   1   0                               !... alpha_TH array
not_used                             0.1   1   0                               !... alpha_TV array
not_used                             0.01   1   0   F                          !... Dm_L array
not_used                             0.01   1   0   F                          !... Dm_TH array
not_used                             0.01   1   0   F                          !... Dm_TV array
1.0   1.0                                                                      !... mult_alpha
1.0   2.0                                                                      !... mult_diff

Mass transfer

Line

Variable

Type

Description

4

mass_transfer_action

logical

True if the package is activated

5

type_mass_transfer

string

Defines the type of mass transfer process

values: description provided in section Multirate Mass Transfer

  • multirate

  • spherical_diffusion

  • layered_diffusion

  • cylindral_diffusion

  • power_law

  • lognormal_law

  • composite_law

if type_mass_transfer = multirate or spherical_diffusion or layered_diffusion or cylindral_diffusion:

6

num_immobile_zones

integer

number of immobile zones

to be repeated num_immobile_zones times:

7

porosity_immobile

array

porosity in the ith immobile zone

8

mass_transfer_coef

array

mass transfer coefficient in the ith immobile zone

if type_mass_transfer = power_law:

6

num_immobile_zones

integer

number of immobile zones

to be repeated num_immobile_zones times:

7

btot

array

total capacity

8

Amin

array

minimum mass transfer coefficient

9

Amax

array

maximum mass transfer coefficient

10

power

array

power coefficient

if type_mass_transfer = lognormal_law:

6

num_immobile_zones

integer

number of immobile zones

to be repeated num_immobile_zones times:

7

btot

array

total capacity

8

mean

array

mean of the lognormal mass transfer coefficients

9

stdv

array

standart deviation in mass transfer coefficients

if type_mass_transfer = composite_media:

6

nmrate nsph ncyl nlay

integer

nmrate: number of immobile zones for the multirate mass transfer model

nsph: number of immobile zones for the spherical diffusion model

ncyl: number of immobile zones for the cylindral diffusion model

nlay: number of immobile zones for the layered diffusion model

for each mass transfer model, fill up sequentially the corresponding parameters as described above

Reactions

Retardation

Line

Variable

Type

Description

4

retardation_action

logical

True if the package is activated

to be repeated nspe_aq times:

5…

R

array

retardation factor for a given aqueous species

if mass_transfer_action``=``T:

if type_mass_transfer = multirate:

… to be repeated nspe_aq times:

…… to be repeated num_immobile_zones times:

6 …

Rim

array

retardation factor for a given aqueous species and given imoobile zone

if type_mass_transfer = spherical_diffusion or layered_diffusion or cylindral_diffusion or power_law or lognormal_law:

… to be repeated nspe_aq times:

6 …

Rim

array

retardation factor for a given aqueous species (for all imoobile zones)

Note

Retardation is not available if type_mass_transfer = composite_media.

First-order decay

Line

Variable

Type

Description

4

first_order_action

logical

True if the package is activated

5

nspe_decay

integer

number of species involved in the decay network

6

name_spe_decay

string

name(s) of the species involved in the decay network

7

type_decay_network

string

type of the decay network

values:

  • serial: sequential degradation (e.g., A \(\to\) B \(\to\) C)

  • serial_moments: sequential degradation solving higher moments in the

derivation of transition probabilities (slower, but more accurate for large dt) - generic: generic reaction network

  • if type_decay_network = serial:

… to be repeated nspe_decay times:

8 …

k

array

first-order decay rate

…… do not fill for the first species for the serial network:

9 …

y

array

yield coefficient

if mass_transfer_action``=``T:

… if type_mass_transfer = multirate:

…… to be repeated nspe_decay times:

……… to be repeated num_immobile_zones times:

10…

kim

array

first-order decay rate for a given aqueous species and given imoobile zone

… if type_mass_transfer = spherical_diffusion or layered_diffusion or cylindral_diffusion or power_law or lognormal_law:

…… to be repeated nspe_decay times:

10…

kim

array

first-order decay rate a given aqueous species (for all imoobile zones)

  • if type_decay_network = serial_moments:

… to be repeated nspe_decay times:

8 …

k

array

first-order decay rate

…… do not fill for the first species for the serial network:

9 …

y

array

yield coefficient

  • if type_decay_network = generic:

… to be repeated nspe_decay times:

8 …

k

array

first-order decay rate

… to be repeated nspe_decay x nspe_decay times:

9 …

y

array

yield coefficient

if mass_transfer_action``=``T:

… if type_mass_transfer = multirate:

…… to be repeated nspe_decay times:

……… to be repeated num_immobile_zones times:

10…

kim

array

first-order decay rate for a given aqueous species and given imoobile zone

… if type_mass_transfer = spherical_diffusion or layered_diffusion or cylindral_diffusion or power_law or lognormal_law:

…… to be repeated nspe_decay times:

10…

kim

array

first-order decay rate a given aqueous species (for all imoobile zones)

Note

serial_moments option is not available if mass_transfer_action = T.

Note

Linear reaction solver is not available if type_mass_transfer = composite_media.

Bimolecular reactions

Line

Variable

Type

Description

4

kinetic_action

logical

True if the package is activated

5

n_reactions

integer

number of reactions in the network

to be repeated n_reactions times:

6

reaction_string

string

string describing a reaction

instructions:

  • following the form: [name_sp1] + [name_sp1] –> [name_sp3]

  • each specie names in brakets ([])

  • reactants and products separeted by an arrow (-->)

  • The name of the species must follow the names specified in General setup

available reaction so far:

  • one reactant and zero product: A –> 0

  • one reactant and one product: A –> C

  • one reactant and two product: A –> C + D

  • two reactants and zero product: A + B –> 0

  • two reactants and one product: A + B –> C

  • two reactants and two product: A + B –> C + D

to be repeated n_reactions times:

7

kf

array

reaction rate

Observation

Note

Information about all observation surfaces (extraction wells, planes, registration lenses) have to be provided in a single block, without header lines between them,

Extraction well

Note

Extraction wells acting as a sink (strong or weak) can be specified in Sinks if the sink is considered uniformly in the cell where a well is located. In Observation, extraction wells are considered as a sink at the well location, with converging velocity leading to the actual well location. See Sink for more details about the implementation.

Line

Variable

Type

Description

4

n_well

integer

number of wells

to be repeated n_well times:

6

wellID xw yw rw zbot ztop partOUT SaveBTC

string real (x5) logical (x2)

wellID: name of the well

xw: x-coordinate of the center of the well

yw: y-coordinate of the center of the well

rw: radius of the well

zbot: z-coordinate of the bottom of the well (or well screen)

ztop: z-coordinate of the top of the well (or well screen)

partOUT: True (T) if particles reaching the observation location are killed

SaveBTC: True (T) if breakthrough curves are saved and printed

7

Qwell_method

string

Method with which extraction fluxes (Q_well) are read

values:

  • CONSTANTQ: total Q_well is uniformly distributed along the well screen

  • WELL_PACKAGE: Q_well is cell-by-cell defined in a external file following Modflow’s well package

  • MNW2_PACKAGE: Q_well is cell-by-cell defined in a external file following Modflow’s mnw2 package

  • if Qwell_method = CONSTANTQ:

… to be repeated n_well times:

8…

Qw

real

total flux extracted by the given well

  • if Qwell_method = WELL_PACKAGE or MNW2_PACKAGE:

8

filename

string

name of the file following the Modflow’s package

Control plane

Line

Variable

Type

Description

5

n_plane

integer

number of control planes

There are 2 options to define the control planes:

  • option 1, to be repeated n_planes times:

6

dist type partOUT SaveBTC

string

dist: distance of the control plane with respect to the x,y or z coordinate axis

type: type of control plane

values:

  • XX: plane parallel to the x coordinate

  • YY: plane parallel to the y coordinate

  • ZZ: plane parallel to the z coordinate

partOUT: True (T) if particles reaching the observation location are killed

SaveBTC: True (T) if breakthrough curves are saved and printed

  • option 2, to be repeated n_planes times:

6

A B C D partOUT SaveBTC

string (x4) logical

A, B, C, D: parameters of the equation defining a plane as: \(A x + B y + C z + D = 0\)

partOUT: True (T) if particles reaching the observation location are killed

SaveBTC: True (T) if breakthrough curves are saved and printed

Registration lense

Injection

Well recirculation

Note

In connection_string, the well names must correspond to the wellID specified in _Extraction well.

Outputs

Format of the file defining the times for snapshots.

Line

Variable

Type

Description

1

header

string

header line (not used by the code)

2

n_snap

integer

number of snapshots

repeat the following line n_snap times:

3

t_snap

string

time of the snapshot

Example:

--------------------------------------------------------------------------------------------
 Outputs
--------------------------------------------------------------------------------------------
0                                                                     !... ixmom
1   1                                                                 !... iwcshot, output_format
150.0   50   1                                                        !... tlen,ntstep,tmult
0                                                                     !... itmom
1   100   plugin   -10.   0.0   250.0   0                             !... iwbtc, ngrid, Kernel, bw, tmin, tmax, output_format
1   1   0                                                             !... iwcbtc, inc, , output_format
1   0   0                                                             !... iwhistory, print_out, output_format
0   1   35496   0                                                     !... iwpath, pathfreq, pathpart, output_format