Timing Contours · BlastScope

STAB +0,+0

FRONT — FIT —

Timing Contours

Load the timing file, and the initiation-time field is built from the hole collars — isochron contours, burden relief in ms per metre, and the movement direction the design implies. Overlay it on the video and the detonation front sweeps the bench as you scrub.

Rock moves broadly perpendicular to the timing contours. That is what makes this a teaching tool: you can see where the timing told the rock to go, and compare it with where it actually went.

Speed

00:00.00 / 00:00.00

Field

View

Video

Live front Holes Measured vectors

Opacity

Contrast

Sens

Frame width m

——

Timing field

no file

Load a timing file with hole ID, X, Y and initiation time. Column names from the common blast design packages are recognised automatically.

The field is interpolated by Delaunay triangulation with linear weights, so every value between holes is a blend of three real detonator times — nothing is invented.

Relief distribution

ms per metre of burden

Designed vs measured movement

Pin four collars, project onto the video, run a deep scan, then press Design vs measured.

The tool compares the direction the timing contours implied at each hole against the direction the rock above it actually moved. Where they disagree, the timing design was not what governed the movement — look for out-of-sequence firing, detonator scatter, a face-burden anomaly, or structure.

Per-hole relief

What the timing is doing

Build the field and this pane reads it back against published practice: how much of the pattern sits inside the 3–15 ms/m envelope where trials find fragmentation improves, how much is confined below 3 ms/m, how much is over-relieved above 25, and the median front speed across the bench.

Each line carries the number it was judged on, so the interpretation can be checked rather than believed.