TUFLOW Message 3001: Difference between revisions
Jump to navigation
Jump to search
Content deleted Content added
No edit summary |
No edit summary |
||
| (4 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
{{TUFLOW_Message |
{{TUFLOW_Message |
||
|tuflow_message=ERROR 3001 |
|tuflow_message= ERROR 3001 - Cannot open file "a" for writing. |
||
|alt_msg=ERROR 3001 - Cannot open file "a" for reading.<br> |
|||
ERROR 3001 - cannot open log file "a" for writing.<br> |
|||
ERROR 3001 - cannot open timestep history file "a" for writing.<br> |
|||
ERROR 3001 - Log file name "a" is too long.<br> |
|||
|type=[[ERROR]] |
|type=[[ERROR]] |
||
|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. |
|||
|message_desc=TUFLOW is unable to open the file for the requested read/write operation. |
|||
|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> |
|||
|suggestions=For files being opened for writing, check that: |
|||
<br> |
|||
* You have write access to the file location and that the total path+file name is not more than 255 characters. |
|||
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> |
|||
* If the file already exists, check that the file is not locked by another application. |
|||
<tt> |
|||
For files being opened for reading, check that: |
|||
Read GIS Location == gis\2d_loc_L.shp<br> |
|||
* The file exists. |
|||
Grid Size (X,Y) == 1000,1000<br> |
|||
* You have read access for the file location and that the total path+file name is not more than 255 characters. |
|||
Write GIS Domain == ..\check\2d_dom_check.shp<br> |
|||
* The file is not locked by another application. |
|||
STOP |
|||
</tt> |
|||
<br> |
|||
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='' |
|||
|prelink=[[TUFLOW_Message_1991|Message 1991]] |
|||
| ⚫ | |||
|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 |
|---|
 3xxx Messages
|