Difference between revisions of "TUFLOW Message 1431"
Jump to navigation
Jump to search
m |
|||
Line 13: | Line 13: | ||
or<br> | or<br> | ||
<font color="blue"><tt>Model Precision </tt></font> <font color="red"><tt>==</tt></font><tt> DOUBLE</tt> | <font color="blue"><tt>Model Precision </tt></font> <font color="red"><tt>==</tt></font><tt> DOUBLE</tt> | ||
− | + | ||
− | |||
− | |||
|prelink=[[TUFLOW_Message_1430|Message 1430]] | |prelink=[[TUFLOW_Message_1430|Message 1430]] | ||
|uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | |uplink=[[1xxx_TUFLOW_Messages|1xxx Messages]] | ||
|nextlink=[[TUFLOW_Message_1432|Message 1432]] | |nextlink=[[TUFLOW_Message_1432|Message 1432]] | ||
}} | }} |
Revision as of 15:48, 5 July 2022
TUFLOW Message
WARNING 1431 - csv XF file precision conflict. Re-reading csv file.
TUFLOW exe Precision = SINGLE
Alternate Message
NA
Message Type
WARNING
Description
The data in the binary (xf) version is not the same precision as the simulation. For example the .xf file has been generated using a single precision version of TUFLOW and the current simulation is running as double precision.
Suggestions
The simulation is reverting to the raw .csv file.
To prevent a simulation from accidentally being started with the wrong version of TUFLOW, the precision of a TUFLOW can be locked using the .tcf command:
Model Precision ==
E.g.
Model Precision == SINGLE
or
Model Precision == DOUBLE
Up |
---|
1xxx Messages |