Files, Autosave & Persistence

What the shared .jws project, browser autosave, .jwsr export, and graph CSV preserve for JRunout.

JRunout uses the shared native .jws project file. There is no separate Rockfall project extension in the current release. A single file can contain the project's Slope and Rockfall model inputs.

What `.jws` preserves

The SQLite-based .jws project preserves Rockfall inputs, including:

project-wide Rock and Source definition catalogs;
materials and their Lumped Mass/Rigid Body Rockfall parameters and distributions;
scenario simulation settings;
Rock Sources, Berms, Collectors, Barriers, and Toe Points;
External Boundary segment material overrides;
Berm material/geometry and stored Barrier capacity metadata;
project options such as WebGPU display, automatic Berm recompute, and the JWSplatt Runout solver mode (Exact or Partitioned).

Use File → Save or Save As. Browsers with the File System Access API can write back to the selected file; other browsers download a new .jws file.

Rockfall results in `.jws`

Saving .jws includes each valid, completed Rockfall run whose input signature still matches its scenario. The stored payload includes trajectories, run summary data, Rock geometry required for results, and Collector/Barrier peak impact records. On open, the application rebuilds each scenario's Rockfall input and restores only a matching, valid result payload.

Failed, incomplete, or stale runs are not saved as current results. Playback UI state and prepared WebGPU scenes are also rebuilt rather than stored. If a saved result is absent, malformed, or no longer matches the inputs, run Rockfall again.

Browser autosave

The shared application autosaves the working model to browser storage. The autosave includes Rockfall catalogs, simulation settings, materials, project settings, scenario snapshots, and Rockfall geometry because those are model inputs.

It does not include the Rockfall runtime run map. A reload recovered only from browser autosave can recover the model but not computed Rockfall trajectories or result displays.

Browser autosave is a convenience, not a backup. It is browser- and machine-specific and can be cleared. Save a .jws file for durable storage.

`.jwsr` results export

The shared File → Export Results command creates a .jwsr sidecar that can contain Slope LEM/FEA results, Rockfall results, or both for each scenario. A Rockfall-only result entry does not require a fabricated Slope result. The current interface has no standalone .jwsr import; save .jws to restore completed runs.

Use graph CSV for portable distribution tables and Peak impacts CSV for the retained highest-energy record for each Rock/Collector-or-Barrier pair.

Import boundaries

Input	Rockfall behavior
Native `.jws`	Restores Rockfall catalogs, settings, materials, geometry, overrides, and valid completed runs that still match their scenario inputs.
Slide2 archive	Imports supported Slope model data, not Rockfall-specific definitions, objects, or computed runs.
2D/3D DXF	Provides supported section geometry; 2D import adds it to the current model and preserves catalogs. DXF does not map Rockfall objects or contact settings.

After Slide2 or DXF import, check the resulting External Boundary, create or review Rockfall contact parameters, define Rocks and Rock Sources, place Rockfall objects, and configure the scenario before computing.

Recommended handoff checklist

Before sharing a Rockfall project:

Save the .jws project.
Confirm every relevant scenario is enabled and has valid materials/Rock Sources.
Record the simulation method, Random Seed, and Deviation Cutoff.
Export .jwsr when you need a separate results sidecar.
Export required distribution and impact CSV tables.
Tell the recipient to recompute if a saved result is absent or rejected as inconsistent with the current scenario inputs.