Difference between revisions of "TUFLOW Message 2550"
Jump to navigation
Jump to search
(Created page with "{{TUFLOW_Message |tuflow_message=WARNING 2550 - <number of > instability timestep corrections recorded at cell [<cell reference>]. |alt_msg=NA |type=WARNING |message_desc=...") |
|||
| (8 intermediate revisions by 2 users not shown) | |||
| Line 3: | Line 3: | ||
|alt_msg=NA | |alt_msg=NA | ||
|type=[[WARNING]] | |type=[[WARNING]] | ||
| − | |message_desc=The | + | |message_desc=The HPC solver has detected instabilities at a cell and a number of timestep corrections have been made in order for the solution to remain stable. There are a variety of reasons that a HPC model may require these corrections:<br> |
* Poor topography data | * Poor topography data | ||
* Inappropriate starting timestep | * Inappropriate starting timestep | ||
* Poorly configured external boundary | * Poorly configured external boundary | ||
* Poorly configured 1D/2D model interface | * Poorly configured 1D/2D model interface | ||
| + | * Starting model as dry and suddenly introducing large volumes of water. | ||
| + | |suggestions=Import the messages layer in to your GIS package, to see the location of the messages. If the last dot point is the cause, either:<br> | ||
| + | *Specify initial water level for the whole model with <font color="blue"><tt>Set IWL</tt></font> command or locally with <font color="blue"><tt>Read GIS IWL</tt></font> command. The wet cells can limit the adaptive timestep through the <u>[[HPC_Adaptive_Timestepping#HPC_2D_Timestep | Shallow Wave Celerity Number]]</u>, and prevent the HPC solver from using big timesteps. | ||
| + | * Use <font color="blue"><tt>Timestep Maximum</tt></font> command to cap the maximum timestep to not get too high. | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | |uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]] | ||
| − | |||
}} | }} | ||
Latest revision as of 09:16, 3 March 2023
TUFLOW Message
WARNING 2550 - <number of > instability timestep corrections recorded at cell [<cell reference>].
Alternate Message
NA
Message Type
WARNING
Description
The HPC solver has detected instabilities at a cell and a number of timestep corrections have been made in order for the solution to remain stable. There are a variety of reasons that a HPC model may require these corrections:
- Poor topography data
- Inappropriate starting timestep
- Poorly configured external boundary
- Poorly configured 1D/2D model interface
- Starting model as dry and suddenly introducing large volumes of water.
Suggestions
Import the messages layer in to your GIS package, to see the location of the messages. If the last dot point is the cause, either:
- Specify initial water level for the whole model with Set IWL command or locally with Read GIS IWL command. The wet cells can limit the adaptive timestep through the Shallow Wave Celerity Number, and prevent the HPC solver from using big timesteps.
- Use Timestep Maximum command to cap the maximum timestep to not get too high.
| Up |
|---|
 2xxx Messages
|