TUFLOW Message 3001 - Revision history

Melissa.Moghanloo at 00:09, 3 March 2023

2023-03-03T00:09:38Z

← Older revision		Revision as of 10:09, 3 March 2023
Line 17:		Line 17:


	\|prelink=[[TUFLOW_Message_2999\|Message 2999]]
	\|uplink=[[3xxx_TUFLOW_Messages\|3xxx Messages]]		\|uplink=[[3xxx_TUFLOW_Messages\|3xxx Messages]]
	\|nextlink=[[TUFLOW_Message_3002\|Message 3002]]
	}}		}}

Emilie Nielsen at 04:48, 2 March 2023

2023-03-02T04:48:44Z

← Older revision		Revision as of 14:48, 2 March 2023
Line 1:		Line 1:
	{{TUFLOW_Message		{{TUFLOW_Message
	\|tuflow_message=ERROR 3001: Cannot open file "a" for writing		\|tuflow_message= ERROR 3001 - Cannot open file "a" for writing.
	~~<br>~~ ERROR 3001: Cannot open file "a" for reading		\|alt_msg=ERROR 3001 - Cannot open file "a" for reading.<br>
	~~\|alt_msg=~~ERROR 3001: cannot open log file "a" for writing		ERROR 3001 - cannot open log file "a" for writing.<br>
	~~<br>~~ ERROR 3001: cannot open timestep history file "a" for writing		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=TUFLOW is unable to open file ~~shown~~.		\|message_desc=TUFLOW is unable to open the file for the requested read/write operation.
	\|suggestions=~~Check~~ to ~~ensure~~ ~~filename~~ is ~~correct~~, ~~and~~ that ~~file is not used by other application.<br>~~		\|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.

Melissa.Moghanloo at 06:43, 1 July 2022

2022-07-01T06:43:08Z

← Older revision		Revision as of 16:43, 1 July 2022
Line 8:		Line 8:
	\|suggestions=Check to ensure filename is correct, and that file is not used by other application.<br>		\|suggestions=Check to ensure filename is correct, and that file is not used by other application.<br>


	\|discussion_page=* [[Talk:TUFLOW Message 3001\|Discuss Message 3001]]
	\|link3=''
	\|link4=''
	\|prelink=[[TUFLOW_Message_2999\|Message 2999]]		\|prelink=[[TUFLOW_Message_2999\|Message 2999]]
	\|uplink=[[3xxx_TUFLOW_Messages\|3xxx Messages]]		\|uplink=[[3xxx_TUFLOW_Messages\|3xxx Messages]]

ShuangGao at 05:30, 17 April 2018

2018-04-17T05:30:19Z

← Older revision		Revision as of 15:30, 17 April 2018
Line 6:		Line 6:
	\|type=[[ERROR]]		\|type=[[ERROR]]
	\|message_desc=TUFLOW is unable to open file shown.		\|message_desc=TUFLOW is unable to open file shown.
	\|suggestions=Check to ensure filename is correct, and that file is ~~closed~~.<br>		\|suggestions=Check to ensure filename is correct, and that file is not used by other application.<br>

	\|discussion_page=* [[Talk:TUFLOW Message 3001\|Discuss Message 3001]]		\|discussion_page=* [[Talk:TUFLOW Message 3001\|Discuss Message 3001]]

ShuangGao at 05:29, 17 April 2018

2018-04-17T05:29:37Z

← Older revision		Revision as of 15:29, 17 April 2018
Line 4:		Line 4:
	\|alt_msg=ERROR 3001: cannot open log file "a" for writing		\|alt_msg=ERROR 3001: cannot open log file "a" for writing
	<br> ERROR 3001: cannot open timestep history file "a" for writing		<br> ERROR 3001: cannot open timestep history file "a" for writing
	\|type=[[ERROR]] ]		\|type=[[ERROR]]
			\|message_desc=TUFLOW is unable to open file shown.
	\|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.
			\|suggestions=Check to ensure filename is correct, and that file is closed.<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>

	<br>
		⚫	\|discussion_page=* [[Talk:TUFLOW Message 3001\|Discuss Message 3001]]
	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>
	<tt>
	Read GIS Location == gis\2d_loc_L.shp<br>
	Grid Size (X,Y) == 1000,1000<br>
	Write GIS Domain == ..\check\2d_dom_check.shp<br>
	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=''		\|link3=''
	\|link4=''		\|link4=''
	\|prelink=[[~~TUFLOW_Message_1991~~\|Message ~~1991~~]]		\|prelink=[[TUFLOW_Message_2999\|Message 2999]]
	\|uplink=[[~~2xxx_TUFLOW_Messages~~\|~~2xxx~~ Messages]]		\|uplink=[[3xxx_TUFLOW_Messages\|3xxx Messages]]
	\|nextlink=[[~~TUFLOW_Message_2002~~\|Message ~~2002~~]]		\|nextlink=[[TUFLOW_Message_3002\|Message 3002]]
	}}		}}

ShuangGao at 05:14, 17 April 2018

2018-04-17T05:14:36Z

← Older revision		Revision as of 15:14, 17 April 2018
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
			<br> ERROR 3001: Cannot open file "a" for reading
	\|alt_msg=WARNING 2001 - ",a," "object" at ",a,",",a," is outside 2D model domain
			\|alt_msg=ERROR 3001: cannot open log file "a" for writing
⚫	\|type=[[ERROR]] ~~<br> [[WARNING]~~]
			<br> ERROR 3001: cannot open timestep history file "a" for writing
		⚫	\|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=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.
	\|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=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>

ShuangGao: 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..."

2018-04-17T05:01:48Z

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..."

New page

{{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=[[ERROR]] [[WARNING]]
|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.
|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). 
 
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: 
<tt>
Read GIS Location == gis\2d_loc_L.shp 
Grid Size (X,Y) == 1000,1000 
Write GIS Domain == ..\check\2d_dom_check.shp 
STOP
</tt>
 
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]]
|uplink=[[2xxx_TUFLOW_Messages|2xxx Messages]]
|nextlink=[[TUFLOW_Message_2002|Message 2002]]
}}