DAT to DAT - Revision history

Anne.Kolega: /* Difference */

2026-04-02T02:00:24Z

Difference

← Older revision		Revision as of 12:00, 2 April 2026
Line 22:		Line 22:
	A special wet/dry algorithm is used. If water level results are not specified (_h.dat or -typeH), the algorithm opens these files, as well as opens the .2dm file associated with the results files, and uses the water levels and ZH Zpt values (for 2D cells) and elevations at the WLL triangle corners to determine whether a node (corner of an mesh element) is wet or dry. This allows two special values to be output in the event that a node is dry in one results file and wet in the other or vice versa. A value of 99 is used to indicate that a node is dry in the first results file, but is flooded in the second results file, while +99 indicates that the node was wet in the first results file but is dry in the second results file. Specifying '''-nowetdry''' does not carry out a wet/dry check using the water level results.		A special wet/dry algorithm is used. If water level results are not specified (_h.dat or -typeH), the algorithm opens these files, as well as opens the .2dm file associated with the results files, and uses the water levels and ZH Zpt values (for 2D cells) and elevations at the WLL triangle corners to determine whether a node (corner of an mesh element) is wet or dry. This allows two special values to be output in the event that a node is dry in one results file and wet in the other or vice versa. A value of 99 is used to indicate that a node is dry in the first results file, but is flooded in the second results file, while +99 indicates that the node was wet in the first results file but is dry in the second results file. Specifying '''-nowetdry''' does not carry out a wet/dry check using the water level results.
	<br>		<br>
	The -t option can be used to carry out the difference at a particular time (rather than all times). The most common time is to take the difference at the flood peak, i.e.. specify t99999.<br>		The -t option can be used to carry out the difference at a particular time (rather than all times). The most common time is to take the difference at the flood peak, i.e. specify t99999.<br>
	<u>Examples</u><br>		<u>Examples</u><br>
	<li><tt>dat_to_dat.exe -dif results_developed_h.dat results_existing_h.dat</tt></li>		<li><tt>dat_to_dat.exe -dif results_developed_h.dat results_existing_h.dat</tt></li>

Anne.Kolega: /* Difference */ i.e.

2026-04-02T02:00:08Z

Difference: i.e.

← Older revision		Revision as of 12:00, 2 April 2026
Line 22:		Line 22:
	A special wet/dry algorithm is used. If water level results are not specified (_h.dat or -typeH), the algorithm opens these files, as well as opens the .2dm file associated with the results files, and uses the water levels and ZH Zpt values (for 2D cells) and elevations at the WLL triangle corners to determine whether a node (corner of an mesh element) is wet or dry. This allows two special values to be output in the event that a node is dry in one results file and wet in the other or vice versa. A value of 99 is used to indicate that a node is dry in the first results file, but is flooded in the second results file, while +99 indicates that the node was wet in the first results file but is dry in the second results file. Specifying '''-nowetdry''' does not carry out a wet/dry check using the water level results.		A special wet/dry algorithm is used. If water level results are not specified (_h.dat or -typeH), the algorithm opens these files, as well as opens the .2dm file associated with the results files, and uses the water levels and ZH Zpt values (for 2D cells) and elevations at the WLL triangle corners to determine whether a node (corner of an mesh element) is wet or dry. This allows two special values to be output in the event that a node is dry in one results file and wet in the other or vice versa. A value of 99 is used to indicate that a node is dry in the first results file, but is flooded in the second results file, while +99 indicates that the node was wet in the first results file but is dry in the second results file. Specifying '''-nowetdry''' does not carry out a wet/dry check using the water level results.
	<br>		<br>
	The -t option can be used to carry out the difference at a particular time (rather than all times). The most common time is to take the difference at the flood peak, ie. specify t99999.<br>		The -t option can be used to carry out the difference at a particular time (rather than all times). The most common time is to take the difference at the flood peak, i.e.. specify t99999.<br>
	<u>Examples</u><br>		<u>Examples</u><br>
	<li><tt>dat_to_dat.exe -dif results_developed_h.dat results_existing_h.dat</tt></li>		<li><tt>dat_to_dat.exe -dif results_developed_h.dat results_existing_h.dat</tt></li>

Emilie Nielsen: /* Ensight (beta) */

2025-02-20T06:28:11Z

Ensight (beta)

← Older revision		Revision as of 16:28, 20 February 2025
Line 129:		Line 129:
	* Ensight geometry file;		* Ensight geometry file;
	* Ensight results as either per node or per element depending on the input file.		* Ensight results as either per node or per element depending on the input file.
	'''This conversion is in beta stage and any feedback can be sent to support@tuflow.com.<br>		'''This conversion is in beta stage and any feedback can be sent to [mailto:support@tuflow.com support@tuflow.com].<br>
	<u>Examples</u><br>		<u>Examples</u><br>
	<li><tt>dat_to_dat.exe -ensight results1.xmdf</tt></li>		<li><tt>dat_to_dat.exe -ensight results1.xmdf</tt></li>

tuflow>Par at 19:47, 27 October 2012

2012-10-27T19:47:22Z

← Older revision		Revision as of 05:47, 28 October 2012
Line 1:		Line 1:
	<ol>		<ol>
		⚫	=Introduction=
	<br><br>
			This utility performs a variety of operations on the TUFLOW 2D outputs. Valid formats are .xmdf (as of utility version 2012-10-AC) and .dat files. This page is split into two section, utility operations (e.g. maximum, difference etc.) and general options. The general options can be used regardless of operation being performed. The table of contents can be used to jump to a desired operation.
	<font size=125%; color="red">This pages is being updated to include the latest version of the utility which supports .xmdf format resutls</font>
⚫	~~<br><br>~~=Introduction=
	We are currently working on an updated version of the dat_to_dat utility which includes support for the XMDF file type. This page will be updated when this is complete.

	=Operations=		=Operations=
	~~This~~ section ~~of the con table~~ below contains a list of ~~operation~~ the utility can perform~~. Additional input options are included in the next section~~. One of ~~the~~ operations ~~from~~ ~~this~~ ~~section~~ ~~must~~ be ~~included~~ in ~~the~~ ~~input~~ ~~argument~~.		The section below contains a list of the operations that the utility can perform. One of these operations must be specified or the utility will generate an error.

	==Max==		==Max==
Line 22:		Line 20:
	<u>Description</u><br>		<u>Description</u><br>
	This can be used to compare two datasets. If a third files is specified, the third file is used as the output file. The output filename can also be specified with the -out option. The output is the first results minus the second result file.<br>		This can be used to compare two datasets. If a third files is specified, the third file is used as the output file. The output filename can also be specified with the -out option. The output is the first results minus the second result file.<br>
	A special wet/dry algorithm is used. If water level results are not specified (_h.dat or -typeH), the algorithm opens these files, as well as opens the .2dm file associated with the results files, and uses the water levels and ZH Zpt values (for 2D cells) and elevations at the WLL triangle corners to determine whether a node (corner of an mesh element) is wet or dry. This allows two special values to be output in the event that a node is dry in one results file and wet in the other or ~~vica~~ versa. A value of 99 is used to indicate that a node is dry in the first results file, but is flooded in the second ~~resuilts~~ file, while +99 indicates that the node was wet in the first results file but is dry in the second results file. Specifying '''-nowetdry''' does not carry out a wet/dry check using the water level results.		A special wet/dry algorithm is used. If water level results are not specified (_h.dat or -typeH), the algorithm opens these files, as well as opens the .2dm file associated with the results files, and uses the water levels and ZH Zpt values (for 2D cells) and elevations at the WLL triangle corners to determine whether a node (corner of an mesh element) is wet or dry. This allows two special values to be output in the event that a node is dry in one results file and wet in the other or vice versa. A value of 99 is used to indicate that a node is dry in the first results file, but is flooded in the second results file, while +99 indicates that the node was wet in the first results file but is dry in the second results file. Specifying '''-nowetdry''' does not carry out a wet/dry check using the water level results.
	<br>		<br>
	The -t option can be used to carry out the difference at a particular time (rather than all times). The most common time is to take the difference at the flood peak, ie. specify t99999.<br>		The -t option can be used to carry out the difference at a particular time (rather than all times). The most common time is to take the difference at the flood peak, ie. specify t99999.<br>
