=Introduction=
A TUFLOW licence is required to run TUFLOW, except when using third party software such as a GIS to prepare input data or view results, or when running TUFLOW demo, tutorial or example models in licence free mode. 

==Lock Types==
TUFLOW Products are licenced via locks, available in two forms; WIBU USB-2 Dongles (hardware lock) and WIBU Software Licenses (software lock). A third form, WIBU Cloud locks, should be available in 2023.

===Current Licence Lock Options===
* '''WIBU Hardware Lock''': WIBU hardware locks are physical dongles (USB-2) that contain TUFLOW licences. Licences are coded onto the dongle and can be moved between computers. WIBU hardware locks are recognised by the 2006-06-BD release onwards. Refer to [[Wibu_Dongles | WIBU Lock Guidance]] for further information.
* '''WIBU Software Lock''': WIBU software locks are coded onto the computer's or server's motherboard, it cannot be transferred to a different host. WIBU software locks are recognised by the 2016-03-AF release onwards. Refer to [[Wibu_Dongles | WIBU Lock Guidance]] for further information.

===Legacy Licence Lock Options===
* '''Softlok Dongle''': As of August 2010 Softlok USB dongles are no longer issued due to the dongle provider not supporting 64-bit. Maintained Softlok dongles may be exchanged for a WIBU dongle for a nominal fee, please contact [mailto:sales@tuflow.com sales@tuflow.com]. For the 2009-07, 2008-08, 2007-07 and 2006-06 releases, the “DB” builds or later will need to be used to recognise a WIBU Codemeter dongle. Refer to [[Softlok_Dongles | Softlok Guidance]] for further information.

==Licence Types==
TUFLOW simulations can be executed using a variety of licence types:
* '''Licence Free Mode''': A licence free mode has been built in TUFLOW. For information outlining the limits associated with the licence free mode, see [[New_User_Guide_Free_Demo_Version | TUFLOW Free DEMO Version Guide]]
* '''Local Licence''': TUFLOW simulations can only be run on the computer hosting the Lock. For installation guidance, see [[New_User_Guide_Local_Licences | Local Licence Installation Guide]]
* '''Network Licence''': The Lock can be hosted on any computer or server. Other computers 'check out' licences from the host computer via a company’s network. There are no regional restrictions associated with Network licences. For installation guidance, see [[New_User_Guide_Network_Licences | Network Licence Installation Guide]]. 
* '''Cloud Licence''': The Lock is hosted on a central WIBU cloud server. Other computers 'check out' licences from the host server over an internet connection. There are no regional restrictions associated with Cloud licences. For installation guidance, see [[New_User_Guide_Cloud_Licences | Cloud Licence Installation Guide]]. 
 

=Frequently Asked Questions (FAQ) =
== Do I require a TUFLOW licence to create TUFLOW inputs and view results from a TUFLOW simulation? ==
No, a TUFLOW licence is only needed to run a TUFLOW .exe file (excluding tutorial, demo and example models or small models eligible for free mode). Running a TUFLOW .exe is required to:
* Process control files (.tcf, etc), check the data inputs and to construct the model using the GIS layers and other inputs. As part of this process any ERROR, WARNING or CHECK messages are issued to help resolve input data conflicts. Check files and GIS layers representing the final model construct are also produced to quality control the model’s inputs.
* To carry out the hydraulic computations provided Step 1 above produces no ERROR messages.
No licence is needed for all other tasks, including:
* Creation and editing of all input files and GIS layers.
* Running GIS plugins such as the QGIS TUFLOW Viewer.
* Running utilities (e.g. asc_to_asc.exe).
* Reviewing check files/layers in GIS.
* Viewing results (e.g. using TUFLOW Viewer in QGIS).
All TUFLOW inputs and outputs use free open formats that are readable and editable by third party software, for example QGIS and Notepad++:
* Download Notepad++ to create and review tabular data: [[NotepadPlusPlus_Tips | Notepad++ installation and tips]].
* Download QGIS: [[QGIS_Tips | QGIS installation and tips]].
* Install the TUFLOW Plugin: [[TUFLOW_QGIS_Plugin | TUFLOW QGIS plugin installation and tips]].
* Use TUFLOW Viewer to review XMDF results: [[TUFLOW_Viewer |TUFLOW Viewer]]. 

