Difference between revisions of "TUFLOW Message 1701"
(Created page with "{{TUFLOW_Message |tuflow_message=ERROR 1701 - 1D timestep not specified for GPU solver.<br> If using virtual pipes, please include "Virtual Pipe == ON" in the .tcf file. |alt_...") |
|||
| (8 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{TUFLOW_Message | {{TUFLOW_Message | ||
|tuflow_message=ERROR 1701 - 1D timestep not specified for GPU solver.<br> | |tuflow_message=ERROR 1701 - 1D timestep not specified for GPU solver.<br> | ||
| − | If using virtual pipes, please include "Virtual Pipe == ON" in the .tcf file. | + | If using virtual pipes, please include "<font color="black"><tt>Virtual Pipe </tt></font><font color="black"><tt>== </tt></font><font color="black"><tt>ON</tt></font>" in the .tcf file. |
|alt_msg=NA | |alt_msg=NA | ||
|type=[[ERROR]] | |type=[[ERROR]] | ||
| Line 8: | Line 8: | ||
* Boundary using hidden 1D node, such as "QT" type boundary. | * Boundary using hidden 1D node, such as "QT" type boundary. | ||
* 1D commands or ESTRY control file specified in the .tcf. For example in the .tcf, both of the following code blocks turn on 1D. | * 1D commands or ESTRY control file specified in the .tcf. For example in the .tcf, both of the following code blocks turn on 1D. | ||
| − | : <tt>Start 1D Domain<br> | + | : <tt><font color="blue">Start 1D Domain</font><br> |
| − | :: Output Folder == ..\results\1d\<br> | + | :: <font color="blue">Output Folder </font><font color="red">== </font>..\results\1d\<br> |
| − | : End 1D Domain</tt><br> | + | : <font color="blue">End 1D Domain</font></tt><br> |
Or <br> | Or <br> | ||
| − | : <tt>1D Output Folder == ..\results\1d\</tt><br> | + | : <tt><font color="blue">1D Output Folder </font><font color="red">== </font> ..\results\1d\</tt><br> |
| − | |suggestions=If the model has virtual pipes, please include | + | |suggestions=If the model has virtual pipes, please include <tt><font color="blue">Virtual Pipe </font><font color="red">== </font><font color="black">ON</font></tt> in the .tcf to enable this feature.<br> |
| − | Check that all 2D boundaries are compatible with the GPU solver (please refer to the TUFLOW | + | Check that all 2D boundaries are compatible with the GPU solver (please refer to the <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW Manual]</u> for documentation).<br> |
| − | Remove any 1D control file references or 1D commands from the control file. | + | Remove any 1D control file references or 1D commands from the control file. |
| − | + | ||
| − | + | ||
| − | |||
| − | |||
| − | |||
|uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | |uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | ||
| − | |||
}} | }} | ||
Latest revision as of 09:35, 23 September 2024
TUFLOW Message
ERROR 1701 - 1D timestep not specified for GPU solver.
If using virtual pipes, please include "Virtual Pipe == ON" in the .tcf file.
Alternate Message
NA
Message Type
ERROR
Description
A TUFLOW GPU model with linked 1D, has been detected, but no 1D timestep has been specified. Support for linked 1D models in TUFLOW GPU is under development. For TUFLOW build 2016-03-AB onward, TUFLOW has the ability to read an ESTRY control file, but the virtual pipe feature is the only 1D functionality that is currently supported. All of the following, can enable 1D in a TUFLOW GPU model:
- Virtual Pipes
- Boundary using hidden 1D node, such as "QT" type boundary.
- 1D commands or ESTRY control file specified in the .tcf. For example in the .tcf, both of the following code blocks turn on 1D.
- Start 1D Domain
- Output Folder == ..\results\1d\
- Output Folder == ..\results\1d\
- End 1D Domain
Or
- 1D Output Folder == ..\results\1d\
Suggestions
If the model has virtual pipes, please include Virtual Pipe == ON in the .tcf to enable this feature.
Check that all 2D boundaries are compatible with the GPU solver (please refer to the TUFLOW Manual for documentation).
Remove any 1D control file references or 1D commands from the control file.
| Up |
|---|
 1xxx Messages
|