Preparing Avalanchers

Loading engine…

Loading example…

Avalanchers: GPU powered avalanche simulation

View on GitHub

Engine status: Loading WASM...

How the flow works

The app is structured as a step-by-step workflow for exploring a DEM, defining release areas, adjusting the simulation settings, and running the avalanche model in the browser.

  1. Shortcut: pick one of the bundled AvaFrame examples and run it directly.
  2. Select DEM: upload a .gpx, .tif/.tiff, .asc, or a Zarr store directory. GPX tracks download matching elevation tiles in Austria, while Zarr stores let you choose a site from the uploaded store.
  3. Select release areas: either calculate them from the terrain or upload a matching release area raster. For Zarr stores, pick a scenario from the selected site.
  4. Simulation settings: tune the model, friction, particle, and solver parameters.
  5. Run simulation: execute the model and inspect the generated plots.
  6. Save results: download the simulation results as Zarr store. Only works for Chromium based browsers.

Zarr stores are expected to follow the site/scenario layout produced by the data processor, and the browser decodes chunks directly in WASM so the workflow stays fully in the app.

Shortcut
Example cases
Quick start

Run a bundled AvaFrame example with its predefined release areas. This replaces the DEM and release areas selected below.

DEM and release setup

Select terrain and release areas
1
Select DEM

Upload a digital elevation model. Supported: .gpx (downloads elevation tiles covering the track), .tif/.tiff, .asc, or a Zarr store directory.

Click or drag & drop a .gpx, .tif, .asc file or a .zarr folder here
No DEM selected.
2
Select release areas

Either let the model derive release areas from the terrain, or upload your own release area raster.

Derives release areas from the terrain, and from the GPX track when one is loaded.
Click or drag & drop a .gpx, .tif, .asc file or a .zarr folder here
No release areas selected.
3
Simulation settings
4
Run simulation
DEM: No DEM selected.
Release: No release areas selected — the engine will derive them.
Waiting for the engine.
Computation Timer
Data Sources: