Convert to TS1 - Revision history

Abrar.Alttahir: /* Options */

2026-03-18T02:06:01Z

Options

← Older revision		Revision as of 12:06, 18 March 2026
Line 25:		Line 25:
	\|"-rows"\|\| The inflow hydrographs are in space or comma delimited files with the data in blocks of one or more rows for each hydrograph. No time data exists in the input files.		\|"-rows"\|\| The inflow hydrographs are in space or comma delimited files with the data in blocks of one or more rows for each hydrograph. No time data exists in the input files.
	\|-		\|-
	\|"-urbs"\|\| Input files are URBS .q files.		\|"-urbs"\|\| Input files are URBS .q files, which must use relative time in hours from the start of the hydrograph.
	\|-		\|-
	\|"-wbnm"\|\| Input files are WBNM _Meta.out files.<br>		\|"-wbnm"\|\| Input files are WBNM _Meta.out files.<br>Only outputs in the .ts1 format. Two files are created:
	Only outputs in the .ts1 format. Two files are created:<br>
	*loc_.ts1 containing the local hydrographs.		*loc_.ts1 containing the local hydrographs.
	*tot_.ts1 containing the total hydrographs.		*tot_.ts1 containing the total hydrographs.

Abrar.Alttahir: /* Introduction */

2026-03-18T02:02:27Z

Introduction

← Older revision		Revision as of 12:02, 18 March 2026
Line 1:		Line 1:
	=Introduction=		=Introduction=
	'''convert_to_ts1.exe''' converts output from hydrologic models to the .ts1 format recognised by TUFLOW. The .ts1 format is a .csv ~~format,~~ ~~but~~ ~~it contains~~ indexing and header information ~~that~~ significantly ~~reduces~~ the time to read ~~the~~ inflow hydrographs ~~into TUFLOW~~. If ~~there are~~ numerous inflow hydrographs, it is strongly recommended ~~to use this format~~.~~<br>~~		'''convert_to_ts1.exe''' converts output from hydrologic models to the .ts1 format recognised by TUFLOW. The .ts1 format is a .csv file that includes indexing and header information, significantly reducing the time required for TUFLOW to read inflow hydrographs. If numerous inflow hydrographs are present, use of this format is strongly recommended.

	Any number of input files (of the same format) can be specified and wildcards (eg. “*.out”) ~~can~~ be used to ~~specify~~ a group of files. The ~~options~~ available are described in the ~~Table~~ below. One input format and one output format switch should be specified, ~~although~~ the ~~default~~ output format is ts1, so this flag ~~can~~ be ~~optionally~~ omitted.~~<br>~~		Any number of input files (of the same format) can be specified, and wildcards (e.g. “*.out”) may be used to select a group of files. The available options are described in the table below. One input format switch and one output format switch should be specified. However, the output format defaults to ts1, so this flag may be omitted.
⚫	For most options, an additional file “_peak_Q.csv” is ~~output~~ ~~providing a summary of~~ the peak flows for each hydrograph. If a group of files is specified, the _peak_Q.csv file ~~is a summary of~~ all files within the group and a second file “_peak_F.csv” ~~contains~~ which file ~~caused~~ the peak flow of all ~~the~~ files. This is useful for determining which storm duration produced the peak flow ~~or is~~ the critical duration event.~~<br>~~

⚫	At ~~present~~ ~~the program~~ supports the hydrology models most commonly used within Australia. ~~Other~~ formats can be ~~built~~ ~~in through~~ supplying example files/formats and ~~any other useful~~ information to [mailto:support@tuflow.com support@tuflow.com].~~<br>~~
		⚫	For most options, an additional file “_peak_Q.csv” is produced, summarising the peak flows for each hydrograph. If a group of files is specified, the _peak_Q.csv file summarises all files within the group, and a second file “_peak_F.csv” identifies which file produced the peak flow across all files. This is useful for determining which storm duration produced the peak flow (i.e. the critical duration event).
⚫	The .ts1 file format is outlined in the following page: [[~~TS1_File_Format \|~~ TS1 File Format]].~~<br>~~

		⚫	The program currently supports the hydrology models most commonly used within Australia. Additional formats can be incorporated by supplying example files/formats and relevant information to [mailto:support@tuflow.com support@tuflow.com].

		⚫	The .ts1 file format is outlined on the following page: [[TS1 File Format]].

	=Options=		=Options=
	'''TABLE 1: convert_to_ts1 Options (Switches)'''		'''TABLE 1: convert_to_ts1 Options (Switches)'''

Emilie Nielsen at 06:26, 20 February 2025

2025-02-20T06:26:50Z

← Older revision		Revision as of 16:26, 20 February 2025
Line 3:		Line 3:
	Any number of input files (of the same format) can be specified and wildcards (eg. “*.out”) can be used to specify a group of files. The options available are described in the Table below. One input format and one output format switch should be specified, although the default output format is ts1, so this flag can be optionally omitted.<br>		Any number of input files (of the same format) can be specified and wildcards (eg. “*.out”) can be used to specify a group of files. The options available are described in the Table below. One input format and one output format switch should be specified, although the default output format is ts1, so this flag can be optionally omitted.<br>
	For most options, an additional file “_peak_Q.csv” is output providing a summary of the peak flows for each hydrograph. If a group of files is specified, the _peak_Q.csv file is a summary of all files within the group and a second file “_peak_F.csv” contains which file caused the peak flow of all the files. This is useful for determining which storm duration produced the peak flow or is the critical duration event.<br>		For most options, an additional file “_peak_Q.csv” is output providing a summary of the peak flows for each hydrograph. If a group of files is specified, the _peak_Q.csv file is a summary of all files within the group and a second file “_peak_F.csv” contains which file caused the peak flow of all the files. This is useful for determining which storm duration produced the peak flow or is the critical duration event.<br>
	At present the program supports the hydrology models most commonly used within Australia. Other formats can be built in through supplying example files/formats and any other useful information to ~~<font~~ ~~color="blue"><u>~~support@tuflow.com~~</u></font>~~.<br>		At present the program supports the hydrology models most commonly used within Australia. Other formats can be built in through supplying example files/formats and any other useful information to [mailto:support@tuflow.com support@tuflow.com].<br>
	The .ts1 file format is outlined in the following page: [[TS1_File_Format \| TS1 File Format]].<br>		The .ts1 file format is outlined in the following page: [[TS1_File_Format \| TS1 File Format]].<br>
	=Options=		=Options=

Emilie Nielsen: /* Examples */

2024-07-22T06:19:57Z

Examples

@@ Line 56: / Line 56: @@
 =Examples=
-outputs two .ts1 files, one the local hydrographs and the other for the total hydrographs in Q100_Meta.out.<br>
+<li>Outputs two .ts1 files, one the local hydrographs and the other for the total hydrographs in Q100_Meta.out.<br>
-<tt>convert_to_ts1.exe -rorb -ts1 -dt5 *.out</tt><br>
+<tt>convert_to_ts1.exe -rorb -ts1 -dt5 *.out</tt>
-<tt>convert_to_ts1.exe -xp -ts1 Q100.int</tt><br>
+<tt>convert_to_ts1.exe -xp -ts1 Q100.int</tt>
 <tt>convert_to_ts1.exe -rafts -mr event_names.txt -e0 -csv my_results.tot</tt><br>
 [[File:RAFTS Storm Control.png | 500px]]<br>
 <br>
 <tt>convert_to_ts1.exe -wbnm -mw -csv Q100.out</tt><br>
 {{Tips Navigation

Pavlina Monhartova: /* Examples */

2020-01-30T23:56:11Z

Examples

← Older revision		Revision as of 09:56, 31 January 2020
Line 61:		Line 61:
	<tt>convert_to_ts1.exe -rorb -ts1 -dt5 *.out</tt><br>		<tt>convert_to_ts1.exe -rorb -ts1 -dt5 *.out</tt><br>
	outputs .ts1 files for every .out file in the folder. A summary of the peak flows can be found in the _peak_Q.csv and _peak_F.csv files.<br>		outputs .ts1 files for every .out file in the folder. A summary of the peak flows can be found in the _peak_Q.csv and _peak_F.csv files.<br>

			<tt>convert_to_ts1.exe -xp -ts1 Q100.int</tt><br>
			outputs .ts1 from .int file.<br>

	<tt>convert_to_ts1.exe -rafts -ts1 Q100.loc Q100.tot</tt><br>		<tt>convert_to_ts1.exe -rafts -ts1 Q100.loc Q100.tot</tt><br>

Pavlina Monhartova at 03:00, 11 June 2019

2019-06-11T03:00:44Z

← Older revision		Revision as of 13:00, 11 June 2019
Line 40:		Line 40:
	\|-		\|-
	\|-		\|-
	\|"-mr event_names.txt"\|\| Multiple Rafts Durations: Read multiple durations from a rafts .loc or .tot file. Must be used in conjunction with the -rafts switch. Events are read directly from the .out file. Names of each event are extracted from the text file event_names.txt (refer example below). Please note: Routing increments must be the same for all storm durations. Multiple file processing using the wildcard feature not yet supported with the -mr switch enabled.		\|"-mr event_names.txt"\|\| Multiple Rafts Durations: Read multiple durations from a rafts .loc or .tot file. Must be used in conjunction with the -rafts switch. Events are read directly from the .out file. Names of each event are extracted from the text file event_names.txt (refer example below). The order of the durations in event_names.txt has to be the same as the order of ticked durations in XPRAFTS. Please note: Routing increments must be the same for all storm durations. Multiple file processing using the wildcard feature not yet supported with the -mr switch enabled.
	\|-		\|-
	!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"\| Miscellaneous Switches		!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"\| Miscellaneous Switches

Pavlina Monhartova: /* Examples */

2019-01-30T03:49:16Z

Examples

← Older revision		Revision as of 13:49, 30 January 2019
Line 69:		Line 69:

	<tt>convert_to_ts1.exe -rafts -mr event_names.txt -e0 -csv my_results.tot</tt><br>		<tt>convert_to_ts1.exe -rafts -mr event_names.txt -e0 -csv my_results.tot</tt><br>
	outputs a separate .csv file for each duration specified within event_names.txt and the result my_results.tot. The order of the durations in event_names.txt is important and has to be the same as the order of ticked durations in XPRAFTS. Example shown below. <br>		outputs a separate .csv file for each duration specified within event_names.txt and the result my_results.tot. The order of the durations in event_names.txt is important and has to be the same as the order of ticked durations in XPRAFTS. Example is shown below. <br>
	[[File:RAFTS Storm Control.png \| 500px]]<br>		[[File:RAFTS Storm Control.png \| 500px]]<br>

Pavlina Monhartova: /* Examples */

2019-01-30T03:48:47Z

Examples

← Older revision		Revision as of 13:48, 30 January 2019
Line 69:		Line 69:

	<tt>convert_to_ts1.exe -rafts -mr event_names.txt -e0 -csv my_results.tot</tt><br>		<tt>convert_to_ts1.exe -rafts -mr event_names.txt -e0 -csv my_results.tot</tt><br>
	outputs a separate .csv file for each duration specified within event_names.txt and the result my_results.tot. The order ~~that~~ ~~you~~ ~~populate~~ event_names.txt is important and has to be the same as the order ticked durations in XPRAFTS. Example shown below. <br>		outputs a separate .csv file for each duration specified within event_names.txt and the result my_results.tot. The order of the durations in event_names.txt is important and has to be the same as the order of ticked durations in XPRAFTS. Example shown below. <br>
	[[File:RAFTS Storm Control.png \| 500px]]<br>		[[File:RAFTS Storm Control.png \| 500px]]<br>

Pavlina Monhartova: /* Examples */

2019-01-30T03:47:28Z

Examples

← Older revision		Revision as of 13:47, 30 January 2019
Line 69:		Line 69:

	<tt>convert_to_ts1.exe -rafts -mr event_names.txt -e0 -csv my_results.tot</tt><br>		<tt>convert_to_ts1.exe -rafts -mr event_names.txt -e0 -csv my_results.tot</tt><br>
	outputs a separate .csv file for each duration specified within event_names.txt and the result my_results.tot. The order that you populate ~~events~~.txt is important ~~with~~ the ~~convention~~ shown below. <br>		outputs a separate .csv file for each duration specified within event_names.txt and the result my_results.tot. The order that you populate event_names.txt is important and has to be the same as the order ticked durations in XPRAFTS. Example shown below. <br>
	[[File:RAFTS Storm Control.png \| 500px]]<br>		[[File:RAFTS Storm Control.png \| 500px]]<br>

Pavlina Monhartova: /* Options */

2018-09-13T04:10:09Z

Options

← Older revision		Revision as of 14:10, 13 September 2018
Line 40:		Line 40:
	\|-		\|-
	\|-		\|-
	\|"-mr event_names.txt"\|\| Multiple Rafts Durations: Read multiple durations from a rafts .loc or .tot file. Must be used in conjunction with the -rafts switch. ~~Event names~~ are read directly from the .out file. Names of each event are extracted from the text file event_names.txt (refer example below). Please note: Multiple file processing using the wildcard feature not yet supported with the -mr switch enabled.		\|"-mr event_names.txt"\|\| Multiple Rafts Durations: Read multiple durations from a rafts .loc or .tot file. Must be used in conjunction with the -rafts switch. Events are read directly from the .out file. Names of each event are extracted from the text file event_names.txt (refer example below). Please note: Routing increments must be the same for all storm durations. Multiple file processing using the wildcard feature not yet supported with the -mr switch enabled.
	\|-		\|-
	!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"\| Miscellaneous Switches		!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"\| Miscellaneous Switches