Warnings (Water Overlay): Difference between revisions
m (→Water Area) |
m (→Water Area) |
||
| Line 43: | Line 43: | ||
====The water level is much lower than the average land height==== | ====The water level is much lower than the average land height==== | ||
The water level is much lower than the average land height, which likely means an improper value has been imported as Water Level. The effect in the model is that waterways will be initialized with excessively low water levels, if they are even deep enough to contain any water | The water level is much lower than the average land height, which likely means an improper value has been imported as Water Level. The effect in the model is that waterways will be initialized with excessively low water levels, if they are even deep enough to contain any water. | ||
'''To resolve:''' Ensure that the configured [[Water level (Water Overlay)|water level]] is not set to a placeholder value. Note that if the water level is indeed correct but the warning persists, the warning can be ignored. | '''To resolve:''' Ensure that the configured [[Water level (Water Overlay)|water level]] is not set to a placeholder value. Note that if the water level is indeed correct but the warning persists, the warning can be ignored. | ||
Revision as of 10:37, 11 June 2020
Redirect to:
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.
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.
To resolve: Reduce the complexity of the calculation. Prioritize reducing the calculation time, and consider running the Water Overlay calculation in low impulse mode.
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.
To resolve: Open the Water Overlay configuration wizard, continue to the step of the constructions, and investigate the errors of constructions on an individual basis.
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.
To resolve: Reduce the grid cell size.
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.
To resolve: As a stop-gap measure, increase the grid cell size. For a more permanent resolution, recreate the project with a more detailed DEM resolution.
Construction warnings
Feature warnings
For individual hydrological features, warnings may be presented when they are improperly configured.
Water Area
Water Level Areas are checked to see if their configured water level is realistic.
The water level is much higher than the average land height
The water level is much higher than the average land height, which likely means an improper value has been imported as Water Level. The effect in the model is that water will be initialized in waterways as a high block exceeding the average surface height, so the simulation will start with a sudden flood emenating from the waterways.
To resolve: Ensure that the configured water level is not set to a placeholder value. Note that if the water level is indeed correct but the warning persists, the warning can be ignored.
The water level is much lower than the average land height
The water level is much lower than the average land height, which likely means an improper value has been imported as Water Level. The effect in the model is that waterways will be initialized with excessively low water levels, if they are even deep enough to contain any water.
To resolve: Ensure that the configured water level is not set to a placeholder value. Note that if the water level is indeed correct but the warning persists, the warning can be ignored.
Inundation Area
Inundation Areas are checked to see if their configured inundation level is realistic.
The inundation level is much higher than the average land height
The water level is much higher than the average land height, which likely means an improper value has been imported as Inundation Level. The effect in the model is that water will be initialized on the surface many meters high, which is an unrealistic starting situation. Check your data for placeholder values.
The inundation level is much lower than the average land height
The water level is much lower than the average land height, which likely means an improper value has been imported as Inundation Level. The effect in the model is that no water will actually be placed on the surface, except in points where the terrain dips far below the average height (without being a waterway). Check your data for placeholder values.
Sewer Area
Sewer Areas are checked for physically impossible models.
Sewer Storage is negative, which is not allowed
The Sewer Area is configured to have a negative amount of sewer storage. All sewer storage must be strictly positive and non-zero. Check your sewer data and adjust the Sewer Storage values where possible.
Sewer Pump Speed is negative, which is not allowed
The Sewer Area is configured to have a negative sewer pump speed. This would mean water is structurally pumped into the sewer. Sewer pump speeds must be 0 or positive. Check your sewer data and adjust the Sewer Pump Speed values where possible.
Aquifer
Aquifers are checked for physically impossible models.
Aquifer does not have a positive non-zero KD value.
The Sewer Area is configured to have a negative hydraulic conductivity, which directly dictates maximum flow speed. The hydraulic conductivity must be positive and no-zero, otherwise the underground flow speed would be similarly negative or zero. Check your aquifer data and adjust the aquifer kd where possible.
Breach
Sewer Areas are checked for improper configurations for water inflow.
The Breach is properly connected to an input area, but another Breach is connected to the same input area. Make sure every breach using an input area has its own input area.
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 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.
Breach uses an external area as input, but it is not allowed to be empty
The Breach does not have a configured Input Area, and therefor defaults to using an external area. However, the external area's size is no a non-zero positive integer.