Run TUFLOW From UltraEdit - Revision history

Anne.Kolega: /* TUFLOW */ e.g.

2026-03-30T04:36:25Z

TUFLOW: e.g.

← Older revision		Revision as of 14:36, 30 March 2026
Line 2:		Line 2:
	The majority of users run single TUFLOW simulations from UltraEdit (and use a <u>[[Run TUFLOW From a Batch-file\| Batch-file]]</u> for multiple simulations in succession). The benefits of running TUFLOW from UltraEdit is that it provides an environment where the .tcf and other control files can be edited, simulations started and text file output be viewed. There is also no need to close the .tcf file (or other control and output files) to run TUFLOW.<br>		The majority of users run single TUFLOW simulations from UltraEdit (and use a <u>[[Run TUFLOW From a Batch-file\| Batch-file]]</u> for multiple simulations in succession). The benefits of running TUFLOW from UltraEdit is that it provides an environment where the .tcf and other control files can be edited, simulations started and text file output be viewed. There is also no need to close the .tcf file (or other control and output files) to run TUFLOW.<br>

	The best way to set up TUFLOW to run from UltraEdit is described below. This will initiate TUFLOW in low priority, therefore the simulation does not dominate the computer’s CPU allowing other processes (eg. MapInfo, SMS, Word, etc) to perform as usual. Low priority will not slow down the TUFLOW simulation whilst no other CPU intensive processes are underway. For multiple core computers the "/low" priority switch can be omitted.<br>		The best way to set up TUFLOW to run from UltraEdit is described below. This will initiate TUFLOW in low priority, therefore the simulation does not dominate the computer’s CPU allowing other processes (e.g. MapInfo, SMS, Word, etc) to perform as usual. Low priority will not slow down the TUFLOW simulation whilst no other CPU intensive processes are underway. For multiple core computers the "/low" priority switch can be omitted.<br>

	To set up UltraEdit to run TUFLOW on low priority go to Advanced, Tool Configuration: <br>		To set up UltraEdit to run TUFLOW on low priority go to Advanced, Tool Configuration: <br>

Mitch3007 at 06:52, 3 March 2015

2015-03-03T06:52:23Z

← Older revision		Revision as of 16:52, 3 March 2015
Line 33:		Line 33:
	=BAT FILE=		=BAT FILE=
	If you prefer running TUFLOW from batch files, you can also execute from Ultraedit using a similar method to that above. Please refer the figure below for the required tool configuration inputs:		If you prefer running TUFLOW from batch files, you can also execute from Ultraedit using a similar method to that above. Please refer the figure below for the required tool configuration inputs:
			[[File:UEditBatchRunning.PNG\|border\|600px]]

Mitch3007 at 06:51, 3 March 2015

2015-03-03T06:51:34Z

← Older revision		Revision as of 16:51, 3 March 2015
Line 1:		Line 1:
			=TUFLOW=
	The majority of users run single TUFLOW simulations from UltraEdit (and use a <u>[[Run TUFLOW From a Batch-file\| Batch-file]]</u> for multiple simulations in succession). The benefits of running TUFLOW from UltraEdit is that it provides an environment where the .tcf and other control files can be edited, simulations started and text file output be viewed. There is also no need to close the .tcf file (or other control and output files) to run TUFLOW.<br>		The majority of users run single TUFLOW simulations from UltraEdit (and use a <u>[[Run TUFLOW From a Batch-file\| Batch-file]]</u> for multiple simulations in succession). The benefits of running TUFLOW from UltraEdit is that it provides an environment where the .tcf and other control files can be edited, simulations started and text file output be viewed. There is also no need to close the .tcf file (or other control and output files) to run TUFLOW.<br>

Line 30:		Line 31:
	<br>		<br>
	[[File:UltraEdit Config 05.png\|border\|600px]]		[[File:UltraEdit Config 05.png\|border\|600px]]
			=BAT FILE=
			If you prefer running TUFLOW from batch files, you can also execute from Ultraedit using a similar method to that above. Please refer the figure below for the required tool configuration inputs:

Par at 00:35, 8 August 2013

2013-08-08T00:35:21Z

← Older revision		Revision as of 10:35, 8 August 2013
Line 13:		Line 13:

	The recommended command line argument is:		The recommended command line argument is:

⚫	<pre>start "TUFLOW" /low "C:\TUFLOW\Releases\2010-10\w32\TUFLOW_iSP_w32.exe" "%f"</pre>
	This starts a new window (start) with the title "TUFLOW" ("TUFLOW") with low priority (/low) the next argument is path the the TUFLOW executable and the file argument "%f" uses the currently open file as the TUFLOW control file. Depending on the location of the executable the above command line will need to be modified. For multi-core machines the first three arguments can be omitted, this will start TUFLOW on normal priority.
	<pre>"C:\TUFLOW\Releases\2010-10\w32\TUFLOW_iSP_w32.exe" "%f"</pre>		<pre>"C:\TUFLOW\Releases\2010-10\w32\TUFLOW_iSP_w32.exe" "%f"</pre>
			Depending on the location of the executable the above command line will need to be modified.<br>
			This starts TUFLOW on the default "Normal" priority, which is generally fine for multi-core machines. The priority can be changed in windows task manager (in the "Processes" tab). The priority can also be set in the Ultraedit command line using the following command line, which will start TUFLOW in "Low" priority.
		⚫	<pre>start "TUFLOW" /low "C:\TUFLOW\Releases\2010-10\w32\TUFLOW_iSP_w32.exe" "%f"</pre>

	In the "Options" tab, set the check boxes as follows:		In the "Options" tab, set the check boxes as follows:

tuflow>Par at 04:15, 4 March 2013

2013-03-04T04:15:01Z

← Older revision		Revision as of 14:15, 4 March 2013
Line 14:		Line 14:
	The recommended command line argument is:		The recommended command line argument is:

	<pre>start "TUFLOW" /low "C:\TUFLOW\Releases\2010-10\w32\TUFLOW_iSP_w32.exe" "%f"</pre>		<pre>start "TUFLOW" /low "C:\TUFLOW\Releases\2010-10\w32\TUFLOW_iSP_w32.exe" "%f"</pre>
	This starts a new window (start) with the title "TUFLOW" ("TUFLOW") with low priority (/low) the next argument is path the the TUFLOW executable and the file argument "%f" uses the currently open file as the TUFLOW control file. Depending on the location of the executable the above command line will need to be modified.		This starts a new window (start) with the title "TUFLOW" ("TUFLOW") with low priority (/low) the next argument is path the the TUFLOW executable and the file argument "%f" uses the currently open file as the TUFLOW control file. Depending on the location of the executable the above command line will need to be modified. For multi-core machines the first three arguments can be omitted, this will start TUFLOW on normal priority.
			<pre>"C:\TUFLOW\Releases\2010-10\w32\TUFLOW_iSP_w32.exe" "%f"</pre>

	In the "Options" tab, set the check boxes as follows:		In the "Options" tab, set the check boxes as follows:

tuflow>Par at 22:49, 6 October 2011

2011-10-06T22:49:01Z

← Older revision		Revision as of 08:49, 7 October 2011
Line 1:		Line 1:
	The majority of users run single TUFLOW simulations from UltraEdit (and use a ~~batch~~ ~~file~~ as ~~described~~ in ~~???par~~ for multiple simulations in succession). The benefits of running TUFLOW from UltraEdit is that it provides an environment where the .tcf and other control files can be edited, simulations started and text file output be viewed. There is also no need to close the .tcf file (or other control and output files) to run TUFLOW.<br>		The majority of users run single TUFLOW simulations from UltraEdit (and use a <u>[[Run TUFLOW From a Batch-file\| Batch-file]]</u> for multiple simulations in succession). The benefits of running TUFLOW from UltraEdit is that it provides an environment where the .tcf and other control files can be edited, simulations started and text file output be viewed. There is also no need to close the .tcf file (or other control and output files) to run TUFLOW.<br>

	The best way to set up TUFLOW to run from UltraEdit is described below. This will initiate TUFLOW in low priority, therefore the simulation does not dominate the computer’s CPU allowing other processes (eg. MapInfo, SMS, Word, etc) to perform as usual. Low priority will not slow down the TUFLOW simulation whilst no other CPU intensive processes are underway. For multiple core computers the "/low" priority switch can be omitted.<br>		The best way to set up TUFLOW to run from UltraEdit is described below. This will initiate TUFLOW in low priority, therefore the simulation does not dominate the computer’s CPU allowing other processes (eg. MapInfo, SMS, Word, etc) to perform as usual. Low priority will not slow down the TUFLOW simulation whilst no other CPU intensive processes are underway. For multiple core computers the "/low" priority switch can be omitted.<br>

tuflow>Par: Protected "Run TUFLOW From UltraEdit": High traffic page ([edit=sysop] (indefinite) [move=sysop] (indefinite))

2011-09-29T01:28:48Z

Protected "Run TUFLOW From UltraEdit": High traffic page ([edit=sysop] (indefinite) [move=sysop] (indefinite))

← Older revision		Revision as of 11:28, 29 September 2011
(No difference)

tuflow>Par at 10:42, 20 July 2011

2011-07-20T10:42:46Z

← Older revision		Revision as of 20:42, 20 July 2011
Line 4:		Line 4:

	To set up UltraEdit to run TUFLOW on low priority go to Advanced, Tool Configuration: <br>		To set up UltraEdit to run TUFLOW on low priority go to Advanced, Tool Configuration: <br>
	[[File:UltraEdit Config 01.png]]		[[File:UltraEdit Config 01.png\|border\|600px]]
	<br><br>		<br><br>
	This will open the following dialogue:		This will open the following dialogue:
Line 28:		Line 28:
	This should create an option in the "Tools" menu of Ultraedit to "Run 2010-10-iSP w32" (or the name you gave you the menu item!). To run TUFLOW, simply have the .tcf file open and active in UltraEdit and select "Run 2010-10-iSP w32".		This should create an option in the "Tools" menu of Ultraedit to "Run 2010-10-iSP w32" (or the name you gave you the menu item!). To run TUFLOW, simply have the .tcf file open and active in UltraEdit and select "Run 2010-10-iSP w32".
	<br>		<br>
	[[File:UltraEdit Config 05.png]]		[[File:UltraEdit Config 05.png\|border\|600px]]

tuflow>Par at 10:08, 20 July 2011

2011-07-20T10:08:37Z

← Older revision		Revision as of 20:08, 20 July 2011
Line 26:		Line 26:
	<br><br>		<br><br>

			This should create an option in the "Tools" menu of Ultraedit to "Run 2010-10-iSP w32" (or the name you gave you the menu item!). To run TUFLOW, simply have the .tcf file open and active in UltraEdit and select "Run 2010-10-iSP w32".
	This should create an option
			<br>
			[[File:UltraEdit Config 05.png]]

tuflow>Par at 10:03, 20 July 2011

2011-07-20T10:03:14Z

← Older revision		Revision as of 20:03, 20 July 2011
Line 3:		Line 3:
	The best way to set up TUFLOW to run from UltraEdit is described below. This will initiate TUFLOW in low priority, therefore the simulation does not dominate the computer’s CPU allowing other processes (eg. MapInfo, SMS, Word, etc) to perform as usual. Low priority will not slow down the TUFLOW simulation whilst no other CPU intensive processes are underway. For multiple core computers the "/low" priority switch can be omitted.<br>		The best way to set up TUFLOW to run from UltraEdit is described below. This will initiate TUFLOW in low priority, therefore the simulation does not dominate the computer’s CPU allowing other processes (eg. MapInfo, SMS, Word, etc) to perform as usual. Low priority will not slow down the TUFLOW simulation whilst no other CPU intensive processes are underway. For multiple core computers the "/low" priority switch can be omitted.<br>

	To set up UltraEdit to run TUFLOW on low priority go to Advanced, Tool ~~Configuration…~~ ~~to open:~~		To set up UltraEdit to run TUFLOW on low priority go to Advanced, Tool Configuration: <br>
			[[File:UltraEdit Config 01.png]]
			<br><br>
			This will open the following dialogue:
			<br>
			[[File:UltraEdit Config 02.png]]
			<br><br>
			Under the Command Tab, give the menu item a name. Up to 10 different tools can be configured. "Run 2010-10-iSP w32" has been used to designate the single precision, 32 bit version of the 2010-10 TUFLOW release.

			The recommended command line argument is:

			<pre>start "TUFLOW" /low "C:\TUFLOW\Releases\2010-10\w32\TUFLOW_iSP_w32.exe" "%f"</pre>
			This starts a new window (start) with the title "TUFLOW" ("TUFLOW") with low priority (/low) the next argument is path the the TUFLOW executable and the file argument "%f" uses the currently open file as the TUFLOW control file. Depending on the location of the executable the above command line will need to be modified.

			In the "Options" tab, set the check boxes as follows:
			<br>
			[[File:UltraEdit Config 03.png]]
			<br><br>
			In the "Output" tab, set the check boxes as follows:
			<br>
			[[File:UltraEdit Config 04.png]]
			<br><br>

			This should create an option