Scenarios & Batch Compute

JRunout uses the shared Project → Group → Scenario structure. This lets the same .jws project carry Slope and Rockfall cases while keeping each product's compute and results controls distinct.

What varies by scenario

Each scenario snapshot includes:

• geometry, including placed Rock Sources, Berms, Collectors, Barriers, and Toe Point;
• material regions and External Boundary segment overrides;
• Rockfall simulation method and settings;
• the normal shared geometry/display state.

Rock and Source definition catalogs are project-wide. A definition cannot be deleted while any scenario geometry references it.

Apply settings to several scenarios

Select the required scenarios in the Scenario Explorer, then open Configure → Scenario Settings → Rockfall → Simulation. Applying the form sends the changed Rockfall settings to the selected scenario IDs.

Choose the batch

Rockfall Compute always targets the enabled scenarios in the project:

1. The active scenario is committed to its snapshot.
2. The application visits every enabled scenario and builds its Rockfall input.
3. Scenarios with complete inputs enter the batch; incomplete scenarios are skipped and listed by name with their validation reason.
4. Valid scenarios are solved in sequence. Rocks within each scenario can run in parallel workers.
5. The application returns to the scenario that was active when the batch started and opens Rockfall results.

If no scenarios are enabled, compute does not start. If none of the enabled scenarios has valid Rockfall inputs, the run reports that no valid inputs were found.

Runtime result state

During the current session, each computed scenario can have its own Rockfall run with complete, failed, or stale status. Editing a trajectory input changes the input signature and marks a completed result stale. A Toe Point edit changes presentation only and does not stale the trajectories.

A valid completed run can be stored with its scenario in .jws. Restore rebuilds the current Rockfall input and accepts the saved run only when its input signature still matches. Browser autosave does not include the runtime result map, so autosave-only recovery still requires recomputation. See Files, Autosave & Persistence.

Automatic Berm recompute

The project option Trigger recompute on berm adjustment starts the same enabled-scenario Rockfall batch after a Berm geometry edit. Disable it while making a series of Berm changes, or reduce the enabled scenario set, to avoid unwanted repeated batch runs.