Configuring Runs

A scenario brings together your inputs and its run settings into a runnable configuration. Everything on this page lives in the scenario settings pane, in the Hydraulics tab of the project panel.

Run settings

Setting	Description	Notes
Name	What the scenario is called in the rail	Required before a build
Base mesh size (m)	Target triangle edge length, in metres, away from any mesh region	Required, greater than zero
Duration	How long the simulation covers, chosen as Hours plus Minutes	Required, greater than zero

There is no hardware to choose. Hydrata picks the compute target for the Run, and the selector for it is shown only to Hydrata staff. See Cloud ANUGA for what the platform runs on.

Base mesh size is a length, not an area. Halving it roughly quadruples the triangle count, and the triangle count is what drives build time, run time and price, so change it in steps and watch what the build reports.

Duration is entered as two dropdowns, Hours and Minutes. There is no seconds box.

Note

Two settings that older versions of this page listed are no longer scenario settings. Simplify Mesh was removed with the adaptive mesher, and a package that still carries the key is ignored rather than rejected. Model Start is not something you type: it is derived for each Run as the earliest first timestamp across the time series that Run uses, so an absolute-time inflow and rainfall line up with each other. A Run with no time series at all falls back to the epoch.

Required and optional inputs

The pane separates Required from Optional inputs, and a build refuses to start until the required ones are set. Hydrata tells you which one is missing rather than failing later: a scenario must be selected and named, and it needs a terrain, a boundary, a base mesh size greater than zero, a duration greater than zero, and either an inflow or a rainfall.

Selecting Inputs covers each input and what happens when you leave an optional one out.

How to build and run

1. Open a project and open the Hydraulics tab
2. Select a scenario, or create one with New Scenario
3. Choose the inputs
4. Set the base mesh size and the duration
5. Click Build and Run

Build and Run builds the mesh and package and dispatches the Run as soon as the build lands. Build stops after the package, and Run runs a package you already built. Progress is reported on the scenario as a status pill, and a Run in progress can be cancelled.

Runs are quoted and charged against your account, with a free allowance per day. The per-run price is shown on the scenario once a build exists, because the quote is computed from the built mesh, so Build and Run does not pause on it. Build first if you want the quote before the Run starts. The Plans page carries the current allowances and prices, and the Billing tab of the Account panel shows your balance and recent activity.

What the build tells you

Before a build, the scenario shows an estimated triangle count for the current settings. After a build it shows the count actually built alongside that estimate, which is the fastest way to find out that a mesh region or a structure changed the mesh more than you expected.

Hints on the pane point at whatever is driving the mesh cost, for example mesh regions rather than the base mesh size, so you tune the setting that is actually responsible. See Mesh Regions for how local refinement is applied.

Outputs

After a successful Run, the following outputs are generated:

Output	Format	Description
SWW file	NetCDF	Full time-series of depth, velocity, stage
Depth max	GeoTIFF	Maximum water depth at each point
Velocity max	GeoTIFF	Maximum flow velocity at each point
Depth-integrated velocity max	GeoTIFF	Maximum momentum at each point
Stage max	GeoTIFF	Maximum water surface elevation

Outputs are viewable in the map interface, can be played back over time, and can be downloaded for use in GIS software. See Exporting Results.