==Why is a pre 2010 version of TUFLOW not working?==
In 2010 [[TUFLOW_Licensing#Softlok_Dongles_.28Legacy_Product.29 | Softlok dongles]] were replaced by WIBU dongles. TUFLOW versions earlier than 2010 might be searching for a Softlok licence, however it is likely you have a WIBU licence. The "DB" builds of TUFLOW were created so earlier versions of TUFLOW recognise the new WIBU licences. Please download a "DB" version from the [https://tuflow.com/downloads/tuflow-classichpc-archive/ TUFLOW website].

==How many simulations can be run at the same time?==
The number of licences reflect how many TUFLOW simulations can be run in parallel at any given time. For example, a Local 4 can run 4 simulations at the same time on the one computer. A Network 5 allows up to 5 simulations at any one time across an organisation’s network. If all licences are in use when a TUFLOW simulation starts, the simulation enters a holding pattern until a free licence is available.

 
{{Tips Navigation
|uplink=[[Main_Page| TUFLOW Main Page]]
}}

2018-04-20T01:16:30Z

Mitch3007: Mitch3007 uploaded a new version of File:RAFTS Storm Control.png

Convert to TS1

2018-04-20T01:02:06Z

Mitch3007: /* Options */

=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. 
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. 
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. 
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 support@tuflow.com. 
The .ts1 file format is outlined in the following page: [[TS1_File_Format | TS1 File Format]]. 
=Options=
'''TABLE 1: convert_to_ts1 Options (Switches)'''
{| align="center" class="wikitable"

! Switch
! width=85% | Description
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| Input File Format Switches
|-
|"-rafts"|| Input files are XP-RAFTS .tot and .loc files.
|-
|"-rorb"|| Input files are RORB .out files. The dt option must also be specified.
|-
|"-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.
|-
|"-wbnm"|| Input files are WBNM _Meta.out files. 
Only outputs in the .ts1 format. Two files are created: 
*loc_.ts1 containing the local hydrographs.
*tot_.ts1 containing the total hydrographs.
|-
|"-xp"|| Input files are XP-SWMM .int or .ext files.
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| Output File Format Switches
|-
|"-csv"|| Output file(s) in .csv format.
|-
|"-ts1"|| Output file(s) in .ts1 format (the default).
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| RAFTS and WBNM Specific Switches
|-
|"-mw"|| Multiple WBNM Durations: Read multiple durations from a wbnm *.out file. Must be used in conjunction with the -wbnm switch. Event names are read directly from the *.out file. Please note: Multiple file processing using the * wildcard feature not yet supported with the -mw 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. 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.
[[File:Rafts_Storm_Control.PNG]]
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| Miscellaneous Switches
|-
|"-b"|| 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.
|-
|<nowiki>"-dt<dt>"</nowiki>|| Time increment of RORB hydrographs in minutes. For example, 5 minutes would be specified as dt5.
|-
|"-s0"|| Insert a zero flow before the start of the hydrograph.
|-
|"-e0"|| Insert a zero flow after the end of the hydrograph.
|}

=Examples=
<tt>convert_to_ts1.exe -wbnm -ts1 Q100_Meta.out</tt> 
outputs two .ts1 files, one the local hydrographs and the other for the total hydrographs in Q100_Meta.out. 

<tt>convert_to_ts1.exe -rorb -ts1 -dt5 *.out</tt> 
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. 

<tt>convert_to_ts1.exe -rafts -ts1 Q100*.loc Q100*.tot</tt> 
outputs .ts1 files for every Q100 .loc and .tot file in the folder. A summary of the peak flows can be found in the _peak_Q.csv and _peak_F.csv files. 

<tt>convert_to_ts1.exe -rafts -csv Q100.tot Q050.tot Q100.loc Q050.loc</tt> 
outputs .csv files for the four files specified. 

<tt>convert_to_ts1.exe -rafts -mr event_names.txt -e0 -csv Q100.tot</tt> 
outputs a separate .csv file for each duration specified within event_names.txt and the Q100.tot. The file event_names.txt simply appends text onto the output results to differentiate each run. An example event_names.txt file format has each event on a separate line as per the example below which will output five files: Q100_15min.tot.csv, Q100_30min.tot.csv etc. 
<tt>15min</tt> 
<tt>30min</tt> 
<tt>60min</tt> 
<tt>120min</tt> 
<tt>180min</tt> 

<tt>convert_to_ts1.exe -wbnm -mw -csv Q100.out</tt> 
outputs a separate .csv file for each event within the wbnm output file Q100.out. 

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

Convert to TS1

2018-04-20T01:01:40Z

Mitch3007: /* Options */

=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. 
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. 
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. 
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 support@tuflow.com. 
The .ts1 file format is outlined in the following page: [[TS1_File_Format | TS1 File Format]]. 
=Options=
'''TABLE 1: convert_to_ts1 Options (Switches)'''
{| align="center" class="wikitable"

! Switch
! width=85% | Description
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| Input File Format Switches
|-
|"-rafts"|| Input files are XP-RAFTS .tot and .loc files.
|-
|"-rorb"|| Input files are RORB .out files. The dt option must also be specified.
|-
|"-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.
|-
|"-wbnm"|| Input files are WBNM _Meta.out files. 
Only outputs in the .ts1 format. Two files are created: 
*loc_.ts1 containing the local hydrographs.
*tot_.ts1 containing the total hydrographs.
|-
|"-xp"|| Input files are XP-SWMM .int or .ext files.
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| Output File Format Switches
|-
|"-csv"|| Output file(s) in .csv format.
|-
|"-ts1"|| Output file(s) in .ts1 format (the default).
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| RAFTS and WBNM Specific Switches
|-
|"-mw"|| Multiple WBNM Durations: Read multiple durations from a wbnm *.out file. Must be used in conjunction with the -wbnm switch. Event names are read directly from the *.out file. Please note: Multiple file processing using the * wildcard feature not yet supported with the -mw 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. 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.
[[File:Rafts_Storm_Control.PNG|200px|left]]
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| Miscellaneous Switches
|-
|"-b"|| 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.
|-
|<nowiki>"-dt<dt>"</nowiki>|| Time increment of RORB hydrographs in minutes. For example, 5 minutes would be specified as dt5.
|-
|"-s0"|| Insert a zero flow before the start of the hydrograph.
|-
|"-e0"|| Insert a zero flow after the end of the hydrograph.
|}

=Examples=
<tt>convert_to_ts1.exe -wbnm -ts1 Q100_Meta.out</tt> 
outputs two .ts1 files, one the local hydrographs and the other for the total hydrographs in Q100_Meta.out. 

<tt>convert_to_ts1.exe -rorb -ts1 -dt5 *.out</tt> 
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. 

<tt>convert_to_ts1.exe -rafts -ts1 Q100*.loc Q100*.tot</tt> 
outputs .ts1 files for every Q100 .loc and .tot file in the folder. A summary of the peak flows can be found in the _peak_Q.csv and _peak_F.csv files. 

<tt>convert_to_ts1.exe -rafts -csv Q100.tot Q050.tot Q100.loc Q050.loc</tt> 
outputs .csv files for the four files specified. 

<tt>convert_to_ts1.exe -rafts -mr event_names.txt -e0 -csv Q100.tot</tt> 
outputs a separate .csv file for each duration specified within event_names.txt and the Q100.tot. The file event_names.txt simply appends text onto the output results to differentiate each run. An example event_names.txt file format has each event on a separate line as per the example below which will output five files: Q100_15min.tot.csv, Q100_30min.tot.csv etc. 
<tt>15min</tt> 
<tt>30min</tt> 
<tt>60min</tt> 
<tt>120min</tt> 
<tt>180min</tt> 

<tt>convert_to_ts1.exe -wbnm -mw -csv Q100.out</tt> 
outputs a separate .csv file for each event within the wbnm output file Q100.out. 

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

Convert to TS1

2018-04-20T01:01:08Z

Mitch3007: /* Options */

=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. 
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. 
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. 
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 support@tuflow.com. 
The .ts1 file format is outlined in the following page: [[TS1_File_Format | TS1 File Format]]. 
=Options=
'''TABLE 1: convert_to_ts1 Options (Switches)'''
{| align="center" class="wikitable"

! Switch
! width=85% | Description
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| Input File Format Switches
|-
|"-rafts"|| Input files are XP-RAFTS .tot and .loc files.
|-
|"-rorb"|| Input files are RORB .out files. The dt option must also be specified.
|-
|"-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.
|-
|"-wbnm"|| Input files are WBNM _Meta.out files. 
Only outputs in the .ts1 format. Two files are created: 
*loc_.ts1 containing the local hydrographs.
*tot_.ts1 containing the total hydrographs.
|-
|"-xp"|| Input files are XP-SWMM .int or .ext files.
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| Output File Format Switches
|-
|"-csv"|| Output file(s) in .csv format.
|-
|"-ts1"|| Output file(s) in .ts1 format (the default).
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| RAFTS and WBNM Specific Switches
|-
|"-mw"|| Multiple WBNM Durations: Read multiple durations from a wbnm *.out file. Must be used in conjunction with the -wbnm switch. Event names are read directly from the *.out file. Please note: Multiple file processing using the * wildcard feature not yet supported with the -mw 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. 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.
[[File:RAFTS_Storm_Control.PNG||200px|left]]
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| Miscellaneous Switches
|-
|"-b"|| 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.
|-
|<nowiki>"-dt<dt>"</nowiki>|| Time increment of RORB hydrographs in minutes. For example, 5 minutes would be specified as dt5.
|-
|"-s0"|| Insert a zero flow before the start of the hydrograph.
|-
|"-e0"|| Insert a zero flow after the end of the hydrograph.
|}

=Examples=
<tt>convert_to_ts1.exe -wbnm -ts1 Q100_Meta.out</tt> 
outputs two .ts1 files, one the local hydrographs and the other for the total hydrographs in Q100_Meta.out. 

<tt>convert_to_ts1.exe -rorb -ts1 -dt5 *.out</tt> 
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. 

<tt>convert_to_ts1.exe -rafts -ts1 Q100*.loc Q100*.tot</tt> 
outputs .ts1 files for every Q100 .loc and .tot file in the folder. A summary of the peak flows can be found in the _peak_Q.csv and _peak_F.csv files. 

<tt>convert_to_ts1.exe -rafts -csv Q100.tot Q050.tot Q100.loc Q050.loc</tt> 
outputs .csv files for the four files specified. 

<tt>convert_to_ts1.exe -rafts -mr event_names.txt -e0 -csv Q100.tot</tt> 
outputs a separate .csv file for each duration specified within event_names.txt and the Q100.tot. The file event_names.txt simply appends text onto the output results to differentiate each run. An example event_names.txt file format has each event on a separate line as per the example below which will output five files: Q100_15min.tot.csv, Q100_30min.tot.csv etc. 
<tt>15min</tt> 
<tt>30min</tt> 
<tt>60min</tt> 
<tt>120min</tt> 
<tt>180min</tt> 

<tt>convert_to_ts1.exe -wbnm -mw -csv Q100.out</tt> 
outputs a separate .csv file for each event within the wbnm output file Q100.out. 

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

2018-04-19T03:56:06Z

Mitch3007: /* Examples */

=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. 
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. 
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. 
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 support@tuflow.com. 
The .ts1 file format is outlined in the following page: [[TS1_File_Format | TS1 File Format]]. 
=Options=
'''TABLE 1: convert_to_ts1 Options (Switches)'''
{| align="center" class="wikitable"

! Switch
! width=85% | Description
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| Input File Format Switches
|-
|"-rafts"|| Input files are XP-RAFTS .tot and .loc files.
|-
|"-rorb"|| Input files are RORB .out files. The dt option must also be specified.
|-
|"-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.
|-
|"-wbnm"|| Input files are WBNM _Meta.out files. 
Only outputs in the .ts1 format. Two files are created: 
*loc_.ts1 containing the local hydrographs.
*tot_.ts1 containing the total hydrographs.
|-
|"-xp"|| Input files are XP-SWMM .int or .ext files.
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| Output File Format Switches
|-
|"-csv"|| Output file(s) in .csv format.
|-
|"-ts1"|| Output file(s) in .ts1 format (the default).
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| RAFTS and WBNM Specific Switches
|-
|"-mw"|| Multiple WBNM Durations: Read multiple durations from a wbnm *.out file. Must be used in conjunction with the -wbnm switch. Event names are read directly from the *.out file. Please note: Multiple file processing using the * wildcard feature not yet supported with the -mw 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. 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.
|-
!colspan="2" style="background-color:#005581; font-weight:bold; color:white;"| Miscellaneous Switches
|-
|"-b"|| 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.
|-
|<nowiki>"-dt<dt>"</nowiki>|| Time increment of RORB hydrographs in minutes. For example, 5 minutes would be specified as dt5.
|-
|"-s0"|| Insert a zero flow before the start of the hydrograph.
|-
|"-e0"|| Insert a zero flow after the end of the hydrograph.
|}

=Examples=
<tt>convert_to_ts1.exe -wbnm -ts1 Q100_Meta.out</tt> 
outputs two .ts1 files, one the local hydrographs and the other for the total hydrographs in Q100_Meta.out. 

<tt>convert_to_ts1.exe -rorb -ts1 -dt5 *.out</tt> 
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. 

<tt>convert_to_ts1.exe -rafts -ts1 Q100*.loc Q100*.tot</tt> 
outputs .ts1 files for every Q100 .loc and .tot file in the folder. A summary of the peak flows can be found in the _peak_Q.csv and _peak_F.csv files. 

<tt>convert_to_ts1.exe -rafts -csv Q100.tot Q050.tot Q100.loc Q050.loc</tt> 
outputs .csv files for the four files specified. 

<tt>convert_to_ts1.exe -rafts -mr event_names.txt -e0 -csv Q100.tot</tt> 
outputs a separate .csv file for each duration specified within event_names.txt and the Q100.tot. The file event_names.txt simply appends text onto the output results to differentiate each run. An example event_names.txt file format has each event on a separate line as follows: 
15min 
30min 
60min 
120min 
180min 
This example will output five files: Q100_15min.tot.csv, Q100_30min.tot.csv etc. 
<tt>convert_to_ts1.exe -wbnm -mw -csv Q100.out</tt> 
outputs a separate .csv file for each event within the wbnm output file Q100.out. 

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