Warnings (Water Overlay)

Redirect to:

• Warning and recommendations (Water Overlay)

---

Calculation warnings

When the Water Overlay is selected in the Editor, a number of warnings may appear in the right panel when a calculation is performed.

Calculation was cancelled

The calculation did not run to completion, because it was cancelled by the user. Depending on the calculation being performed, partial results may be available.

Calc too long forced timeout

The calculation exceeded the allowed calculation time. During business hours (9-17, GMT+1, during weekdays), there is a maximum calculation time of 1 hour. If during business hours a calculation has been calculating for an hour, the calculation times out automatically. Depending on the calculation being performed, partial results may be available.

Error in GPU calculation

During the calculation, an unknown error has occurred. This may be due to an unexpected configuration of the specific calculation, or an internal error in the calculation infrastructure. Please contact support with a description of the calculation and its related settings to further investigate the issue.

Insufficient memory

An overlay's simulation model comprises numerous data arrays, such as fluxes and water levels in a water simulation, which are processed on the GPUs. When this error arises, it indicates that the total number of data arrays required for the simulation exceeds the available GPU memory (note that GPUs have their own dedicated memory, distinct from the general RAM used by the CPU). This error is constrained by hardware limitations and can only be addressed by reducing the dataset size. There are several solutions:

• The first approach is to increase the grid cell size, as fewer cells will result in reduced memory usage.
• The second option involves simplifying the simulation by using fewer result types. For instance, result types like AVG_DIRECTION, FLOOD_RISE_RATE, or TRACERS in the water model generate additional arrays.
• Disabling model options like groundwater in a Water simulation can also help decrease the data volume.
• Lastly, the number of timeframes does not affect memory usage. Timeframes are snapshots taken during the simulation and sent back to the Project on the CPU, but they do not require additional data arrays on the GPU.

Prequel

When a Grid Overlay encounters an error, its results may not be valid. Any other Grid Overlay which uses that first Grid Overlay as a prequel will warn about that error in one of the prequels taking place. Subsequent Grid Overlays relying on that one will also report the error.

Limited cycles. Inaccurate results

It took too many calculation cycles to perform the calculation. The maximum amount of calculation cycles is 2147483647. The amount of cycles is dictated by the complexity, size, and duration of the simulation. More water with a higher maximum impulse across a larger calculation area over a longer period of time requires more computational cycles to accurately compute.

Invalid constructions

One or more constructions used in the calculation are invalid. They may be incorrectly configured, or interfered with by the presence of other constructions. More information for the individual constructions with errors can be found in the Water Overlay Wizard, or under the Construction warnings header.

Large cell size. Inacurate results

The grid cell size has been configured as greater than 4 meters. This means water may have difficulty flowing into alleys or through fair-sized waterways, and other accuracy-related artifacts may present themselves in the calculation results.

Heightmap resolution is too low

The resolution of the heightmap is lower than the grid cell resolution, meaning that even though more accurate results might be expected, it's not possible to refine the detail of water flow to the configured accuracy. The only way to enhance the height map accuracy is to load in a new Project with a more detailed DEM resolution.

Feature warnings

Breach: Breach uses an empty Input Area, which will have no effect

The Breach is properly connected to an input area, but the input area is not a polygon in the 3D world.

Breach: Breach has an invalid Input Area

The Breach refers to an Area as Input Area, but the referred Area is not configured to be an Input Area.