TUFLOW Message 3043: Difference between revisions
		
		
		
		Jump to navigation
		Jump to search
		
Content deleted Content added
| No edit summary | No edit summary | ||
| Line 18: | Line 18: | ||
| |prelink=[[TUFLOW_Message_3042|Message 3042]] | |||
| |uplink=[[3xxx_TUFLOW_Messages|3xxx Messages]] | |uplink=[[3xxx_TUFLOW_Messages|3xxx Messages]] | ||
| |nextlink=[[TUFLOW_Message_3044|Message 3044]] | |||
| }} | }} | ||
Latest revision as of 10:18, 3 March 2023
TUFLOW Message 
ERROR 3043 - Model unstable.
Alternate Message 
ERROR 3043 - Too many consecutive failed step attempts.
Message Type 
ERROR
Description 
Either:
- A model running with fixed timestep has encountered NaNs.
- A model running with adaptive timestep has exceeded the maximum step retry count.
- A model running with adaptive timestep has dropped below the minimum allowable timestep.
Suggestions 
- If running a fixed timestep for a reason, consider first running in adaptive timestep mode and then identifying the minimum timestep used in the .hpc.dt.csv file, and then using this value (or slightly less) as the fixed timestep.
- If running with adaptive timestep and the model has exceeded the maximum step retry count, try running with a reduced "HPC Control Number".
- If running with adaptive timestep and the model has dropped below the minimum allowable timestep, consider whether the minimum timestep is reasonable and reduce if necessary.
- Also review the "Minimum dt" map output and messages layer to see if a particular location is responsible, and then review model details in the region.
 
| Up | 
|---|
|  3xxx Messages |