Difference between revisions of "TUFLOW Message 3001"

From Tuflow
Jump to navigation Jump to search
(Created page with "{{TUFLOW_Message |tuflow_message=ERROR 2001 - GIS Object is outside 2D model domain |alt_msg=WARNING 2001 - ",a," "object" at ",a,",",a," is outside 2D model domain |type=ER...")
 
 
(5 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{{TUFLOW_Message
 
{{TUFLOW_Message
−
|tuflow_message=ERROR 2001 - GIS Object is outside 2D model domain
+
|tuflow_message= ERROR 3001 - Cannot open file "a" for writing.
−
|alt_msg=WARNING 2001 - ",a," "object" at ",a,",",a," is outside 2D model domain
+
|alt_msg=ERROR 3001 - Cannot open file "a" for reading.<br>
−
|type=[[ERROR]] <br> [[WARNING]]
+
ERROR 3001 - cannot open log file "a" for writing.<br>
−
|message_desc=An object is located outside the 2D domain that it is assigned to.  The <tt>Check Inside Grid == </tt> command controls whether this message is an ERROR, WARNING or not given.
+
ERROR 3001 - cannot open timestep history file "a" for writing.<br>
−
|suggestions=Ensure the 2D model domain has sufficient extent or remove object from input files.  The messages layer contains the location of the object outside the model domain in GIS format (.mif or .shp). <br>
+
ERROR 3001 - Log file name "a" is too long.<br>
−
<br>
+
|type=[[ERROR]]  
−
The TUFLOW domain is written in the check files ([[Check_Files_2d_dom | _dom_check.mif or _dom_check_R.shp]]).  The domain extent can also be written by including the <tt>Write GIS Domain == <filename></tt> command in the geometry control file. For example:<br>
+
|message_desc=TUFLOW is unable to open the file for the requested read/write operation.
−
<tt>
+
|suggestions=For files being opened for writing, check that:
−
Read GIS Location == gis\2d_loc_L.shp<br>
+
* You have write access to the file location and that the total path+file name is not more than 255 characters.
−
Grid Size (X,Y) == 1000,1000<br>
+
* If the file already exists, check that the file is not locked by another application.
−
Write GIS Domain == ..\check\2d_dom_check.shp<br>
+
For files being opened for reading, check that:
−
STOP
+
* The file exists.
−
</tt>
+
* You have read access for the file location and that the total path+file name is not more than 255 characters.
−
<br>
+
* The file is not locked by another application.
−
The '''_messages.mif''' or '''_messages_P.shp''' layer in the log folder contains the locations of the offending boundary objects.  Review the '''_dom_check''' file and the messages layer to ensure that all 2d_bc objects are within the model domain.  Check also that the projection of the boundary layer is the same as the TUFLOW model projection.
+
 
−
|discussion_page=* [[Talk:TUFLOW Message 2001|Discuss Message 2001]]
+
 
−
|link3=''
+
 
−
|link4=''
+
|uplink=[[3xxx_TUFLOW_Messages|3xxx Messages]]
−
|prelink=[[TUFLOW_Message_1991|Message 1991]]
 
−
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
 
−
|nextlink=[[TUFLOW_Message_2002|Message 2002]]
 
 
}}
 
}}

Latest revision as of 10:09, 3 March 2023

TUFLOW Message
ERROR 3001 - Cannot open file "a" for writing.

Alternate Message
ERROR 3001 - Cannot open file "a" for reading.
ERROR 3001 - cannot open log file "a" for writing.
ERROR 3001 - cannot open timestep history file "a" for writing.
ERROR 3001 - Log file name "a" is too long.

Message Type
ERROR

Description
TUFLOW is unable to open the file for the requested read/write operation.

Suggestions
For files being opened for writing, check that:

  • You have write access to the file location and that the total path+file name is not more than 255 characters.
  • If the file already exists, check that the file is not locked by another application.

For files being opened for reading, check that:

  • The file exists.
  • You have read access for the file location and that the total path+file name is not more than 255 characters.
  • The file is not locked by another application.


Up
Go-up.png 3xxx Messages
Retrieved from "https://wiki.tuflow.com/w/index.php?title=TUFLOW_Message_3001&oldid=32490"