Line 92:		Line 90:
	Creates an an output file with the specified filename "xmdf_info.txt", which contains information about the contents of the xmdf file.		Creates an an output file with the specified filename "xmdf_info.txt", which contains information about the contents of the xmdf file.

	==~~Velocity~~ Angle==		==Vector Angle==
	'''Input Switch: -va'''<br>		'''Input Switch: -va'''<br>
	<u>Description</u><br>		<u>Description</u><br>
			Outputs the vector direction in degrees relative to north (North = 0°, East = 90°, South = 180°/-180°, West = -90°).

	<u>Examples</u><br>		<u>Examples</u><br>
			<li><tt>dat_to_dat.exe -va results_v.dat</tt></li>

			Outputs the velocity direction for all timesteps in the results_V.dat file.
	==Concatenate==		==Concatenate==
	'''Input Switch: -con'''<br>		'''Input Switch: -con'''<br>
	<u>Description</u><br>		<u>Description</u><br>
			Concatenates (joins) two or more results files into one. Each results file must be from the same 1D/2D mesh.

	<u>Examples</u><br>		<u>Examples</u><br>
			<li><tt>dat_to_dat.exe -con results1_h.dat results2_h.dat results3_h.dat</tt></li>
			Joins the three files into a single .dat file.
			<li><tt>dat_to_dat.exe -con -typeH results1.xmdf results2.xmdf results3.xmdf</tt></li>
			Joins the water level results contained in the .xmdf files into a single

	==Convert==		==Convert==
	'''Input Switch: -conv'''<br>		'''Input Switch: -conv'''<br>
	<u>Description</u><br>		<u>Description</u><br>
			Converts between .dat and .xmdf format results. Not to be confused with -con (concatenate option described above)!

	<u>Examples</u><br>		<u>Examples</u><br>
			<li><tt>dat_to_dat.exe -conv -typeH -t99999 results1.xmdf</tt></li>
			Converts the maximum water level results in the xmdf file into .dat file format.
			<li><tt>dat_to_dat.exe -conv results1.xmdf</tt></li>
			Converts all datasets and times in the .xmdf file into .dat file format. This will output a number of .dat files.
			<li><tt>dat_to_dat.exe -conv results1_h.dat</tt></li>
			Converts all times in the .dat file into xmdf file format.

	==Ensight (beta)==		==Ensight (beta)==
	'''Input Switch: -ensight'''<br>		'''Input Switch: -ensight'''<br>
	<u>Description</u><br>		<u>Description</u><br>
			Converts an .xmdf file (.dat not yet supported) into Ensight Gold format.<br>
			If the input dataset is corner based (standard output) the Ensight results are output as scalar / vector '''per node''' (cell and triangle corners).<br>
			If the result is high resolution (Map Output Format == xmdf high res) then the Ensight results are '''per element'''. For 2D cells this is based on the cell centre output, for triangles (1D water level lines) this is based on an interpolation of the triangle vertices.
			The conversion produces the following output files:<br>
			* Ensight case file;
			* Ensight geometry file;
			* Ensight results as either per node or per element depending on the input file.
			'''This conversion is in beta stage and any feedback can be sent to support@tuflow.com.<br>
		⚫	<u>Examples</u><br>
			<li><tt>dat_to_dat.exe -ensight results1.xmdf</tt></li>
			Converts all datasets in the xmdf file into Ensight format.

⚫	<u>Examples</u><br>
	=General Options=		=General Options=
			==Batch Mode==
	For examples on the current dat_to_dat utility please see section 11.3 of the 2010 TUFLOW manual.
			'''Input Switch: -b'''<br>
			Batch mode suppresses prompt to press Enter at end of processing. Used in .bat files where two or more files are to be processed in succession.
			==Output Filename==
			'''Input Switch: -out "output_filename"'''<br>
			Sets the output filename.

	{{Tips Navigation		{{Tips Navigation
	\|uplink=[[TUFLOW_Utilities \| Back to TUFLOW Utilities]]		\|uplink=[[TUFLOW_Utilities \| Back to TUFLOW Utilities]]

tuflow>Par at 18:46, 27 October 2012

2012-10-27T18:46:56Z

Show changes

tuflow>Par at 03:30, 27 October 2012

2012-10-27T03:30:53Z

@@ Line 1: / Line 1: @@
 <br><br>
-<font size=250%; color="red">This pages is being updated to include the latest version of the utility which supports .xmdf format resutls</font>
+<font size=125%; color="red">This pages is being updated to include the latest version of the utility which supports .xmdf format resutls</font>
 <br><br>=Introduction=
 We are currently working on an updated version of the dat_to_dat utility which includes support for the XMDF file type.  This page will be updated when this is complete.
@@ Line 10: / Line 11: @@
 '''Input Switch: -max'''<br>
 ===Description===
-This can be used to extract the maximum from a number of input datasets.  Any number of input files can be specified.  If a maximum folder exists in an .xmdf file for the type specified, this dataset will be used, uSe -t99999
+This can be used to extract the maximum from a number of input datasets.  Any number of input files can be specified.  If a maximum folder exists in an .xmdf file for the type specified, this dataset will be used, for dat files use -t99999 to use the maximum data in the .dat file.
 ===Examples===
 For examples on the current dat_to_dat utility please see section 11.3 of the 2010 TUFLOW manual.
 {{Tips Navigation
 |uplink=[[TUFLOW_Utilities | Back to TUFLOW Utilities]]
 }}

tuflow>Par at 00:51, 19 October 2012

2012-10-19T00:51:13Z

@@ Line 1: / Line 1: @@
 We are currently working on an updated version of the dat_to_dat utility which includes support for the XMDF file type.  This page will be updated when this is complete.
 =Examples=
 For examples on the current dat_to_dat utility please see section 11.3 of the 2010 TUFLOW manual.

tuflow>Par: Protected "DAT to DAT": High traffic page ([edit=sysop] (indefinite) [move=sysop] (indefinite))

2011-10-06T21:48:45Z

Protected "DAT to DAT": High traffic page ([edit=sysop] (indefinite) [move=sysop] (indefinite))

← Older revision		Revision as of 07:48, 7 October 2011
(No difference)

tuflow>Par at 21:48, 6 October 2011

2011-10-06T21:48:26Z

← Older revision		Revision as of 07:48, 7 October 2011
Line 1:		Line 1:
	=Introduction=		=Introduction=
			We are currently working on an updated version of the dat_to_dat utility which includes support for the XMDF file type. This page will be updated when this is complete.
	TBC
	=Examples=		=Examples=
			For examples on the current dat_to_dat utility please see section 11.3 of the 2010 TUFLOW manual.
	TBC
	{{Tips Navigation		{{Tips Navigation
	\|uplink=[[TUFLOW_Utilities \| Back to TUFLOW Utilities]]		\|uplink=[[TUFLOW_Utilities \| Back to TUFLOW Utilities]]

tuflow>Par at 10:20, 12 September 2011

2011-09-12T10:20:00Z

← Older revision		Revision as of 20:20, 12 September 2011
Line 1:		Line 1:
	=Introduction=		=Introduction=
			TBC
			=Examples=
			TBC
	{{Tips Navigation		{{Tips Navigation
	\|uplink=[[TUFLOW_Utilities \| Back to TUFLOW Utilities]]		\|uplink=[[TUFLOW_Utilities \| Back to TUFLOW Utilities]]