Skip to main content
Version: 3.4.8 (unreleased)

Analysis Runs

The Analysis Runs branch keeps a record of every Slope Stability, Block Size, Key Blocks, Bench As-built, Tunnel As-built, Rockfall Inventory and Rockfall Trajectories run. A run records what it was made from — the object, the settings, the sets it read, the random seed, the build of VRGS — and which layers it wrote. When a set it read changes afterwards, the run is marked stale, so you know its layers no longer match your interpretation.

Each object and each scale is a run of its own: Slope Stability at three scales on one mesh records three runs.

A run is listed as Analysis (scale): object (date and time in UTC), for example Slope stability (Bench): Pit wall (2026-10-17T20:55), with - stale at the end when it is stale. A run at the single radius has no scale in its name.

Properties​

Select a run to see its record in the Properties panel. Nothing in it can be edited.

Analysis Run

PropertyDescription
RunIts number in this project.
AnalysisSlope stability, Block size, Key blocks, Bench as-built, Tunnel as-built, Rockfall inventory or Rockfall trajectories.
ObjectThe mesh or point cloud it ran on.
When (UTC)When it ran.
VRGS BuildThe version of VRGS that ran it.
SeedThe seed of the run's random draws: the probability of failure's, or the rockfall trajectories'.
StatusCurrent; Current (it read no sets); or Stale: changed since - and the names of the sets that changed.
FingerprintA short code of the sets it read, which the stale check compares.

Settings lists the run's settings by their stored names, such as radius and friction_deg. Sets Read lists each set with its number of planes, and its friction angle when it had one of its own. Layers Written lists the layers.

When a run is stale​

A run is stale when a set it read has gained, lost or moved a plane, or its friction angle has changed. A set that has been deleted counts as changed too. The layers of a stale run keep their values; they are not updated or removed. The runs that read the project Sets record them: Slope Stability, Block Size by sets, Key Blocks from the Sets, Tunnel As-built (its set ratings and wedges) and Rockfall Inventory on the later epoch (its release sets). A Bench As-built or Rockfall Trajectories run, or a Key Blocks run from a DFN, reads no sets and is never stale; a run from a DFN does not track the DFN. Re-running a Tunnel As-built run does not make the design surface again.

The status is checked when the run is listed, when you select it, and with Check for Stale Runs.

Context menu​

Right-click the Analysis Runs branch header or a run.

  • Re-run — (a run) Repeat the run exactly as recorded — on the same object, with its own settings, at its scale and with its seed — without a dialog. A new run is recorded; the old one stays. (ID_ANALYSISRUN_RERUN)
  • Check for Stale Runs — Check every run against the sets as they are now and relist them. The messages panel says how many are stale. (ID_ANALYSISRUN_REFRESH)
  • Delete — (a run) Delete the record. The layers it wrote stay on the object. (ID_POPUP_ITEM_DELETE)
Re-run repeats the run as recorded

A Slope Stability run re-runs with the planes it recorded, not the sets as they are now, so a stale run gives the same result again, and the messages panel says so. To use the sets as they are now, run the analysis again from the object's menu.

The object must still be in the project and loaded.

See also​