TUFLOW Message 2550: Difference between revisions

Browse history interactively

← Older edit

Content deleted Content added

VisualWikitext

Revision as of 13:17, 1 March 2019 view source Pavlina Monhartova (talk \| contribs) Bureaucrats, Administrators 5,343 edits No edit summary ← Older edit		Latest revision as of 09:16, 3 March 2023 view source Melissa.Moghanloo (talk \| contribs) Bureaucrats, Administrators 2,918 edits No edit summary
(5 intermediate revisions by 2 users not shown)
Line 3: \|alt_msg=NA \|type=[[WARNING]] \|message_desc=The ~~GPU~~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 ~~TUFLOW GPU~~HPC model may require these corrections:<br> * 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:<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. ▲\|suggestions=Import the messages layer in to your GIS package, to see the location of the messages. ~~\|discussion_page=* [[Talk:TUFLOW Message 2550\|Discuss Message 2550]]~~ ~~\|link3=''~~ ~~\|link4=''~~ ~~\|prelink=[[TUFLOW_Message_2522\|Message 2522]]~~ \|uplink=[[2xxx_TUFLOW_Messages\|2xxx Messages]] ~~\|nextlink=[[TUFLOW_Message_2600\|Message 2600]]~~ }}