Difference between revisions of "TUFLOW Message 2019"

From Tuflow
Jump to navigation Jump to search
 
(One intermediate revision by one other user not shown)
Line 4: Line 4:
 
|type=[[ERROR]]
 
|type=[[ERROR]]
 
|message_desc=An error occurred reading 2D BC data whilst allocating memory requirements.  This would usually mean that the format of the file being read is incorrect (for example, incorrect number or types of attributes in a 2d_bc layer), or the file has been corrupted.
 
|message_desc=An error occurred reading 2D BC data whilst allocating memory requirements.  This would usually mean that the format of the file being read is incorrect (for example, incorrect number or types of attributes in a 2d_bc layer), or the file has been corrupted.
|suggestions=Check the GIS attributes match those described in Table 4.33 2D Boundary Conditions (2d_bc) Attribute Descriptions of TUFLOW manual (Table reference for 2010 version), or in empty file: 2d_bc_empty. If problem still persists try re-exporting file (in case of corruption).
+
|suggestions=Check the GIS attributes match those described in the <u>[https://docs.tuflow.com/classic-hpc/manual/latest/ TUFLOW Manual]</u>, or in empty file: 2d_bc_empty. If problem still persists try re-exporting file (in case of corruption).
 +
 
  
|prelink=[[TUFLOW_Message_2018|Message 2018]]
 
 
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
 
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
|nextlink=[[TUFLOW_Message_2020|Message 2020]]
 
 
}}
 
}}

Latest revision as of 09:45, 23 September 2024

TUFLOW Message
ERROR 2019 - Reading 2D BC data while allocating memory.

Alternate Message
NA

Message Type
ERROR

Description
An error occurred reading 2D BC data whilst allocating memory requirements. This would usually mean that the format of the file being read is incorrect (for example, incorrect number or types of attributes in a 2d_bc layer), or the file has been corrupted.

Suggestions
Check the GIS attributes match those described in the TUFLOW Manual, or in empty file: 2d_bc_empty. If problem still persists try re-exporting file (in case of corruption).


Up
Go-up.png 2xxx Messages