diff --git a/doc/modules/changes/20241022_bangerth b/doc/modules/changes/20241022_bangerth
new file mode 100644
index 00000000000..012d6d9e753
--- /dev/null
+++ b/doc/modules/changes/20241022_bangerth
@@ -0,0 +1,4 @@
+New: The new input parameter "Output directory LFS stripe count" allows for configuring
+the ASPECT output directory for better performance on Lustre file systems.
+
+(Wolfgang Bangerth, 2024/10/22)
diff --git a/doc/parameter_view/parameters.xml b/doc/parameter_view/parameters.xml
index 0879255577b..7e872e23655 100644
--- a/doc/parameter_view/parameters.xml
+++ b/doc/parameter_view/parameters.xml
@@ -83,7 +83,7 @@ The number of space dimensions you want to run this program in. ASPECT can run i
The end time of the simulation. The default value is a number so that when converted from years to seconds it is approximately equal to the largest number representable in floating point arithmetic. For all practical purposes, this equals infinity. Units: Years if the 'Use years in output instead of seconds' parameter is set; seconds otherwise.
-433
+434
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -240,7 +240,7 @@ output
output
-The name of the directory into which all output files should be placed. This may be an absolute or a relative path.
+The name of the directory into which all output files should be placed. This may be an absolute or a relative path. ASPECT will write output such as statistics files or visualization files into this directory or into directories further nested within.
19
@@ -249,6 +249,27 @@ The name of the directory into which all output files should be placed. This may
[DirectoryName]
+
+
+0
+
+
+0
+
+
+Many large clusters use the Lustre file system (LFS) that allows to 'stripe' files, i.e., to use multiple file servers to store a single file. This is useful when writing very large files from multiple MPI processes, such as when creating graphical output or creating checkpoints. In those cases, if all MPI processes try to route their data to a single file server, that file server and the disks it manages may be saturated by data and everything slows down. File striping instead ensures that the data is sent to several file servers, improving performance. A description of how Lustre manages file striping can be found at https://doc.lustre.org/lustre_manual.xhtml#managingstripingfreespace . How file striping can be configured is discussed at https://wiki.lustre.org/Configuring_Lustre_File_Striping .
+
+When this parameter is set to anything other than zero, ASPECT will call the Lustre support tool, `lst`, as follows: `lst setstripe -c N OUTPUT_DIR`, where `N` is the value of the input parameter discussed here, and `OUTPUT_DIR` is the directory into which ASPECT writes its output. The file striping so set on the output directory are also inherited by the sub-directories ASPECT creates within it.
+
+In order to use this parameter, your cluster must obviously be using the Lustre file system. What the correct value for the stripe count is is something you will have to find out from your cluster's local documentation, or your cluster administrator. It depends on the physical details and configuration of the file servers attached to a cluster.
+
+
+20
+
+
+[Integer range 0...2147483647 (inclusive)]
+
+
surface
@@ -366,7 +387,7 @@ false
If set to true, the advection and reactions of compositional fields and temperature are solved separately, and can use different time steps. Note that this will only work if the material/heating model fills the reaction\_rates/heating\_reaction\_rates structures. Operator splitting can be used with any existing solver schemes that solve the temperature/composition equations.
-20
+21
[Bool]
@@ -400,7 +421,7 @@ For the purposes of this parameter, a year consists of 60*60*24*365.2425 seconds
Name of the world builder file. If empty, the world builder is not initialized.
-21
+22
[FileName (Type: input)]
@@ -426,7 +447,7 @@ Select one of the following models:
`function': A model in which the adiabatic profile is specified by a user defined function. The supplied function has to contain temperature, pressure, and density as a function of depth in this order.
-1419
+1420
[Selection ascii data|compute entropy profile|compute profile|function ]
@@ -444,7 +465,7 @@ $ASPECT_SOURCE_DIR/tests/adiabatic-conditions/ascii-data/test/
The name of a directory that contains the model data. This path may either be absolute (if starting with a `/') or relative to the current directory. The path may also include the special text `$ASPECT_SOURCE_DIR' which will be interpreted as the path in which the ASPECT source files were located when ASPECT was compiled. This interpretation allows, for example, to reference files located in the `data/' subdirectory of ASPECT.
-1420
+1421
[DirectoryName]
@@ -457,7 +478,7 @@ The name of a directory that contains the model data. This path may either be ab
The file name of the model data.
-1421
+1422
[Anything]
@@ -474,7 +495,7 @@ The file name of the model data.
Scalar factor, which is applied to the model data. You might want to use this to scale the input to a reference model. Another way to use this factor is to convert units of the input files. For instance, if you provide velocities in cm/yr set this factor to 0.01.
-1422
+1423
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -493,7 +514,7 @@ Scalar factor, which is applied to the model data. You might want to use this to
The number of points we use to compute the adiabatic profile. The higher the number of points, the more accurate the downward integration from the adiabatic surface conditions will be.
-1423
+1424
[Integer range 5...2147483647 (inclusive)]
@@ -510,7 +531,7 @@ The number of points we use to compute the adiabatic profile. The higher the num
The surface entropy for the profile.
-1424
+1425
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -529,7 +550,7 @@ initial composition
Select how the reference profile for composition is computed. This profile is used to evaluate the material model, when computing the pressure and temperature profile.
-1428
+1429
[Selection initial composition|function ]
@@ -544,7 +565,7 @@ Sometimes it is convenient to use symbolic constants in the expression that desc
A typical example would be to set this runtime parameter to `pi=3.1415926536' and then use `pi' in the expression of the actual formula. (That said, for convenience this class actually defines both `pi' and `Pi' by default, but you get the idea.)
-1427
+1428
[Anything]
@@ -563,7 +584,7 @@ The formula that denotes the function you want to evaluate for particular values
If the function you are describing represents a vector-valued function with multiple components, then separate the expressions for individual components by a semicolon.
-1426
+1427
[Anything]
@@ -580,7 +601,7 @@ If the function you are describing represents a vector-valued function with mult
The number of points we use to compute the adiabatic profile. The higher the number of points, the more accurate the downward integration from the adiabatic surface temperature will be.
-1429
+1430
[Integer range 5...2147483647 (inclusive)]
@@ -597,7 +618,7 @@ false
Whether to use the 'Surface condition function' to determine surface conditions, or the 'Adiabatic surface temperature' and 'Surface pressure' parameters. If this is set to true the reference profile is updated every timestep. The function expression of the function should be independent of space, but can depend on time 't'. The function must return two components, the first one being reference surface pressure, the second one being reference surface temperature.
-1430
+1431
[Bool]
@@ -614,7 +635,7 @@ x,t
The names of the variables as they will be used in the function, separated by commas. By default, the names of variables at which the function will be evaluated are `x' (in 1d), `x,y' (in 2d) or `x,y,z' (in 3d) for spatial coordinates and `t' for time. You can then use these variable names in your function expression and they will be replaced by the values of these variables at which the function is currently evaluated. However, you can also choose a different set of names for the independent variables at which to evaluate your function expression. For example, if you work in spherical coordinates, you may wish to set this input parameter to `r,phi,theta,t' and then use these variable names in your function expression.
-1425
+1426
[Anything]
@@ -630,7 +651,7 @@ Sometimes it is convenient to use symbolic constants in the expression that desc
A typical example would be to set this runtime parameter to `pi=3.1415926536' and then use `pi' in the expression of the actual formula. (That said, for convenience this class actually defines both `pi' and `Pi' by default, but you get the idea.)
-1433
+1434
[Anything]
@@ -649,7 +670,7 @@ The formula that denotes the function you want to evaluate for particular values
If the function you are describing represents a vector-valued function with multiple components, then separate the expressions for individual components by a semicolon.
-1432
+1433
[Anything]
@@ -666,7 +687,7 @@ x,t
The names of the variables as they will be used in the function, separated by commas. By default, the names of variables at which the function will be evaluated are `x' (in 1d), `x,y' (in 2d) or `x,y,z' (in 3d) for spatial coordinates and `t' for time. You can then use these variable names in your function expression and they will be replaced by the values of these variables at which the function is currently evaluated. However, you can also choose a different set of names for the independent variables at which to evaluate your function expression. For example, if you work in spherical coordinates, you may wish to set this input parameter to `r,phi,theta,t' and then use these variable names in your function expression.
-1431
+1432
[Anything]
@@ -684,7 +705,7 @@ Sometimes it is convenient to use symbolic constants in the expression that desc
A typical example would be to set this runtime parameter to `pi=3.1415926536' and then use `pi' in the expression of the actual formula. (That said, for convenience this class actually defines both `pi' and `Pi' by default, but you get the idea.)
-1436
+1437
[Anything]
@@ -701,7 +722,7 @@ A typical example would be to set this runtime parameter to `pi=3.1415926536&apo
Expression for the adiabatic temperature, pressure, and density separated by semicolons as a function of `depth'.
-1437
+1438
[Anything]
@@ -716,7 +737,7 @@ depth
-1438
+1439
[Anything]
@@ -740,7 +761,7 @@ Mathematically speaking, the compositional fields satisfy an advection equation
A warning for models with melt transport: In models with fluid flow, some compositional fields (in particular the porosity) might be transported with the fluid velocity, and would need to set the constraints based on the fluid velocity. However, this is currently not possible, because we reuse the same matrix for all compositional fields, and therefore can not use different constraints for different fields. Consequently, we set this parameter to true by default in models where melt transport is enabled. Be aware that if you change this default setting, you will not use the melt velocity, but the solid velocity to determine on which parts of the boundaries there is outflow.
-1392
+1393
[Selection true|false|false for models without melt ]
@@ -757,7 +778,7 @@ The names of the boundaries listed here can either be numbers (in which case the
This parameter only describes which boundaries have a fixed composition, but not what composition should hold on these boundaries. The latter piece of information needs to be implemented in a plugin in the BoundaryComposition group, unless an existing implementation in this group already provides what you want.
-1391
+1392
[List of <[Anything]> of length 0...4294967295 (inclusive)]
@@ -790,7 +811,7 @@ Because this class simply takes what the initial composition had described, this
`spherical constant': A model in which the composition is chosen constant on the inner and outer boundaries of a sphere, spherical shell, chunk or ellipsoidal chunk. Parameters are read from subsection 'Spherical constant'.
-1388
+1389
[MultipleSelection ascii data|box|box with lithosphere boundary indicators|function|initial composition|spherical constant ]
@@ -807,7 +828,7 @@ add
A comma-separated list of operators that will be used to append the listed composition models onto the previous models. If only one operator is given, the same operator is applied to all models.
-1389
+1390
[MultipleSelection add|subtract|minimum|maximum|replace if valid ]
@@ -844,7 +865,7 @@ Because this class simply takes what the initial composition had described, this
\textbf{Warning}: This parameter provides an old and deprecated way of specifying boundary composition models and shouldn't be used. Please use 'List of model names' instead.
-1390
+1391
[Selection ascii data|box|box with lithosphere boundary indicators|function|initial composition|spherical constant|unspecified ]
@@ -862,7 +883,7 @@ $ASPECT_SOURCE_DIR/data/boundary-composition/ascii-data/test/
The name of a directory that contains the model data. This path may either be absolute (if starting with a `/') or relative to the current directory. The path may also include the special text `$ASPECT_SOURCE_DIR' which will be interpreted as the path in which the ASPECT source files were located when ASPECT was compiled. This interpretation allows, for example, to reference files located in the `data/' subdirectory of ASPECT.
-1393
+1394
[DirectoryName]
@@ -879,7 +900,7 @@ box_2d_%s.%d.txt
The file name of the model data. Provide file in format: (File name).\%s\%d, where \%s is a string specifying the boundary of the model according to the names of the boundary indicators (of the chosen geometry model), and \%d is any sprintf integer qualifier specifying the format of the current file number.
-1396
+1397
[Anything]
@@ -896,7 +917,7 @@ The file name of the model data. Provide file in format: (File name).\%s\%d, whe
Time step between following data files. Depending on the setting of the global `Use years in output instead of seconds' flag in the input file, this number is either interpreted as seconds or as years. The default is one million, i.e., either one million seconds or one million years.
-1397
+1398
[Double 0...MAX_DOUBLE (inclusive)]
@@ -913,7 +934,7 @@ false
In some cases the boundary files are not numbered in increasing but in decreasing order (e.g. `Ma BP'). If this flag is set to `True' the plugin will first load the file with the number `First data file number' and decrease the file number during the model run.
-1400
+1401
[Bool]
@@ -930,7 +951,7 @@ In some cases the boundary files are not numbered in increasing but in decreasin
The `First data file model time' parameter has been deactivated and will be removed in a future release. Do not use this parameter and instead provide data files starting from the model start time.
-1398
+1399
[Double 0...MAX_DOUBLE (inclusive)]
@@ -947,7 +968,7 @@ The `First data file model time' parameter has been deactivated and will be
Number of the first velocity file to be loaded when the model time is larger than `First velocity file model time'.
-1399
+1400
[Integer range -2147483648...2147483647 (inclusive)]
@@ -964,7 +985,7 @@ Number of the first velocity file to be loaded when the model time is larger tha
Scalar factor, which is applied to the model data. You might want to use this to scale the input to a reference model. Another way to use this factor is to convert units of the input files. For instance, if you provide velocities in cm/yr set this factor to 0.01.
-1395
+1396
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -979,7 +1000,7 @@ Scalar factor, which is applied to the model data. You might want to use this to
A comma separated list of composition boundary values at the bottom boundary (at minimal $y$-value in 2d, or minimal $z$-value in 3d). This list must have as many entries as there are compositional fields. Units: none.
-1403
+1404
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -992,7 +1013,7 @@ A comma separated list of composition boundary values at the bottom boundary (at
A comma separated list of composition boundary values at the left boundary (at minimal $x$-value). This list must have as many entries as there are compositional fields. Units: none.
-1401
+1402
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -1005,7 +1026,7 @@ A comma separated list of composition boundary values at the left boundary (at m
A comma separated list of composition boundary values at the right boundary (at maximal $x$-value). This list must have as many entries as there are compositional fields. Units: none.
-1402
+1403
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -1018,7 +1039,7 @@ A comma separated list of composition boundary values at the right boundary (at
A comma separated list of composition boundary values at the top boundary (at maximal $y$-value in 2d, or maximal $z$-value in 3d). This list must have as many entries as there are compositional fields. Units: none.
-1404
+1405
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -1033,7 +1054,7 @@ A comma separated list of composition boundary values at the top boundary (at ma
A comma separated list of composition boundary values at the bottom boundary (at minimal $y$-value in 2d, or minimal $z$-value in 3d). This list must have as many entries as there are compositional fields. Units: none.
-1417
+1418
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -1046,7 +1067,7 @@ A comma separated list of composition boundary values at the bottom boundary (at
A comma separated list of composition boundary values at the left boundary (at minimal $x$-value). This list must have as many entries as there are compositional fields. Units: none.
-1413
+1414
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -1059,7 +1080,7 @@ A comma separated list of composition boundary values at the left boundary (at m
A comma separated list of composition boundary values at the left boundary (at minimal $x$-value). This list must have as many entries as there are compositional fields. Units: none.
-1415
+1416
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -1072,7 +1093,7 @@ A comma separated list of composition boundary values at the left boundary (at m
A comma separated list of composition boundary values at the right boundary (at maximal $x$-value). This list must have as many entries as there are compositional fields. Units: none.
-1414
+1415
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -1085,7 +1106,7 @@ A comma separated list of composition boundary values at the right boundary (at
A comma separated list of composition boundary values at the right boundary (at maximal $x$-value). This list must have as many entries as there are compositional fields. Units: none.
-1416
+1417
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -1098,7 +1119,7 @@ A comma separated list of composition boundary values at the right boundary (at
A comma separated list of composition boundary values at the top boundary (at maximal $y$-value in 2d, or maximal $z$-value in 3d). This list must have as many entries as there are compositional fields. Units: none.
-1418
+1419
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -1117,7 +1138,7 @@ cartesian
A selection that determines the assumed coordinate system for the function variables. Allowed values are 'cartesian', 'spherical', and 'depth'. 'spherical' coordinates are interpreted as r,phi or r,phi,theta in 2d/3d respectively with theta being the polar angle. 'depth' will create a function, in which only the first parameter is non-zero, which is interpreted to be the depth of the point.
-1405
+1406
[Selection cartesian|spherical|depth ]
@@ -1132,7 +1153,7 @@ Sometimes it is convenient to use symbolic constants in the expression that desc
A typical example would be to set this runtime parameter to `pi=3.1415926536' and then use `pi' in the expression of the actual formula. (That said, for convenience this class actually defines both `pi' and `Pi' by default, but you get the idea.)
-1408
+1409
[Anything]
@@ -1151,7 +1172,7 @@ The formula that denotes the function you want to evaluate for particular values
If the function you are describing represents a vector-valued function with multiple components, then separate the expressions for individual components by a semicolon.
-1407
+1408
[Anything]
@@ -1168,7 +1189,7 @@ x,y,t
The names of the variables as they will be used in the function, separated by commas. By default, the names of variables at which the function will be evaluated are `x' (in 1d), `x,y' (in 2d) or `x,y,z' (in 3d) for spatial coordinates and `t' for time. You can then use these variable names in your function expression and they will be replaced by the values of these variables at which the function is currently evaluated. However, you can also choose a different set of names for the independent variables at which to evaluate your function expression. For example, if you work in spherical coordinates, you may wish to set this input parameter to `r,phi,theta,t' and then use these variable names in your function expression.
-1406
+1407
[Anything]
@@ -1187,7 +1208,7 @@ The names of the variables as they will be used in the function, separated by co
Maximal composition. Units: none.
-1410
+1411
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -1204,7 +1225,7 @@ Maximal composition. Units: none.
Minimal composition. Units: none.
-1409
+1410
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -1223,7 +1244,7 @@ Minimal composition. Units: none.
A comma separated list of composition boundary values at the bottom boundary (at minimal radius). This list must have one entry or as many entries as there are compositional fields. Units: none.
-1412
+1413
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -1240,7 +1261,7 @@ A comma separated list of composition boundary values at the bottom boundary (at
A comma separated list of composition boundary values at the top boundary (at maximal radius). This list must have one entry or as many entries as there are compositional fields. Units: none.
-1411
+1412
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -1262,7 +1283,7 @@ Select one of the following plugins:
`density': A plugin that prescribes the fluid pressure gradient at the boundary based on fluid/solid density from the material model.
-109
+110
[Selection density ]
@@ -1286,7 +1307,7 @@ The density formulation used to compute the fluid pressure gradient at the model
'average density' prescribes the gradient of the fluid pressure as the averaged fluid and solid density times gravity (which is a better approximation for the lithostatic pressure than just the solid density) and leads to approximately the same pressure in the melt as in the solid, so that fluid is only flowing in or out due to differences in dynamic pressure.
-110
+111
[Selection solid density|fluid density|average density ]
@@ -1306,7 +1327,7 @@ The names of the boundaries listed here can either be numbers (in which case the
This parameter only describes which boundaries have a fixed heat flux, but not what heat flux should hold on these boundaries. The latter piece of information needs to be implemented in a plugin in the BoundaryHeatFlux group, unless an existing implementation in this group already provides what you want.
-56
+57
[List of <[Anything]> of length 0...4294967295 (inclusive)]
@@ -1329,7 +1350,7 @@ The formula you describe in the mentioned section is a scalar value for the heat
The symbol $t$ indicating time that may appear in the formulas for the prescribed heat flux is interpreted as having units seconds unless the global parameter ``Use years in output instead of seconds'' has been set.
-1482
+1483
[Selection function ]
@@ -1347,7 +1368,7 @@ cartesian
A selection that determines the assumed coordinate system for the function variables. Allowed values are `cartesian', `spherical', and `depth'. `spherical' coordinates are interpreted as r,phi or r,phi,theta in 2d/3d respectively with theta being the polar angle. `depth' will create a function, in which only the first parameter is non-zero, which is interpreted to be the depth of the point.
-1483
+1484
[Selection cartesian|spherical|depth ]
@@ -1362,7 +1383,7 @@ Sometimes it is convenient to use symbolic constants in the expression that desc
A typical example would be to set this runtime parameter to `pi=3.1415926536' and then use `pi' in the expression of the actual formula. (That said, for convenience this class actually defines both `pi' and `Pi' by default, but you get the idea.)
-1486
+1487
[Anything]
@@ -1381,7 +1402,7 @@ The formula that denotes the function you want to evaluate for particular values
If the function you are describing represents a vector-valued function with multiple components, then separate the expressions for individual components by a semicolon.
-1485
+1486
[Anything]
@@ -1398,7 +1419,7 @@ x,y,t
The names of the variables as they will be used in the function, separated by commas. By default, the names of variables at which the function will be evaluated are `x' (in 1d), `x,y' (in 2d) or `x,y,z' (in 3d) for spatial coordinates and `t' for time. You can then use these variable names in your function expression and they will be replaced by the values of these variables at which the function is currently evaluated. However, you can also choose a different set of names for the independent variables at which to evaluate your function expression. For example, if you work in spherical coordinates, you may wish to set this input parameter to `r,phi,theta,t' and then use these variable names in your function expression.
-1484
+1485
[Anything]
@@ -1420,7 +1441,7 @@ When the temperature is fixed on a given boundary as determined by the list of &
Mathematically speaking, the temperature satisfies an advection-diffusion equation. For this type of equation, one can prescribe the temperature even on outflow boundaries as long as the diffusion coefficient is nonzero. This would correspond to the ``true'' setting of this parameter, which is correspondingly the default. In practice, however, this would only make physical sense if the diffusion coefficient is actually quite large to prevent the creation of a boundary layer. In addition, if there is no diffusion, one can only impose Dirichlet boundary conditions (i.e., prescribe a fixed temperature value at the boundary) at those boundaries where material flows in. This would correspond to the ``false'' setting of this parameter.
-1328
+1329
[Bool]
@@ -1439,7 +1460,7 @@ The names of the boundaries listed here can either be numbers (in which case the
This parameter only describes which boundaries have a fixed temperature, but not what temperature should hold on these boundaries. The latter piece of information needs to be implemented in a plugin in the BoundaryTemperature group, unless an existing implementation in this group already provides what you want.
-1327
+1328
[List of <[Anything]> of length 0...4294967295 (inclusive)]
@@ -1480,7 +1501,7 @@ Because this class simply takes what the initial temperature had described, this
`spherical constant': A model in which the temperature is chosen constant on the inner and outer boundaries of a spherical shell, ellipsoidal chunk or chunk. Parameters are read from subsection 'Spherical constant'.
-1324
+1325
[MultipleSelection ascii data|box|box with lithosphere boundary indicators|constant|dynamic core|function|initial temperature|spherical constant ]
@@ -1497,7 +1518,7 @@ add
A comma-separated list of operators that will be used to append the listed temperature models onto the previous models. If only one operator is given, the same operator is applied to all models.
-1325
+1326
[MultipleSelection add|subtract|minimum|maximum|replace if valid ]
@@ -1540,7 +1561,7 @@ Because this class simply takes what the initial temperature had described, this
\textbf{Warning}: This parameter provides an old and deprecated way of specifying boundary temperature models and shouldn't be used. Please use 'List of model names' instead.
-1326
+1327
[Selection ascii data|box|box with lithosphere boundary indicators|constant|dynamic core|function|initial temperature|spherical constant|unspecified ]
@@ -1558,7 +1579,7 @@ $ASPECT_SOURCE_DIR/data/boundary-temperature/ascii-data/test/
The name of a directory that contains the model data. This path may either be absolute (if starting with a `/') or relative to the current directory. The path may also include the special text `$ASPECT_SOURCE_DIR' which will be interpreted as the path in which the ASPECT source files were located when ASPECT was compiled. This interpretation allows, for example, to reference files located in the `data/' subdirectory of ASPECT.
-1339
+1340
[DirectoryName]
@@ -1575,7 +1596,7 @@ box_2d_%s.%d.txt
The file name of the model data. Provide file in format: (File name).\%s\%d, where \%s is a string specifying the boundary of the model according to the names of the boundary indicators (of the chosen geometry model), and \%d is any sprintf integer qualifier specifying the format of the current file number.
-1342
+1343
[Anything]
@@ -1592,7 +1613,7 @@ The file name of the model data. Provide file in format: (File name).\%s\%d, whe
Time step between following data files. Depending on the setting of the global `Use years in output instead of seconds' flag in the input file, this number is either interpreted as seconds or as years. The default is one million, i.e., either one million seconds or one million years.
-1343
+1344
[Double 0...MAX_DOUBLE (inclusive)]
@@ -1609,7 +1630,7 @@ false
In some cases the boundary files are not numbered in increasing but in decreasing order (e.g. `Ma BP'). If this flag is set to `True' the plugin will first load the file with the number `First data file number' and decrease the file number during the model run.
-1346
+1347
[Bool]
@@ -1626,7 +1647,7 @@ In some cases the boundary files are not numbered in increasing but in decreasin
The `First data file model time' parameter has been deactivated and will be removed in a future release. Do not use this parameter and instead provide data files starting from the model start time.
-1344
+1345
[Double 0...MAX_DOUBLE (inclusive)]
@@ -1643,7 +1664,7 @@ The `First data file model time' parameter has been deactivated and will be
Number of the first velocity file to be loaded when the model time is larger than `First velocity file model time'.
-1345
+1346
[Integer range -2147483648...2147483647 (inclusive)]
@@ -1660,7 +1681,7 @@ Number of the first velocity file to be loaded when the model time is larger tha
Scalar factor, which is applied to the model data. You might want to use this to scale the input to a reference model. Another way to use this factor is to convert units of the input files. For instance, if you provide velocities in cm/yr set this factor to 0.01.
-1341
+1342
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -1679,7 +1700,7 @@ Scalar factor, which is applied to the model data. You might want to use this to
Temperature at the bottom boundary (at minimal $z$-value). Units: \si{\kelvin}.
-1349
+1350
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -1696,7 +1717,7 @@ Temperature at the bottom boundary (at minimal $z$-value). Units: \si{\kelvin}.
Temperature at the left boundary (at minimal $x$-value). Units: \si{\kelvin}.
-1347
+1348
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -1713,7 +1734,7 @@ Temperature at the left boundary (at minimal $x$-value). Units: \si{\kelvin}.
Temperature at the right boundary (at maximal $x$-value). Units: \si{\kelvin}.
-1348
+1349
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -1730,7 +1751,7 @@ Temperature at the right boundary (at maximal $x$-value). Units: \si{\kelvin}.
Temperature at the top boundary (at maximal $x$-value). Units: \si{\kelvin}.
-1350
+1351
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -1749,7 +1770,7 @@ Temperature at the top boundary (at maximal $x$-value). Units: \si{\kelvin}.
Temperature at the bottom boundary (at minimal $z$-value). Units: \si{\kelvin}.
-1335
+1336
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -1766,7 +1787,7 @@ Temperature at the bottom boundary (at minimal $z$-value). Units: \si{\kelvin}.
Temperature at the left boundary (at minimal $x$-value). Units: \si{\kelvin}.
-1333
+1334
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -1783,7 +1804,7 @@ Temperature at the left boundary (at minimal $x$-value). Units: \si{\kelvin}.
Temperature at the additional left lithosphere boundary (specified by user in Geometry Model). Units: \si{\kelvin}.
-1337
+1338
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -1800,7 +1821,7 @@ Temperature at the additional left lithosphere boundary (specified by user in Ge
Temperature at the right boundary (at maximal $x$-value). Units: \si{\kelvin}.
-1334
+1335
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -1817,7 +1838,7 @@ Temperature at the right boundary (at maximal $x$-value). Units: \si{\kelvin}.
Temperature at the additional right lithosphere boundary (specified by user in Geometry Model). Units: \si{\kelvin}.
-1338
+1339
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -1834,7 +1855,7 @@ Temperature at the additional right lithosphere boundary (specified by user in G
Temperature at the top boundary (at maximal $x$-value). Units: \si{\kelvin}.
-1336
+1337
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -1849,7 +1870,7 @@ Temperature at the top boundary (at maximal $x$-value). Units: \si{\kelvin}.
A comma separated list of mappings between boundary indicators and the temperature associated with the boundary indicators. The format for this list is ``indicator1 : value1, indicator2 : value2, ...'', where each indicator is a valid boundary indicator (either a number or the symbolic name of a boundary as provided by the geometry model) and each value is the temperature of that boundary.
-1351
+1352
[Map of <[Anything]>:<[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -1868,7 +1889,7 @@ A comma separated list of mappings between boundary indicators and the temperatu
Core thermal expansivity. Units: \si{\per\kelvin}.
-1365
+1366
[Double 0...MAX_DOUBLE (inclusive)]
@@ -1885,7 +1906,7 @@ Core thermal expansivity. Units: \si{\per\kelvin}.
Compositional expansion coefficient $Beta_c$. See \cite{NPB+04} for more details.
-1368
+1369
[Double 0...MAX_DOUBLE (inclusive)]
@@ -1902,7 +1923,7 @@ Compositional expansion coefficient $Beta_c$. See \cite{NPB+04} for more details
Pressure at CMB. Units: \si{\pascal}.
-1359
+1360
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -1919,7 +1940,7 @@ Pressure at CMB. Units: \si{\pascal}.
Core heat conductivity $k_c$. Units: \si{\watt\per\meter\per\kelvin}.
-1370
+1371
[Double 0...MAX_DOUBLE (inclusive)]
@@ -1936,7 +1957,7 @@ Core heat conductivity $k_c$. Units: \si{\watt\per\meter\per\kelvin}.
Density of the core. Units: \si{\kilogram\per\meter\cubed}.
-1357
+1358
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -1953,7 +1974,7 @@ Density of the core. Units: \si{\kilogram\per\meter\cubed}.
Heat capacity of the core. Units: \si{\joule\per\kelvin\per\kilogram}.
-1362
+1363
[Double 0...MAX_DOUBLE (inclusive)]
@@ -1970,7 +1991,7 @@ Heat capacity of the core. Units: \si{\joule\per\kelvin\per\kilogram}.
Partition coefficient of the light element.
-1369
+1370
[Double 0...1 (inclusive)]
@@ -1987,7 +2008,7 @@ Partition coefficient of the light element.
Gravitation acceleration at CMB. Units: \si{\meter\per\second\squared}.
-1358
+1359
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -2004,7 +2025,7 @@ Gravitation acceleration at CMB. Units: \si{\meter\per\second\squared}.
Initial light composition (eg. S,O) concentration in weight fraction.
-1360
+1361
[Double 0...MAX_DOUBLE (inclusive)]
@@ -2021,7 +2042,7 @@ Initial light composition (eg. S,O) concentration in weight fraction.
Temperature at the inner boundary (core mantle boundary) at the beginning. Units: \si{\kelvin}.
-1353
+1354
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -2038,7 +2059,7 @@ Temperature at the inner boundary (core mantle boundary) at the beginning. Units
Core compressibility at zero pressure. See \cite{NPB+04} for more details.
-1363
+1364
[Double 0...MAX_DOUBLE (inclusive)]
@@ -2055,7 +2076,7 @@ Core compressibility at zero pressure. See \cite{NPB+04} for more details.
The latent heat of core freeze. Units: \si{\joule\per\kilogram}.
-1366
+1367
[Double 0...MAX_DOUBLE (inclusive)]
@@ -2072,7 +2093,7 @@ The latent heat of core freeze. Units: \si{\joule\per\kilogram}.
The max iterations for nonlinear core energy solver.
-1361
+1362
[Integer range 0...2147483647 (inclusive)]
@@ -2089,7 +2110,7 @@ The max iterations for nonlinear core energy solver.
Temperature at the outer boundary (lithosphere water/air). Units: \si{\kelvin}.
-1352
+1353
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -2106,7 +2127,7 @@ Temperature at the outer boundary (lithosphere water/air). Units: \si{\kelvin}.
The heat of reaction. Units: \si{\joule\per\kilogram}.
-1367
+1368
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -2123,7 +2144,7 @@ The heat of reaction. Units: \si{\joule\per\kilogram}.
Core density at zero pressure. Units: \si{\kilogram\per\meter\cubed}. See \cite{NPB+04} for more details.
-1364
+1365
[Double 0...MAX_DOUBLE (inclusive)]
@@ -2140,7 +2161,7 @@ Core density at zero pressure. Units: \si{\kilogram\per\meter\cubed}. See \cite{
Initial inner core radius changing rate. Units: \si{\kilo\meter}/year.
-1355
+1356
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -2157,7 +2178,7 @@ Initial inner core radius changing rate. Units: \si{\kilo\meter}/year.
Initial CMB temperature changing rate. Units: \si{\kelvin}/year.
-1354
+1355
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -2174,7 +2195,7 @@ Initial CMB temperature changing rate. Units: \si{\kelvin}/year.
Initial light composition changing rate. Units: 1/year.
-1356
+1357
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -2192,7 +2213,7 @@ true
If melting curve dependent on composition.
-1375
+1376
[Bool]
@@ -2209,7 +2230,7 @@ If melting curve dependent on composition.
Melting curve (\cite{NPB+04} eq. (40)) parameter Theta.
-1374
+1375
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -2226,7 +2247,7 @@ Melting curve (\cite{NPB+04} eq. (40)) parameter Theta.
Melting curve (\cite{NPB+04} eq. (40)) parameter Tm0. Units: \si{\kelvin}.
-1371
+1372
[Double 0...MAX_DOUBLE (inclusive)]
@@ -2243,7 +2264,7 @@ Melting curve (\cite{NPB+04} eq. (40)) parameter Tm0. Units: \si{\kelvin}.
Melting curve (\cite{NPB+04} eq. (40)) parameter Tm1. Units: \si{\per\tera\pascal}.
-1372
+1373
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -2260,7 +2281,7 @@ Melting curve (\cite{NPB+04} eq. (40)) parameter Tm1. Units: \si{\per\tera\pasca
Melting curve (\cite{NPB+04} eq. (40)) parameter Tm2. Units: \si{\per\tera\pascal\squared}.
-1373
+1374
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -2277,7 +2298,7 @@ false
If using the Fe-FeS system solidus from Buono \& Walker (2011) instead.
-1376
+1377
[Bool]
@@ -2292,7 +2313,7 @@ If using the Fe-FeS system solidus from Buono \& Walker (2011) instead.
Data file name for other energy source into the core. The 'other energy source' is used for external core energy source.For example if someone want to test the early lunar core powered by precession (Dwyer, C. A., et al. (2011). A long-lived lunar dynamo driven by continuous mechanical stirring. Nature 479(7372): 212-214.)Format [Time(Gyr) Energy rate(W)]
-1381
+1382
[Anything]
@@ -2307,7 +2328,7 @@ Data file name for other energy source into the core. The 'other energy sou
Half decay times of different elements (Ga)
-1379
+1380
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -2320,7 +2341,7 @@ Half decay times of different elements (Ga)
Heating rates of different elements (W/kg)
-1378
+1379
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -2333,7 +2354,7 @@ Heating rates of different elements (W/kg)
Initial concentrations of different elements (ppm)
-1380
+1381
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -2350,7 +2371,7 @@ Initial concentrations of different elements (ppm)
Number of different radioactive heating elements in core
-1377
+1378
[Integer range 0...2147483647 (inclusive)]
@@ -2370,7 +2391,7 @@ cartesian
A selection that determines the assumed coordinate system for the function variables. Allowed values are `cartesian', `spherical', and `depth'. `spherical' coordinates are interpreted as r,phi or r,phi,theta in 2d/3d respectively with theta being the polar angle. `depth' will create a function, in which only the first parameter is non-zero, which is interpreted to be the depth of the point.
-1382
+1383
[Selection cartesian|spherical|depth ]
@@ -2385,7 +2406,7 @@ Sometimes it is convenient to use symbolic constants in the expression that desc
A typical example would be to set this runtime parameter to `pi=3.1415926536' and then use `pi' in the expression of the actual formula. (That said, for convenience this class actually defines both `pi' and `Pi' by default, but you get the idea.)
-1385
+1386
[Anything]
@@ -2404,7 +2425,7 @@ The formula that denotes the function you want to evaluate for particular values
If the function you are describing represents a vector-valued function with multiple components, then separate the expressions for individual components by a semicolon.
-1384
+1385
[Anything]
@@ -2421,7 +2442,7 @@ If the function you are describing represents a vector-valued function with mult
Maximal temperature. Units: \si{\kelvin}.
-1387
+1388
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -2438,7 +2459,7 @@ Maximal temperature. Units: \si{\kelvin}.
Minimal temperature. Units: \si{\kelvin}.
-1386
+1387
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -2455,7 +2476,7 @@ x,y,t
The names of the variables as they will be used in the function, separated by commas. By default, the names of variables at which the function will be evaluated are `x' (in 1d), `x,y' (in 2d) or `x,y,z' (in 3d) for spatial coordinates and `t' for time. You can then use these variable names in your function expression and they will be replaced by the values of these variables at which the function is currently evaluated. However, you can also choose a different set of names for the independent variables at which to evaluate your function expression. For example, if you work in spherical coordinates, you may wish to set this input parameter to `r,phi,theta,t' and then use these variable names in your function expression.
-1383
+1384
[Anything]
@@ -2474,7 +2495,7 @@ The names of the variables as they will be used in the function, separated by co
Maximal temperature. Units: \si{\kelvin}.
-1330
+1331
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -2491,7 +2512,7 @@ Maximal temperature. Units: \si{\kelvin}.
Minimal temperature. Units: \si{\kelvin}.
-1329
+1330
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -2510,7 +2531,7 @@ Minimal temperature. Units: \si{\kelvin}.
Temperature at the inner boundary (core mantle boundary). Units: \si{\kelvin}.
-1332
+1333
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -2527,7 +2548,7 @@ Temperature at the inner boundary (core mantle boundary). Units: \si{\kelvin}.
Temperature at the outer boundary (lithosphere water/air). Units: \si{\kelvin}.
-1331
+1332
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -2561,7 +2582,7 @@ Gravity is expected to point along the depth direction.
`zero traction': Implementation of a model in which the boundary traction is zero. This is commonly referred to as an ``open boundary condition'', indicating that the material experiences no forces in response to what might exist on the other side of the boundary. However, this is only true in the case where hydrostatic pressure is not relevant. If hydrostatic pressure is not negligible, for example at the sides of a regional model, the material at the other side of the boundary does exceed a force, namely the force normal to the boundary induced by the hydrostatic pressure.
-1466
+1467
[Map of <[Anything]>:<[Selection ascii data|function|initial lithostatic pressure|zero traction ]> of length 0...4294967295 (inclusive)]
@@ -2579,7 +2600,7 @@ $ASPECT_SOURCE_DIR/data/boundary-traction/ascii-data/test/
The name of a directory that contains the model data. This path may either be absolute (if starting with a `/') or relative to the current directory. The path may also include the special text `$ASPECT_SOURCE_DIR' which will be interpreted as the path in which the ASPECT source files were located when ASPECT was compiled. This interpretation allows, for example, to reference files located in the `data/' subdirectory of ASPECT.
-1467
+1468
[DirectoryName]
@@ -2596,7 +2617,7 @@ box_2d_%s.%d.txt
The file name of the model data. Provide file in format: (File name).\%s\%d, where \%s is a string specifying the boundary of the model according to the names of the boundary indicators (of the chosen geometry model), and \%d is any sprintf integer qualifier specifying the format of the current file number.
-1470
+1471
[Anything]
@@ -2613,7 +2634,7 @@ The file name of the model data. Provide file in format: (File name).\%s\%d, whe
Time step between following data files. Depending on the setting of the global `Use years in output instead of seconds' flag in the input file, this number is either interpreted as seconds or as years. The default is one million, i.e., either one million seconds or one million years.
-1471
+1472
[Double 0...MAX_DOUBLE (inclusive)]
@@ -2630,7 +2651,7 @@ false
In some cases the boundary files are not numbered in increasing but in decreasing order (e.g. `Ma BP'). If this flag is set to `True' the plugin will first load the file with the number `First data file number' and decrease the file number during the model run.
-1474
+1475
[Bool]
@@ -2647,7 +2668,7 @@ In some cases the boundary files are not numbered in increasing but in decreasin
The `First data file model time' parameter has been deactivated and will be removed in a future release. Do not use this parameter and instead provide data files starting from the model start time.
-1472
+1473
[Double 0...MAX_DOUBLE (inclusive)]
@@ -2664,7 +2685,7 @@ The `First data file model time' parameter has been deactivated and will be
Number of the first velocity file to be loaded when the model time is larger than `First velocity file model time'.
-1473
+1474
[Integer range -2147483648...2147483647 (inclusive)]
@@ -2681,7 +2702,7 @@ Number of the first velocity file to be loaded when the model time is larger tha
Scalar factor, which is applied to the model data. You might want to use this to scale the input to a reference model. Another way to use this factor is to convert units of the input files. For instance, if you provide velocities in cm/yr set this factor to 0.01.
-1469
+1470
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -2700,7 +2721,7 @@ cartesian
A selection that determines the assumed coordinate system for the function variables. Allowed values are `cartesian', `spherical', and `depth'. `spherical' coordinates are interpreted as r,phi or r,phi,theta in 2d/3d respectively with theta being the polar angle. `depth' will create a function, in which only the first parameter is non-zero, which is interpreted to be the depth of the point.
-1475
+1476
[Selection cartesian|spherical|depth ]
@@ -2715,7 +2736,7 @@ Sometimes it is convenient to use symbolic constants in the expression that desc
A typical example would be to set this runtime parameter to `pi=3.1415926536' and then use `pi' in the expression of the actual formula. (That said, for convenience this class actually defines both `pi' and `Pi' by default, but you get the idea.)
-1479
+1480
[Anything]
@@ -2734,7 +2755,7 @@ The formula that denotes the function you want to evaluate for particular values
If the function you are describing represents a vector-valued function with multiple components, then separate the expressions for individual components by a semicolon.
-1478
+1479
[Anything]
@@ -2751,7 +2772,7 @@ false
Specify traction as $r$, $\phi$, and $\theta$ components instead of $x$, $y$, and $z$. Positive tractions point up, east, and north (in 3d) or out and clockwise (in 2d). This setting only makes sense for spherical geometries.
-1476
+1477
[Bool]
@@ -2768,7 +2789,7 @@ x,y,t
The names of the variables as they will be used in the function, separated by commas. By default, the names of variables at which the function will be evaluated are `x' (in 1d), `x,y' (in 2d) or `x,y,z' (in 3d) for spatial coordinates and `t' for time. You can then use these variable names in your function expression and they will be replaced by the values of these variables at which the function is currently evaluated. However, you can also choose a different set of names for the independent variables at which to evaluate your function expression. For example, if you work in spherical coordinates, you may wish to set this input parameter to `r,phi,theta,t' and then use these variable names in your function expression.
-1477
+1478
[Anything]
@@ -2787,7 +2808,7 @@ The names of the variables as they will be used in the function, separated by co
The number of integration points over which we integrate the lithostatic pressure downwards.
-1481
+1482
[Integer range 0...2147483647 (inclusive)]
@@ -2800,7 +2821,7 @@ The number of integration points over which we integrate the lithostatic pressur
The point where the pressure profile will be calculated. Cartesian coordinates $(x,y,z)$ when geometry is a box, otherwise enter radius, longitude, and in 3d latitude. Note that the coordinate related to the depth ($y$ in 2d Cartesian, $z$ in 3d Cartesian and radius in spherical coordinates) is not used. Units: \si{\meter} or degrees.
-1480
+1481
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -2834,7 +2855,7 @@ Likewise, since the symbol $t$ indicating time may appear in the formulas for th
`zero velocity': Implementation of a model in which the boundary velocity is zero. This is commonly referred to as a ``stick boundary condition'', indicating that the material ``sticks'' to the material on the other side of the boundary.
-1439
+1440
[Map of <[Anything]>:<[Selection ascii data|function|gplates|zero velocity ]> of length 0...4294967295 (inclusive)]
@@ -2849,7 +2870,7 @@ A comma separated list of names denoting those boundaries on which the velocity
The names of the boundaries listed here can either by numbers (in which case they correspond to the numerical boundary indicators assigned by the geometry object), or they can correspond to any of the symbolic names the geometry object may have provided for each part of the boundary. You may want to compare this with the documentation of the geometry model you use in your model.
-1441
+1442
[List of <[Anything]> of length 0...4294967295 (inclusive)]
@@ -2864,7 +2885,7 @@ A comma separated list of names denoting those boundaries on which the velocity
The names of the boundaries listed here can either by numbers (in which case they correspond to the numerical boundary indicators assigned by the geometry object), or they can correspond to any of the symbolic names the geometry object may have provided for each part of the boundary. You may want to compare this with the documentation of the geometry model you use in your model.
-1440
+1441
[List of <[Anything]> of length 0...4294967295 (inclusive)]
@@ -2882,7 +2903,7 @@ $ASPECT_SOURCE_DIR/data/boundary-velocity/ascii-data/test/
The name of a directory that contains the model data. This path may either be absolute (if starting with a `/') or relative to the current directory. The path may also include the special text `$ASPECT_SOURCE_DIR' which will be interpreted as the path in which the ASPECT source files were located when ASPECT was compiled. This interpretation allows, for example, to reference files located in the `data/' subdirectory of ASPECT.
-1442
+1443
[DirectoryName]
@@ -2899,7 +2920,7 @@ box_2d_%s.%d.txt
The file name of the model data. Provide file in format: (File name).\%s\%d, where \%s is a string specifying the boundary of the model according to the names of the boundary indicators (of the chosen geometry model), and \%d is any sprintf integer qualifier specifying the format of the current file number.
-1445
+1446
[Anything]
@@ -2916,7 +2937,7 @@ The file name of the model data. Provide file in format: (File name).\%s\%d, whe
Time step between following data files. Depending on the setting of the global `Use years in output instead of seconds' flag in the input file, this number is either interpreted as seconds or as years. The default is one million, i.e., either one million seconds or one million years.
-1446
+1447
[Double 0...MAX_DOUBLE (inclusive)]
@@ -2933,7 +2954,7 @@ false
In some cases the boundary files are not numbered in increasing but in decreasing order (e.g. `Ma BP'). If this flag is set to `True' the plugin will first load the file with the number `First data file number' and decrease the file number during the model run.
-1449
+1450
[Bool]
@@ -2950,7 +2971,7 @@ In some cases the boundary files are not numbered in increasing but in decreasin
The `First data file model time' parameter has been deactivated and will be removed in a future release. Do not use this parameter and instead provide data files starting from the model start time.
-1447
+1448
[Double 0...MAX_DOUBLE (inclusive)]
@@ -2967,7 +2988,7 @@ The `First data file model time' parameter has been deactivated and will be
Number of the first velocity file to be loaded when the model time is larger than `First velocity file model time'.
-1448
+1449
[Integer range -2147483648...2147483647 (inclusive)]
@@ -2984,7 +3005,7 @@ Number of the first velocity file to be loaded when the model time is larger tha
Scalar factor, which is applied to the model data. You might want to use this to scale the input to a reference model. Another way to use this factor is to convert units of the input files. For instance, if you provide velocities in cm/yr set this factor to 0.01.
-1444
+1445
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -3001,7 +3022,7 @@ false
Specify velocity as r, phi, and theta components instead of x, y, and z. Positive velocities point up, east, and north (in 3d) or out and clockwise (in 2d). This setting only makes sense for spherical geometries.
-1450
+1451
[Bool]
@@ -3020,7 +3041,7 @@ cartesian
A selection that determines the assumed coordinate system for the function variables. Allowed values are `cartesian', `spherical', and `depth'. `spherical' coordinates are interpreted as r,phi or r,phi,theta in 2d/3d respectively with theta being the polar angle. `depth' will create a function, in which only the first parameter is non-zero, which is interpreted to be the depth of the point.
-1451
+1452
[Selection cartesian|spherical|depth ]
@@ -3035,7 +3056,7 @@ Sometimes it is convenient to use symbolic constants in the expression that desc
A typical example would be to set this runtime parameter to `pi=3.1415926536' and then use `pi' in the expression of the actual formula. (That said, for convenience this class actually defines both `pi' and `Pi' by default, but you get the idea.)
-1455
+1456
[Anything]
@@ -3054,7 +3075,7 @@ The formula that denotes the function you want to evaluate for particular values
If the function you are describing represents a vector-valued function with multiple components, then separate the expressions for individual components by a semicolon.
-1454
+1455
[Anything]
@@ -3071,7 +3092,7 @@ false
Specify velocity as $r$, $\phi$, and $\theta$ components instead of $x$, $y$, and $z$. Positive velocities point up, east, and north (in 3d) or out and clockwise (in 2d). This setting only makes sense for spherical geometries.
-1452
+1453
[Bool]
@@ -3088,7 +3109,7 @@ x,y,t
The names of the variables as they will be used in the function, separated by commas. By default, the names of variables at which the function will be evaluated are `x' (in 1d), `x,y' (in 2d) or `x,y,z' (in 3d) for spatial coordinates and `t' for time. You can then use these variable names in your function expression and they will be replaced by the values of these variables at which the function is currently evaluated. However, you can also choose a different set of names for the independent variables at which to evaluate your function expression. For example, if you work in spherical coordinates, you may wish to set this input parameter to `r,phi,theta,t' and then use these variable names in your function expression.
-1453
+1454
[Anything]
@@ -3107,7 +3128,7 @@ $ASPECT_SOURCE_DIR/data/boundary-velocity/gplates/
The name of a directory that contains the model data. This path may either be absolute (if starting with a '/') or relative to the current directory. The path may also include the special text '$ASPECT_SOURCE_DIR' which will be interpreted as the path in which the ASPECT source files were located when ASPECT was compiled. This interpretation allows, for example, to reference files located in the `data/' subdirectory of ASPECT.
-1456
+1457
[DirectoryName]
@@ -3124,7 +3145,7 @@ The name of a directory that contains the model data. This path may either be ab
Time step between following velocity files. Depending on the setting of the global 'Use years in output instead of seconds' flag in the input file, this number is either interpreted as seconds or as years. The default is one million, i.e., either one million seconds or one million years.
-1461
+1462
[Double 0...MAX_DOUBLE (inclusive)]
@@ -3141,7 +3162,7 @@ false
In some cases the boundary files are not numbered in increasing but in decreasing order (e.g. 'Ma BP'). If this flag is set to 'True' the plugin will first load the file with the number 'First velocity file number' and decrease the file number during the model run.
-1460
+1461
[Bool]
@@ -3158,7 +3179,7 @@ In some cases the boundary files are not numbered in increasing but in decreasin
Time from which on the velocity file with number 'First velocity file number' is used as boundary condition. Previous to this time, a no-slip boundary condition is assumed. Depending on the setting of the global 'Use years in output instead of seconds' flag in the input file, this number is either interpreted as seconds or as years.
-1458
+1459
[Double 0...MAX_DOUBLE (inclusive)]
@@ -3175,7 +3196,7 @@ Time from which on the velocity file with number 'First velocity file numbe
Number of the first velocity file to be loaded when the model time is larger than 'First velocity file model time'.
-1459
+1460
[Integer range -2147483648...2147483647 (inclusive)]
@@ -3192,7 +3213,7 @@ Number of the first velocity file to be loaded when the model time is larger tha
Determines the depth of the lithosphere, so that the GPlates velocities can be applied at the sides of the model as well as at the surface.
-1465
+1466
[Double 0...MAX_DOUBLE (inclusive)]
@@ -3209,7 +3230,7 @@ Determines the depth of the lithosphere, so that the GPlates velocities can be a
Point that determines the plane in which a 2d model lies in. Has to be in the format `a,b' where a and b are theta (polar angle) and phi in radians. This value is not utilized in 3d geometries, and can therefore be set to the default or any user-defined quantity.
-1463
+1464
[Anything]
@@ -3226,7 +3247,7 @@ Point that determines the plane in which a 2d model lies in. Has to be in the fo
Point that determines the plane in which a 2d model lies in. Has to be in the format `a,b' where a and b are theta (polar angle) and phi in radians. This value is not utilized in 3d geometries, and can therefore be set to the default or any user-defined quantity.
-1464
+1465
[Anything]
@@ -3243,7 +3264,7 @@ Point that determines the plane in which a 2d model lies in. Has to be in the fo
Scalar factor, which is applied to the boundary velocity. You might want to use this to scale the velocities to a reference model (e.g. with free-slip boundary) or another plate reconstruction.
-1462
+1463
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -3260,7 +3281,7 @@ phi.%d
The file name of the material data. Provide file in format: (Velocity file name).\%d.gpml where \%d is any sprintf integer qualifier, specifying the format of the current file number.
-1457
+1458
[Anything]
@@ -3280,7 +3301,7 @@ The file name of the material data. Provide file in format: (Velocity file name)
The number of timesteps between performing checkpoints. If 0 and time between checkpoint is not specified, checkpointing will not be performed. Units: None.
-71
+72
[Integer range 0...2147483647 (inclusive)]
@@ -3297,7 +3318,7 @@ The number of timesteps between performing checkpoints. If 0 and time between ch
The wall time between performing checkpoints. If 0, will use the checkpoint step frequency instead. Units: Seconds.
-70
+71
[Integer range 0...2147483647 (inclusive)]
@@ -3321,7 +3342,7 @@ These choices correspond to the following methods by which compositional fields
\item ``prescribed field with diffusion'': If a compositional field is marked this way, the value of a specific additional material model output, called the `PrescribedFieldOutputs' is interpolated onto the field, as in the ``prescribed field'' method. Afterwards, the field is diffused based on a solver parameter, the diffusion length scale, smoothing the field. Specifically, the field is updated by solving the equation $(I-l^2 \Delta) C_\text{smoothed} = C_\text{prescribed}$, where $l$ is the diffusion length scale. Note that this means that the amount of diffusion is independent of the time step size, and that the field is not advected with the flow.\end{itemize}
-97
+98
[List of <[Selection field|particles|volume of fluid|static|melt field|darcy field|prescribed field|prescribed field with diffusion ]> of length 0...4294967295 (inclusive)]
@@ -3334,7 +3355,7 @@ These choices correspond to the following methods by which compositional fields
A list of integers smaller than or equal to the number of compositional fields. All compositional fields in this list will be normalized before the first timestep. The normalization is implemented in the following way: First, the sum of the fields to be normalized is calculated at every point and the global maximum is determined. Second, the compositional fields to be normalized are divided by this maximum.
-99
+100
[List of <[Integer range 0...2147483647 (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -3349,7 +3370,7 @@ A comma separated list denoting the particle properties that will be projected t
The format of valid entries for this parameter is that of a map given as ``key1: value1, key2: value2 [component2], key3: value3 [component4], ...'' where each key must be a valid field name of the ``particles'' type, and each value must be one of the currently selected particle properties. Component is a component index of the particle property that is 0 by default, but can be set up to n-1, where n is the number of vector components of this particle property. The component indicator only needs to be set if not the first component of the particle property should be mapped (e.g. the $y$-component of the velocity at the particle positions).
-98
+99
[Map of <[Anything]>:<[Anything]> of length 0...4294967295 (inclusive)]
@@ -3362,7 +3383,7 @@ The format of valid entries for this parameter is that of a map given as ``key1:
A user-defined name for each of the compositional fields requested.
-95
+96
[List of <[Anything]> of length 0...4294967295 (inclusive)]
@@ -3379,7 +3400,7 @@ A user-defined name for each of the compositional fields requested.
The number of fields that will be advected along with the flow field, excluding velocity, pressure and temperature.
-94
+95
[Integer range 0...2147483647 (inclusive)]
@@ -3396,7 +3417,7 @@ unspecified
A type for each of the compositional fields requested. Each entry of the list must be one of several recognized types: chemical composition, stress, strain, grain size, porosity, density, entropy, general and unspecified. The generic type is intended to be a placeholder type that has no effect on the running of any material model, while the unspecified type is intended to tell ASPECT that the user has not explicitly indicated the type of field (facilitating parameter file checking). Plugins such as material models can use these types to affect how that plugin functions.
-96
+97
[List of <[Selection chemical composition|stress|strain|grain size|porosity|density|entropy|generic|unspecified ]> of length 0...4294967295 (inclusive)]
@@ -3417,7 +3438,7 @@ The polynomial degree to use for the composition variable(s). As an example, a v
For continuous elements, the value needs to be 1 or larger as $Q_1$ is the lowest order element, while $DGQ_0$ is a valid choice. Units: None.
-74
+75
[List of <[Integer range 0...2147483647 (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -3436,7 +3457,7 @@ The polynomial degree to use for the velocity variables in the Stokes system. Th
Be careful if you choose 1 as the degree. The resulting element is not stable and it may lead to artifacts in the solution. Units: None.
-72
+73
[Integer range 1...2147483647 (inclusive)]
@@ -3453,7 +3474,7 @@ Be careful if you choose 1 as the degree. The resulting element is not stable an
The polynomial degree to use for the temperature variable. As an example, a value of 2 for this parameter will yield either the element $Q_2$ or $DGQ_2$ for the temperature field, depending on whether we use a continuous or discontinuous field. Units: None.
-73
+74
[Integer range 1...2147483647 (inclusive)]
@@ -3470,7 +3491,7 @@ false
Whether to use a composition discretization that is discontinuous as opposed to continuous. This then requires the assembly of face terms between cells, and weak imposition of boundary terms for the composition field via the discontinuous Galerkin method.
-78
+79
[List of <[Bool]> of length 0...4294967295 (inclusive)]
@@ -3487,7 +3508,7 @@ false
Whether to use a temperature discretization that is discontinuous as opposed to continuous. This then requires the assembly of face terms between cells, and weak imposition of boundary terms for the temperature field via the interior-penalty discontinuous Galerkin method.
-77
+78
[Bool]
@@ -3512,7 +3533,7 @@ While \aspect{} \textit{allows} you to use this method, it is generally understo
:::
-76
+77
[Bool]
@@ -3537,7 +3558,7 @@ On the other hand, if this parameter is set to ``false''(the default),
For an in-depth discussion of these issues and a quantitative evaluation of the different choices, see \cite{kronbichler:etal:2012}.
-75
+76
[Bool]
@@ -3555,7 +3576,7 @@ For an in-depth discussion of these issues and a quantitative evaluation of the
The value used to penalize discontinuities in the discontinuous Galerkin method. This is used only for the temperature field, and not for the composition field, as pure advection does not use the interior penalty method. This is largely empirically decided -- it must be large enough to ensure the bilinear form is coercive, but not so large as to penalize discontinuity at all costs.
-86
+87
[Double 0...MAX_DOUBLE (inclusive)]
@@ -3572,7 +3593,7 @@ The value used to penalize discontinuities in the discontinuous Galerkin method.
The maximum global composition values that will be used in the bound preserving limiter for the discontinuous solutions from composition advection fields. The number of the input 'Global composition maximum' values separated by ',' has to be one or the same as the number of the compositional fields. When only one value is supplied, this same value is assumed for all compositional fields.
-91
+92
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -3589,7 +3610,7 @@ The maximum global composition values that will be used in the bound preserving
The minimum global composition value that will be used in the bound preserving limiter for the discontinuous solutions from composition advection fields. The number of the input 'Global composition minimum' values separated by ',' has to be one or the same as the number of the compositional fields. When only one value is supplied, this same value is assumed for all compositional fields.
-92
+93
[List of <[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -3606,7 +3627,7 @@ The minimum global composition value that will be used in the bound preserving l
The maximum global temperature value that will be used in the bound preserving limiter for the discontinuous solutions from temperature advection fields.
-89
+90
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -3623,7 +3644,7 @@ The maximum global temperature value that will be used in the bound preserving l
The minimum global temperature value that will be used in the bound preserving limiter for the discontinuous solutions from temperature advection fields.
-90
+91
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -3636,7 +3657,7 @@ The minimum global temperature value that will be used in the bound preserving l
Select for which compositional fields to skip the entropy viscosity stabilization at dirichlet boundaries. This is only advisable for compositional fieldsthat have intrinsic physical diffusion terms, otherwise oscillations may develop. The parameter should contain a list of compositional field names.
-80
+81
[List of <[Anything]> of length 0...4294967295 (inclusive)]
@@ -3653,7 +3674,7 @@ entropy viscosity
Select the method for stabilizing the advection equation. The original method implemented is 'entropy viscosity' as described in \cite {kronbichler:etal:2012}. SUPG is currently experimental.
-79
+80
[Selection entropy viscosity|SUPG ]
@@ -3670,7 +3691,7 @@ false
If set to false, the artificial viscosity of a cell is computed and is computed on every cell separately as discussed in \cite{kronbichler:etal:2012}. If set to true, the maximum of the artificial viscosity in the cell as well as the neighbors of the cell is computed and used instead.
-81
+82
[Bool]
@@ -3687,7 +3708,7 @@ false
Whether to apply the bound preserving limiter as a correction after having the discontinuous composition solution. The limiter will only have an effect if the 'Global composition maximum' and 'Global composition minimum' parameters are defined in the .prm file. This limiter keeps the discontinuous solution in the range given by Global composition maximum' and 'Global composition minimum'. The number of input values in this parameter separated by ',' has to be one or the number of the compositional fields. When only one value is supplied, this same value is assumed for all compositional fields, otherwise each value represents if the limiter should be applied to the respective compositional field. Because this limiter modifies the solution it no longer satisfies the assembled equation. Therefore, the nonlinear residual for this field is meaningless, and in nonlinear solvers we will ignore the residual for this field to evaluate if the nonlinear solver has converged.
-88
+89
[List of <[Bool]> of length 0...4294967295 (inclusive)]
@@ -3704,7 +3725,7 @@ false
Whether to apply the bound preserving limiter as a correction after computing the discontinuous temperature solution. The limiter will only have an effect if the 'Global temperature maximum' and 'Global temperature minimum' parameters are defined in the .prm file. This limiter keeps the discontinuous solution in the range given by 'Global temperature maximum' and 'Global temperature minimum'. Because this limiter modifies the solution it no longer satisfies the assembled equation. Therefore, the nonlinear residual for this field is meaningless, and in nonlinear solvers we will ignore the residual for this field to evaluate if the nonlinear solver has converged.
-87
+88
[Bool]
@@ -3721,7 +3742,7 @@ Whether to apply the bound preserving limiter as a correction after computing th
The exponent $\alpha$ in the entropy viscosity stabilization. Valid options are 1 or 2. The recommended setting is 2. (This parameter does not correspond to any variable in the 2012 paper by Kronbichler, Heister and Bangerth that describes ASPECT, see \cite{kronbichler:etal:2012}. Rather, the paper always uses 2 as the exponent in the definition of the entropy, following equation (15) of the paper. The full approach is discussed in \cite{guermond:etal:2011}.) Note that this is not the thermal expansion coefficient, also commonly referred to as $\alpha$.Units: None.
-82
+83
[Integer range 1...2 (inclusive)]
@@ -3738,7 +3759,7 @@ The exponent $\alpha$ in the entropy viscosity stabilization. Valid options are
The $\beta$ factor in the artificial viscosity stabilization. This parameter controls the maximum dissipation of the entropy viscosity, which is the part that only scales with the cell diameter and the maximum velocity in the cell, but does not depend on the solution field itself or its residual. An appropriate value for 2d is 0.052 and 0.78 for 3d. (For historical reasons, the name used here is different from the one used in the 2012 paper by Kronbichler, Heister and Bangerth that describes ASPECT, see \cite{kronbichler:etal:2012}. This parameter can be given as a single value or as a list with as many entries as one plus the number of compositional fields. In the former case all advection fields use the same stabilization parameters, in the latter case each field (temperature first, then all compositions) use individual parameters. This can be useful to reduce the stabilization for the temperature, which already has some physical diffusion. This parameter corresponds to the factor $\alpha_{\text{max}}$ in the formulas following equation (15) of the paper.) Units: None.
-84
+85
[List of <[Double 0...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -3755,7 +3776,7 @@ The $\beta$ factor in the artificial viscosity stabilization. This parameter con
The $c_R$ factor in the entropy viscosity stabilization. This parameter controls the part of the entropy viscosity that depends on the solution field itself and its residual in addition to the cell diameter and the maximum velocity in the cell. This parameter can be given as a single value or as a list with as many entries as one plus the number of compositional fields. In the former case all advection fields use the same stabilization parameters, in the latter case each field (temperature first, then all compositions) use individual parameters. This can be useful to reduce the stabilization for the temperature, which already has some physical diffusion. (For historical reasons, the name used here is different from the one used in the 2012 paper by Kronbichler, Heister and Bangerth that describes ASPECT, see \cite{kronbichler:etal:2012}. This parameter corresponds to the factor $\alpha_E$ in the formulas following equation (15) of the paper.) Units: None.
-83
+84
[List of <[Double 0...MAX_DOUBLE (inclusive)]> of length 0...4294967295 (inclusive)]
@@ -3772,7 +3793,7 @@ The $c_R$ factor in the entropy viscosity stabilization. This parameter controls
The strain rate scaling factor in the artificial viscosity stabilization. This parameter determines how much the strain rate (in addition to the velocity) should influence the stabilization. (This parameter does not correspond to any variable in the 2012 paper by Kronbichler, Heister and Bangerth that describes ASPECT, see \cite{kronbichler:etal:2012}. Rather, the paper always uses 0, i.e. they specify the maximum dissipation $\nu_h^\text{max}$ as $\nu_h^\text{max}\vert_K = \alpha_{\text{max}} h_K \|\mathbf u\|_{\infty,K}$. Here, we use $\|\lvert\mathbf u\rvert + \gamma h_K \lvert\varepsilon (\mathbf u)\rvert\|_{\infty,K}$ instead of $\|\mathbf u\|_{\infty,K}$. Units: None.
-85
+86
[Double 0...MAX_DOUBLE (inclusive)]
@@ -3792,7 +3813,7 @@ false
Whether to ask the material model for additional terms for the right-hand side of the Stokes equation. This feature is likely only used when implementing force vectors for manufactured solution problems and requires filling additional outputs of type AdditionalMaterialOutputsStokesRHS.
-51
+52
[Bool]
@@ -3809,7 +3830,7 @@ false
Whether to include the additional elastic terms on the right-hand side of the Stokes equation.
-52
+53
[Bool]
@@ -3826,7 +3847,7 @@ false
Whether to include additional terms on the right-hand side of the Stokes equation to set a given compression term specified in the MaterialModel output PrescribedPlasticDilation.
-53
+54
[Bool]
@@ -3852,7 +3873,7 @@ The `anelastic liquid approximation' option here can also be used to set up
:::
-48
+49
[Selection isentropic compression|custom|anelastic liquid approximation|Boussinesq approximation ]
@@ -3869,7 +3890,7 @@ ask material model
Possible approximations for the density derivatives in the mass conservation equation. Note that this parameter is only evaluated if `Formulation' is set to `custom'. Other formulations ignore the value of this parameter.
-49
+50
[Selection incompressible|isentropic compression|hydrostatic compression|reference density profile|implicit reference density profile|projected density field|ask material model ]
@@ -3886,7 +3907,7 @@ real density
Possible approximations for the density in the temperature equation. Possible approximations are `real density' and `reference density profile'. Note that this parameter is only evaluated if `Formulation' is set to `custom'. Other formulations ignore the value of this parameter.
-50
+51
[Selection real density|reference density profile ]
@@ -3943,7 +3964,7 @@ The model assigns boundary indicators as follows: In 2d, inner and outer boundar
In 3d, inner and outer indicators are treated as in 2d. If the opening angle is chosen as 90 degrees, i.e., the domain is the intersection of a spherical shell and the first octant, then indicator 2 is at the face $x=0$, 3 at $y=0$, and 4 at $z=0$. These last three boundaries can then also be referred to as `east', `west' and `south' symbolically in input files.
-1067
+1068
[Selection box|box with lithosphere boundary indicators|chunk|chunk with lithosphere boundary indicators|ellipsoidal chunk|sphere|spherical shell|unspecified ]
@@ -3961,7 +3982,7 @@ In 3d, inner and outer indicators are treated as in 2d. If the opening angle is
X coordinate of box origin. Units: \si{\meter}.
-1111
+1112
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -3978,7 +3999,7 @@ X coordinate of box origin. Units: \si{\meter}.
Y coordinate of box origin. Units: \si{\meter}.
-1112
+1113
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -3995,7 +4016,7 @@ Y coordinate of box origin. Units: \si{\meter}.
Z coordinate of box origin. This value is ignored if the simulation is in 2d. Units: \si{\meter}.
-1113
+1114
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -4012,7 +4033,7 @@ Z coordinate of box origin. This value is ignored if the simulation is in 2d. Un
Extent of the box in x-direction. Units: \si{\meter}.
-1108
+1109
[Double 0...MAX_DOUBLE (inclusive)]
@@ -4029,7 +4050,7 @@ false
Whether the box should be periodic in X direction
-1117
+1118
[Bool]
@@ -4046,7 +4067,7 @@ Whether the box should be periodic in X direction
Number of cells in X direction.
-1114
+1115
[Integer range 1...2147483647 (inclusive)]
@@ -4063,7 +4084,7 @@ Number of cells in X direction.
Extent of the box in y-direction. Units: \si{\meter}.
-1109
+1110
[Double 0...MAX_DOUBLE (inclusive)]
@@ -4080,7 +4101,7 @@ false
Whether the box should be periodic in Y direction
-1118
+1119
[Bool]
@@ -4097,7 +4118,7 @@ Whether the box should be periodic in Y direction
Number of cells in Y direction.
-1115
+1116
[Integer range 1...2147483647 (inclusive)]
@@ -4114,7 +4135,7 @@ Number of cells in Y direction.
Extent of the box in z-direction. This value is ignored if the simulation is in 2d. Units: \si{\meter}.
-1110
+1111
[Double 0...MAX_DOUBLE (inclusive)]
@@ -4131,7 +4152,7 @@ false
Whether the box should be periodic in Z direction
-1119
+1120
[Bool]
@@ -4148,7 +4169,7 @@ Whether the box should be periodic in Z direction
Number of cells in Z direction.
-1116
+1117
[Integer range 1...2147483647 (inclusive)]
@@ -4167,7 +4188,7 @@ Number of cells in Z direction.
X coordinate of box origin. Units: \si{\meter}.
-1082
+1083
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -4184,7 +4205,7 @@ X coordinate of box origin. Units: \si{\meter}.
Y coordinate of box origin. Units: \si{\meter}.
-1083
+1084
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -4201,7 +4222,7 @@ Y coordinate of box origin. Units: \si{\meter}.
Z coordinate of box origin. This value is ignored if the simulation is in 2d. Units: \si{\meter}.
-1084
+1085
[Double -MAX_DOUBLE...MAX_DOUBLE (inclusive)]
@@ -4218,7 +4239,7 @@ Z coordinate of box origin. This value is ignored if the simulation is in 2d. Un
The thickness of the lithosphere used to create additional boundary indicators to set specific boundary conditions for the lithosphere.
-1078
+1079
[Double 0...MAX_DOUBLE (inclusive)]
@@ -4235,7 +4256,7 @@ true
Whether to make the grid by gluing together two boxes, or just use one chunk to make the grid. Using two grids glued together is a safer option, since it forces the boundary conditions to be always applied to the same depth, but using one grid allows for a more flexible usage of the adaptive refinement. Note that if there is no cell boundary exactly on the boundary between the lithosphere and the mantle, the velocity boundary will not be exactly at that depth. Therefore, using a merged grid is generally recommended over using one grid.When using one grid, the parameter for lower repetitions is used and the upper repetitions are ignored.
-1095
+1096
[Bool]
@@ -4252,7 +4273,7 @@ Whether to make the grid by gluing together two boxes, or just use one chunk to
Extent of the box in x-direction. Units: \si{\meter}.
-1079
+1080
[Double 0...MAX_DOUBLE (inclusive)]
@@ -4269,7 +4290,7 @@ false
Whether the box should be periodic in X direction.
-1090
+1091
[Bool]
@@ -4286,7 +4307,7 @@ false
Whether the box should be periodic in X direction in the lithosphere.
-1093
+1094
[Bool]
@@ -4303,7 +4324,7 @@ Whether the box should be periodic in X direction in the lithosphere.
Number of cells in X direction of the lower box. The same number of repetitions will be used in the upper box.
-1085
+1086
[Integer range 1...2147483647 (inclusive)]
@@ -4320,7 +4341,7 @@ Number of cells in X direction of the lower box. The same number of repetitions
Extent of the box in y-direction. Units: \si{\meter}.
-1080
+1081
[Double 0...MAX_DOUBLE (inclusive)]
@@ -4337,7 +4358,7 @@ false
Whether the box should be periodic in Y direction.
-1091
+1092
[Bool]
@@ -4354,7 +4375,7 @@ false
Whether the box should be periodic in Y direction in the lithosphere. This value is ignored if the simulation is in 2d.
-1094
+1095
[Bool]
@@ -4371,7 +4392,7 @@ Whether the box should be periodic in Y direction in the lithosphere. This value
Number of cells in Y direction of the lower box. If the simulation is in 3d, the same number of repetitions will be used in the upper box.
-1086
+1087
[Integer range 1...2147483647 (inclusive)]
@@ -4388,7 +4409,7 @@ Number of cells in Y direction of the lower box. If the simulation is in 3d, the
Number of cells in Y direction in the lithosphere. This value is ignored if the simulation is in 3d.
-1088
+1089
[Integer range 1...2147483647 (inclusive)]
@@ -4405,7 +4426,7 @@ Number of cells in Y direction in the lithosphere. This value is ignored if the
Extent of the box in z-direction. This value is ignored if the simulation is in 2d. Units: \si{\meter}.
-1081
+1082
[Double 0...MAX_DOUBLE (inclusive)]
@@ -4422,7 +4443,7 @@ false
Whether the box should be periodic in Z direction. This value is ignored if the simulation is in 2d.
-1092
+1093
[Bool]
@@ -4439,7 +4460,7 @@ Whether the box should be periodic in Z direction. This value is ignored if the
Number of cells in Z direction of the lower box. This value is ignored if the simulation is in 2d.
-1087
+1088
[Integer range 1...2147483647 (inclusive)]
@@ -4456,7 +4477,7 @@ Number of cells in Z direction of the lower box. This value is ignored if the si
Number of cells in Z direction in the lithosphere. This value is ignored if the simulation is in 2d.
-1089
+1090
[Integer range 1...2147483647 (inclusive)]
@@ -4475,7 +4496,7 @@ Number of cells in Z direction in the lithosphere. This value is ignored if the
Radius at the bottom surface of the chunk. Units: \si{\meter}.
-1120
+1121
[Double 0...MAX_DOUBLE (inclusive)]
@@ -4492,7 +4513,7 @@ Radius at the bottom surface of the chunk. Units: \si{\meter}.
Maximum latitude of the chunk. This value is ignored if the simulation is in 2d. Units: degrees.
-1125
+1126
[Double -90...90 (inclusive)]
@@ -4509,7 +4530,7 @@ Maximum latitude of the chunk. This value is ignored if the simulation is in 2d.
Maximum longitude of the chunk. Units: degrees.
-1123
+1124
[Double -180...360 (inclusive)]
@@ -4526,7 +4547,7 @@ Maximum longitude of the chunk. Units: degrees.
Minimum latitude of the chunk. This value is ignored if the simulation is in 2d. Units: degrees.
-1124
+1125
[Double -90...90 (inclusive)]
@@ -4543,7 +4564,7 @@ Minimum latitude of the chunk. This value is ignored if the simulation is in 2d.
Minimum longitude of the chunk. Units: degrees.
-1122
+1123
[Double -180...360 (inclusive)]
@@ -4560,7 +4581,7 @@ Minimum longitude of the chunk. Units: degrees.
Radius at the top surface of the chunk. Units: \si{\meter}.
-1121
+1122
[Double 0...MAX_DOUBLE (inclusive)]
@@ -4577,7 +4598,7 @@ Radius at the top surface of the chunk. Units: \si{\meter}.
Number of cells in latitude. This value is ignored if the simulation is in 2d
-1128
+1129
[Integer range 1...2147483647 (inclusive)]
@@ -4594,7 +4615,7 @@ Number of cells in latitude. This value is ignored if the simulation is in 2d
Number of cells in longitude.
-1127
+1128
[Integer range 1...2147483647 (inclusive)]
@@ -4611,7 +4632,7 @@ Number of cells in longitude.
Number of cells in radius.
-1126
+1127
[Integer range 1...2147483647 (inclusive)]
@@ -4630,7 +4651,7 @@ Number of cells in radius.
Radius at the bottom surface of the chunk. Units: \si{\meter}.
-1096
+1097
[Double 0...MAX_DOUBLE (inclusive)]
@@ -4647,7 +4668,7 @@ Radius at the bottom surface of the chunk. Units: \si{\meter}.
Maximum latitude of the chunk. This value is ignored if the simulation is in 2d. Units: degrees.
-1102
+1103
[Double -90...90 (inclusive)]
@@ -4664,7 +4685,7 @@ Maximum latitude of the chunk. This value is ignored if the simulation is in 2d.
Maximum longitude of the chunk. Units: degrees.
-1100
+1101
[Double -180...360 (inclusive)]
@@ -4681,7 +4702,7 @@ Maximum longitude of the chunk. Units: degrees.
Radius at the top surface of the lower chunk, where it merges with the upper chunk. Units: \si{\meter}.
-1098
+1099
[Double 0...MAX_DOUBLE (inclusive)]
@@ -4698,7 +4719,7 @@ Radius at the top surface of the lower chunk, where it merges with the upper chu
Minimum latitude of the chunk. This value is ignored if the simulation is in 2d. Units: degrees.
-1101
+1102
[Double -90...90 (inclusive)]
@@ -4715,7 +4736,7 @@ Minimum latitude of the chunk. This value is ignored if the simulation is in 2d.
Minimum longitude of the chunk. Units: degrees.
-1099
+1100
[Double -180...360 (inclusive)]
@@ -4732,7 +4753,7 @@ Minimum longitude of the chunk. Units: degrees.
Radius at the top surface of the chunk. Units: \si{\meter}.
-1097
+1098
[Double 0...MAX_DOUBLE (inclusive)]
@@ -4749,7 +4770,7 @@ Radius at the top surface of the chunk. Units: \si{\meter}.
Number of cells in radial direction for the lower chunk.
-1104
+1105
[Integer range 1...2147483647 (inclusive)]
@@ -4766,7 +4787,7 @@ Number of cells in radial direction for the lower chunk.
Number of cells in latitude. This value is ignored if the simulation is in 2d
-1106
+1107
[Integer range 1...2147483647 (inclusive)]
@@ -4783,7 +4804,7 @@ Number of cells in latitude. This value is ignored if the simulation is in 2d
Number of cells in longitude.
-1105
+1106
[Integer range 1...2147483647 (inclusive)]
@@ -4800,7 +4821,7 @@ Number of cells in longitude.
Number of cells in radial direction for the upper chunk.
-1103
+1104
[Integer range 1...2147483647 (inclusive)]
@@ -4817,7 +4838,7 @@ true
Whether to make the grid by gluing together two boxes, or just use one chunk to make the grid. Using two grids glued together is a safer option, since it forces the boundary conditions to be always applied to the same depth, but using one grid allows for a more flexible usage of the adaptive refinement. Note that if there is no cell boundary exactly on the boundary between the lithosphere and the mantle, the velocity boundary will not be exactly at that depth. Therefore, using a merged grid is generally recommended over using one grid. When using one grid, the parameter for lower repetitions is used and the upper repetitions are ignored.
-1107
+1108
[Bool]
@@ -4836,7 +4857,7 @@ Whether to make the grid by gluing together two boxes, or just use one chunk to
Bottom depth of model region.
-1133
+1134
[Double 0...MAX_DOUBLE (inclusive)]
@@ -4853,7 +4874,7 @@ Bottom depth of model region.
The number of subdivisions of the coarse (initial) mesh in depth.
-1138
+1139
[Integer range 0...2147483647 (inclusive)]
@@ -4870,7 +4891,7 @@ The number of subdivisions of the coarse (initial) mesh in depth.
The number of subdivisions of the coarse (initial) mesh in the East-West direction.
-1136
+1137
[Integer range 0...2147483647 (inclusive)]
@@ -4887,7 +4908,7 @@ The number of subdivisions of the coarse (initial) mesh in the East-West directi
Eccentricity of the ellipsoid. Zero is a perfect sphere, default (8.1819190842622e-2) is WGS84.