Stone¶
STONE simulates the three-dimensional trajectories of rockfalls on a digital elevation model (Guzzetti et al., 2002). The module is a port of the GRASS GIS r.stone addon, itself a port of the original STONE code by Fausto Guzzetti and Massimiliano Alvioli.
A rockfall is simulated as a point-like boulder that falls, bounces and rolls on the terrain:
the DEM is used as a triangular network: each square between four cell centers is split into two triangles, on which the motion is computed;
the boulders start from the center of the source cells, with the start velocity, in the direction of steepest descent towards the neighbouring cells;
a flying boulder follows a parabola until it hits the terrain. At the bounce it keeps the given percentages of its velocity normal and tangential to the terrain, the normal and tangential restitution coefficients;
after a short and slow bounce (two impacts closer than 3 m, at less than 5 m/s) the boulder starts rolling, slowed down by the rolling friction coefficient, and flies again where the terrain drops away under it;
a boulder stops when its velocity falls under the stop velocity, when it reaches a stop cell (value -1 in the sources), when it bounces on a cell with a normal restitution of 0 (as fallen into water), or when it leaves the DEM.
The start direction of each boulder, and the coefficients of each bounce and roll, are drawn at random around the values of the maps, with the given distributions and variabilities. So the boulders thrown from the same cell follow different trajectories, and the results have a probabilistic meaning. The random numbers of each source cell come from a fixed seed and the position of the cell: the same input always gives the same result, and the trajectories of a source don’t depend on the other sources.
The results are:
the counter, the number of trajectories crossing each cell. With one boulder per source it shows where single random falls from all the sources go; more boulders per source also show the rarer long runouts, and give the counts the meaning of a frequency;
the maximum velocity of the boulders in each cell;
the maximum height of the trajectories over the ground in each cell, useful for example to size protection barriers;
optionally, the 3D lines of a sample of the trajectories, chosen evenly over all the sources, with their maximum velocity and height. The flights are drawn along their exact parabola every meter.
The input maps can be prepared from as little as a DEM with the StoneInputs module. Example values of the coefficients for the lithological classes of Italy are in Alvioli et al. (2021), and listed on that page.
The step¶
The boulders are moved and their positions recorded about every step meters (pStep), as in the original model, where the step was fixed to 5 m. The step is limited to the cell size, since larger steps let the boulders jump over cells. The results depend on the step: finer steps give longer runouts, mostly because with coarse steps more boulders are lost when they pass from a triangle to the next. Keep the default of 5 m to compare the results with those of the original model and of the literature.
Differences from r.stone¶
The counter counts all the cells crossed between two recorded points, while r.stone counts only the cells containing a point: with a 5 m step on 10 m cells, about 10% more counts. The cells crossed between two points get the velocity and the height interpolated between them.
The maximum velocity and height are real numbers, r.stone truncates them to integers.
The random numbers differ, so the single trajectories differ: the results are equivalent in their statistics, as the results of two runs of r.stone with different random numbers.
Parameters¶
The STONE model for the three-dimensional simulation of rockfall trajectories.
Toolbox folder: Hydro-Geomorphology
Status: Experimental
Keywords: Rockfall, Stone, Hazard, Trajectories
Authors: Fausto Guzzetti, Massimiliano Alvioli, Andrea Antonello
Class: org.hortonmachine.modules.Stone
Inputs
Parameter |
Type |
Unit |
Default |
Description |
|---|---|---|---|---|
|
raster file |
The map of the digital elevation model (DEM). |
||
|
raster file |
The map of sources and stop areas: positive integer values are the number of trajectories simulated from the cell, -1 marks areas where boulders stop (e.g. lakes). |
||
|
raster file |
The map of the normal restitution coefficient used at impact points, as integer percentage, from 0 (total energy damping) to 100 (elastic restitution). |
||
|
raster file |
The map of the tangential restitution coefficient used at impact points, as integer percentage, from 0 (total energy damping) to 100 (elastic restitution). |
||
|
raster file |
The map of the rolling friction coefficient tan(beta) (e.g. 0.85 for alluvial deposits, 0.30 for bedrock). |
||
|
double |
|
The start velocity of the boulders [m/s]. |
|
|
double |
|
The velocity under which a boulder stops [m/s]. |
|
|
int |
|
The variability of the start angle around the direction of steepest descent, as percentage of 45 degrees. |
|
|
int |
|
The variability of the normal restitution around the cell value, in percentage points. |
|
|
int |
|
The variability of the tangential restitution around the cell value, in percentage points. |
|
|
int |
|
The variability of the friction coefficient around the cell value, in hundredths. |
|
|
String |
|
The distribution of the start angle around the direction of steepest descent. Allowed values: |
|
|
String |
|
The distribution of the restitution and friction coefficients around the cell values. Allowed values: |
|
|
double |
|
The spatial step of the trajectories [m]: boulders are moved and recorded about every step. It is limited to the cell size. The results depend on it (finer steps give longer runouts), the default of 5 m is the one of the original model. |
|
|
int |
|
The number of boulders, about, whose trajectories are stored, sampled over all sources (0 for none). |
Outputs
Parameter |
Type |
Unit |
Description |
|---|---|---|---|
|
output file |
The map of the number of trajectories passing through each cell. |
|
|
output file |
The optional map of the maximum velocity of the boulders in each cell [m/s]. |
|
|
output file |
The optional map of the maximum height of the trajectories over the ground in each cell [m]. |
|
|
output file |
The optional vector file of the 3D lines of a sample of pMaxTrajectories trajectories, with the source cell, the maximum velocity [m/s] and the maximum height over the ground [m]. |
References
Guzzetti, F., Crosta, G., Detti, R., Agliardi, F. (2002). STONE: a computer program for the three-dimensional simulation of rock-falls. Computers & Geosciences, 28(9), 1079-1093.
Alvioli, M., et al. (2021). Rockfall susceptibility and network-ranked susceptibility along the Italian railway. Engineering Geology, 293, 106301.
Example¶
The example runs on the sample elevation model of the manual, dtm_flanginec.tif in docs/manual/modules/maps/data, each module on the outputs of the previous ones:
import org.hortonmachine.modules.Stone
// the folder with the elevation model: change it to yours
var folder = "/data/flanginec/"
var stone = new Stone()
stone.inElev = folder + "dtm_flanginec.tif"
// the inputs prepared by StoneInputs
stone.inSources = folder + "sources.tif"
stone.inNormalRestitution = folder + "nrest.tif"
stone.inTangentialRestitution = folder + "trest.tif"
stone.inFriction = folder + "friction.tif"
stone.outCounter = folder + "counter.tif"
stone.outMaxVelocity = folder + "velocity.tif"
stone.outMaxDz = folder + "height.tif"
// a sample of the trajectories, as 3D lines
stone.pMaxTrajectories = 300
stone.outTrajectories = folder + "trajectories.shp"
stone.process()
The number of trajectories crossing each cell, with 10 boulders from each source of StoneInputs and the coefficients of the unclassified class everywhere.¶
The maximum velocity of the boulders in each cell, in m/s.¶
The maximum height of the trajectories over the ground in each cell, in m.¶
A sample of 300 trajectories, colored by the maximum velocity of their boulder, in m/s.¶