TRIM Tips - Revision history

Emilie Nielsen at 01:52, 8 January 2026

2026-01-08T01:52:16Z

← Older revision		Revision as of 11:52, 8 January 2026
Line 46:		Line 46:

	[[File:reporting.gif\|frame\|none]]		[[File:reporting.gif\|frame\|none]]


			{{Tips Navigation
			\|uplink=[[Running_TUFLOW\| Back to Running TUFLOW]]
			}}

Emilie Nielsen at 00:34, 18 July 2024

2024-07-18T00:34:46Z

Chris Ryan at 20:41, 21 November 2012

2012-11-21T20:41:20Z

← Older revision		Revision as of 06:41, 22 November 2012
Line 21:		Line 21:
	==Increasing the speed of your TUFLOW modelling==		==Increasing the speed of your TUFLOW modelling==

	We all want to get our TUFLOW simulations complete ASAP. TRIM is designed to aid in this process by clever queue management ensuring all available licenses are in use at all time. However, there are also ~~a couple of~~ ways to speed up individual simulations. These include		We all want to get our TUFLOW simulations complete ASAP. TRIM is designed to aid in this process by clever queue management ensuring all available licenses are in use at all time. However, there are also some ways to speed up individual simulations. These include

	===Auto Stop===		===Auto Stop===

	TRIM can automatically stop your simulation once it has safely passed the peak. This can save loads of time. For more information refer [http://www.csse.com.au/trim_online_help/index.php?trim_autostop.htm here]. Note, if your modelling PC is unattended, you may need to apply the fix at the bottom of the [http://www.csse.com.au/trim_online_help/index.php?trim_autostop.htm page] to get Auto Stop to work properly.		TRIM can automatically stop your simulation once it has safely passed the peak. This can save loads of time. For more information refer [http://www.csse.com.au/trim_online_help/index.php?trim_autostop.htm here]. Note, if your modelling PC is unattended, you may need to apply the fix at the bottom of the [http://www.csse.com.au/trim_online_help/index.php?trim_autostop.htm page] to get Auto Stop to work properly.

	===Hide Windows===

	TRIM has an option to suppress the TUFLOW console display. Besides avoiding hijacking the screen when new windows are launched, we are investigating if this can improve performance.

	==Automation of Post Processing==		==Automation of Post Processing==

Chris Ryan at 05:36, 21 November 2012

2012-11-21T05:36:12Z

← Older revision		Revision as of 15:36, 21 November 2012
Line 29:		Line 29:
	===Hide Windows===		===Hide Windows===

	TRIM has an option to suppress the TUFLOW console display. Besides avoiding hijacking the screen when new windows are launched, we are investigating if this can improve performance ~~(we have observed up to a 10% speed increase based on the tutorial model)~~.		TRIM has an option to suppress the TUFLOW console display. Besides avoiding hijacking the screen when new windows are launched, we are investigating if this can improve performance.

	==Automation of Post Processing==		==Automation of Post Processing==

Chris Ryan at 05:16, 21 November 2012

2012-11-21T05:16:14Z

← Older revision		Revision as of 15:16, 21 November 2012
Line 47:		Line 47:
	==Reporting==		==Reporting==

	~~The~~ reporting allows you to ~~report~~ at ~~various~~ levels ~~within~~ ~~simulation~~ ~~names~~ if your naming convention ~~uses~~ underscores '_' to distinguish between events and scenarios		TRIM includes some reporting features that allows you to examine the breakdown of modelling hours between, models, specific events, users or even TUFLOW versions. Further levels of details are available via the Chart Level component but this relies on your naming convention using underscores '_' to distinguish between events and scenarios.

	[[File:reporting.gif\|frame\|none]]		[[File:reporting.gif\|frame\|none]]

Chris Ryan at 05:13, 21 November 2012

2012-11-21T05:13:29Z

← Older revision		Revision as of 15:13, 21 November 2012
Line 1:		Line 1:
	=Overview=		=Overview=
			TUFLOW Run Interface Manager (TRIM) is a product developed by [http://www.csse.com.au Catchment Simulation Solutions] to help manage your TUFLOW model runs more efficiently. It allows you to manage a large queue of simulations with any designated number of simulations running simultaneously. This ensures the fastest job completion and maximum license utilisation.
	<br>

⚫	~~TUFLOW Run Interface Manager (TRIM) is a TUFLOW simulation manager developed by [http://www.csse.com.au Catchment Simulation Solutions].~~ Detailed documentation can be found at: [http://www.csse.com.au/trim_online_help http://www.csse.com.au/trim_online_help]
			*On the fly charting of flows, errors and wet cell counts.
			*Simple display of simulation progress and expected end times.
			*Rapid notification of unstable or incomplete simulations by email or Skype.
			*Complete automation of common post processing tasks.
			*Configure multiple simulations from event/scenario models via an intuitive GUI
			*Detailed reporting on modelling time broken up by project, date, user or other criteria.

		⚫	Detailed documentation can be found at: [http://www.csse.com.au/trim_online_help http://www.csse.com.au/trim_online_help]

			TRIM is free for a one simultaneous simulation version. For more information on commercial license options, please vist [http://www.csse.com.au/trim this page].

	[[File:TRIM_Image.gif\|frame\|none]]		[[File:TRIM_Image.gif\|frame\|none]]

Chris Ryan at 05:09, 21 November 2012

2012-11-21T05:09:38Z

← Older revision		Revision as of 15:09, 21 November 2012
Line 32:		Line 32:

	The power of automated post processing is at its best when used with Events and Scenarios models. These can be configured using the [http://www.csse.com.au/trim_online_help/index.php?events_and_scenarios.htm Events and Scenarios GUI]. The table icon button allows you to automatically add all combinations of ARIs and durations and automatically group them into suitable groupings for dat_to_dat processing. There are options available via right click to duplicate entire groups with a different scenario further streamlining your modelling.		The power of automated post processing is at its best when used with Events and Scenarios models. These can be configured using the [http://www.csse.com.au/trim_online_help/index.php?events_and_scenarios.htm Events and Scenarios GUI]. The table icon button allows you to automatically add all combinations of ARIs and durations and automatically group them into suitable groupings for dat_to_dat processing. There are options available via right click to duplicate entire groups with a different scenario further streamlining your modelling.

			[[File:events.gif\|frame\|none]]

	==Reporting==		==Reporting==

	The reporting allows you to report at various levels within simulation names if your naming convention uses underscores '_' to distinguish between events and scenarios		The reporting allows you to report at various levels within simulation names if your naming convention uses underscores '_' to distinguish between events and scenarios

			[[File:reporting.gif\|frame\|none]]

Chris Ryan at 05:04, 21 November 2012

2012-11-21T05:04:27Z

Chris Ryan at 05:03, 21 November 2012

2012-11-21T05:03:09Z

← Older revision		Revision as of 15:03, 21 November 2012
Line 1:		Line 1:
			=Overview=
	This page is currently under construction.<br>
	<br>		<br>
	TUFLOW Run Interface Manager (TRIM) is a TUFLOW simulation manager developed by [http://www.csse.com.au Catchment Simulation Solutions]. Detailed documentation can be found at: [http://www.csse.com.au/trim_online_help http://www.csse.com.au/trim_online_help]		TUFLOW Run Interface Manager (TRIM) is a TUFLOW simulation manager developed by [http://www.csse.com.au Catchment Simulation Solutions]. Detailed documentation can be found at: [http://www.csse.com.au/trim_online_help http://www.csse.com.au/trim_online_help]
Line 7:		Line 7:
	Some specific tips and tricks include:		Some specific tips and tricks include:

	===Increasing the speed of your TUFLOW modelling===		=Increasing the speed of your TUFLOW modelling=

	We all want to get our TUFLOW simulations complete ASAP. TRIM is designed to aid in this process by clever queue management ensuring all available licenses are in use at all time. However, there are also a couple of ways to speed up individual simulations. These include		We all want to get our TUFLOW simulations complete ASAP. TRIM is designed to aid in this process by clever queue management ensuring all available licenses are in use at all time. However, there are also a couple of ways to speed up individual simulations. These include

	''Auto Stop''		==Auto Stop==

	TRIM can automatically stop your simulation once it has safely passed the peak. This can save loads of time. For more information refer [http://www.csse.com.au/trim_online_help/index.php?trim_autostop.htm here]. Note, if your modelling PC is unattended, you may need to apply the fix at the bottom of the [http://www.csse.com.au/trim_online_help/index.php?trim_autostop.htm page] to get Auto Stop to work properly.		TRIM can automatically stop your simulation once it has safely passed the peak. This can save loads of time. For more information refer [http://www.csse.com.au/trim_online_help/index.php?trim_autostop.htm here]. Note, if your modelling PC is unattended, you may need to apply the fix at the bottom of the [http://www.csse.com.au/trim_online_help/index.php?trim_autostop.htm page] to get Auto Stop to work properly.

	''Hide Windows''		==Hide Windows==

	TRIM has an option to suppress the TUFLOW console display. Besides avoiding hijacking the screen when new windows are launched, we are investigating if this can improve performance (we have observed up to a 10% speed increase based on the tutorial model).		TRIM has an option to suppress the TUFLOW console display. Besides avoiding hijacking the screen when new windows are launched, we are investigating if this can improve performance (we have observed up to a 10% speed increase based on the tutorial model).

	'''Automation of Post Processing~~'''~~		='Automation of Post Processing=

	Fiddling around with batch files to post process your simulations is virtually a thing of the past with TRIM's automation of post processing. TRIM can automatically group your simulations (based on common ARIs), run dat_t_dat to extract peak results and run TUFLOW_to_GIS to convert to common formats. It can also automatically create other formats such as TAB / SHP / TIF and others. Detailed documentation can be found [http://www.csse.com.au/trim_online_help/index.php?automation_of_post_processing.htm here] but there are a couple tricks to using this tool.		Fiddling around with batch files to post process your simulations is virtually a thing of the past with TRIM's automation of post processing. TRIM can automatically group your simulations (based on common ARIs), run dat_t_dat to extract peak results and run TUFLOW_to_GIS to convert to common formats. It can also automatically create other formats such as TAB / SHP / TIF and others. Detailed documentation can be found [http://www.csse.com.au/trim_online_help/index.php?automation_of_post_processing.htm here] but there are a couple tricks to using this tool.

	''Removal of 1D Networks from results''		==Removal of 1D Networks from results==

	It's quite common to want to remove the underground 1d network from your 2D results. TRIM has a special command to do this, for example ''<remove_1d_net_match_"subsurface">''. This will remove any 1D network that has the text ''subsurface'' in its name. Firstly, for this to work correctly, you must have the ''Meshparts == ON'' command in your model. Secondly, since this works based on a text match set in the Post Processing template, it would be useful to adopt a naming convention in all TUFLOW projects where all 1D networks (that you want to remove from 2D results) share acommon code that is unlikely to be inadvertently used by accident.		It's quite common to want to remove the underground 1d network from your 2D results. TRIM has a special command to do this, for example ''<remove_1d_net_match_"subsurface">''. This will remove any 1D network that has the text ''subsurface'' in its name. Firstly, for this to work correctly, you must have the ''Meshparts == ON'' command in your model. Secondly, since this works based on a text match set in the Post Processing template, it would be useful to adopt a naming convention in all TUFLOW projects where all 1D networks (that you want to remove from 2D results) share acommon code that is unlikely to be inadvertently used by accident.

	''Auto-grouping of simulations''		==Auto-grouping of simulations==

	The power of automated post processing is at its best when used with Events and Scenarios models. These can be configured using the [http://www.csse.com.au/trim_online_help/index.php?events_and_scenarios.htm Events and Scenarios GUI]. The table icon button allows you to automatically add all combinations of ARIs and durations and automatically group them into suitable groupings for dat_to_dat processing. There are options available via right click to duplicate entire groups with a different scenario further streamlining your modelling.		The power of automated post processing is at its best when used with Events and Scenarios models. These can be configured using the [http://www.csse.com.au/trim_online_help/index.php?events_and_scenarios.htm Events and Scenarios GUI]. The table icon button allows you to automatically add all combinations of ARIs and durations and automatically group them into suitable groupings for dat_to_dat processing. There are options available via right click to duplicate entire groups with a different scenario further streamlining your modelling.

	~~'''~~Reporting~~'''~~		=Reporting=

	The reporting allows you to report at various levels within simulation names if your naming convention uses underscores '_' to distinguish between events and scenarios		The reporting allows you to report at various levels within simulation names if your naming convention uses underscores '_' to distinguish between events and scenarios


	For more information please see:<br>
	[http://www.csse.com.au/index.php?option=com_content&task=view&id=14&Itemid=106 http://www.csse.com.au/]

Chris Ryan at 05:00, 21 November 2012

2012-11-21T05:00:41Z

← Older revision		Revision as of 15:00, 21 November 2012
Line 7:		Line 7:
	Some specific tips and tricks include:		Some specific tips and tricks include:

	~~'''~~Increasing the speed of your TUFLOW modelling~~'''~~		===Increasing the speed of your TUFLOW modelling===

	We all want to get our TUFLOW simulations complete ASAP. TRIM is designed to aid in this process by clever queue management ensuring all available licenses are in use at all time. However, there are also a couple of ways to speed up individual simulations. These include		We all want to get our TUFLOW simulations complete ASAP. TRIM is designed to aid in this process by clever queue management ensuring all available licenses are in use at all time. However, there are also a couple of ways to speed up individual simulations. These include

← Older revision		Revision as of 10:34, 18 July 2024
Line 1:		Line 1:
	=Overview=		=Overview=
	TUFLOW Run Interface Manager (TRIM) is a product developed by [~~http~~://www.csse.com.au Catchment Simulation Solutions] to help manage your TUFLOW model runs more efficiently. It allows you to manage a large queue of simulations with any designated number of simulations running simultaneously. This ensures the fastest job completion and maximum license utilisation.		TUFLOW Run Interface Manager (TRIM) is a product developed by [https://www.csse.com.au Catchment Simulation Solutions] to help manage your TUFLOW model runs more efficiently. It allows you to manage a large queue of simulations with any designated number of simulations running simultaneously. This ensures the fastest job completion and maximum license utilisation.

	*On the fly charting of flows, errors and wet cell counts.		*On the fly charting of flows, errors and wet cell counts.
Line 9:		Line 9:
	*Detailed reporting on modelling time broken up by project, date, user or other criteria.		*Detailed reporting on modelling time broken up by project, date, user or other criteria.

	Detailed documentation can be found at: [~~http~~://www.csse.com.au/trim_online_help ~~http~~://www.csse.com.au/trim_online_help]		Detailed documentation can be found at: [https://www.csse.com.au/trim_online_help https://www.csse.com.au/trim_online_help]

	TRIM is free for a one simultaneous simulation version. For more information on commercial license options, please vist [~~http~~://www.csse.com.au/trim this page].		TRIM is free for a one simultaneous simulation version. For more information on commercial license options, please vist [https://www.csse.com.au/trim this page].

	[[File:TRIM_Image.gif\|frame\|none]]		[[File:TRIM_Image.gif\|frame\|none]]
Line 25:		Line 25:
	===Auto Stop===		===Auto Stop===

	TRIM can automatically stop your simulation once it has safely passed the peak. This can save loads of time. For more information refer [~~http~~://www.csse.com.au/trim_online_help/~~index.php?~~trim_autostop.~~htm~~ here]. Note, if your modelling PC is unattended, you may need to apply the fix at the bottom of the [~~http~~://www.csse.com.au/trim_online_help/~~index.php?~~trim_autostop.~~htm~~ page] to get Auto Stop to work properly.		TRIM can automatically stop your simulation once it has safely passed the peak. This can save loads of time. For more information refer [https://www.csse.com.au/trim_online_help/trim_autostop.html here]. Note, if your modelling PC is unattended, you may need to apply the fix at the bottom of the [https://www.csse.com.au/trim_online_help/trim_autostop.html page] to get Auto Stop to work properly.

	==Automation of Post Processing==		==Automation of Post Processing==

	Fiddling around with batch files to post process your simulations is virtually a thing of the past with TRIM's automation of post processing. TRIM can automatically group your simulations (based on common ARIs), run dat_t_dat to extract peak results and run TUFLOW_to_GIS to convert to common formats. It can also automatically create other formats such as TAB / SHP / TIF and others. Detailed documentation can be found [~~http~~://www.csse.com.au/trim_online_help/~~index.php?~~automation_of_post_processing.~~htm~~ here] but there are a couple tricks to using this tool.		Fiddling around with batch files to post process your simulations is virtually a thing of the past with TRIM's automation of post processing. TRIM can automatically group your simulations (based on common ARIs), run dat_t_dat to extract peak results and run TUFLOW_to_GIS to convert to common formats. It can also automatically create other formats such as TAB / SHP / TIF and others. Detailed documentation can be found [https://www.csse.com.au/trim_online_help/automation_of_post_processing.html here] but there are a couple tricks to using this tool.

	===Removal of 1D Networks from results===		===Removal of 1D Networks from results===
Line 37:		Line 37:
	===Auto-grouping of simulations===		===Auto-grouping of simulations===

	The power of automated post processing is at its best when used with Events and Scenarios models. These can be configured using the [~~http~~://www.csse.com.au/trim_online_help/~~index.php?~~events_and_scenarios.~~htm~~ Events and Scenarios GUI]. The table icon button allows you to automatically add all combinations of ARIs and durations and automatically group them into suitable groupings for dat_to_dat processing. There are options available via right click to duplicate entire groups with a different scenario further streamlining your modelling.		The power of automated post processing is at its best when used with Events and Scenarios models. These can be configured using the [https://www.csse.com.au/trim_online_help/events_and_scenarios.html Events and Scenarios GUI]. The table icon button allows you to automatically add all combinations of ARIs and durations and automatically group them into suitable groupings for dat_to_dat processing. There are options available via right click to duplicate entire groups with a different scenario further streamlining your modelling.

	[[File:events.gif\|frame\|none]]		[[File:events.gif\|frame\|none]]

← Older revision		Revision as of 15:04, 21 November 2012
Line 4:		Line 4:

	[[File:TRIM_Image.gif\|frame\|none]]		[[File:TRIM_Image.gif\|frame\|none]]

			=Tips=

	Some specific tips and tricks include:		Some specific tips and tricks include:

	=Increasing the speed of your TUFLOW modelling=		==Increasing the speed of your TUFLOW modelling==

	We all want to get our TUFLOW simulations complete ASAP. TRIM is designed to aid in this process by clever queue management ensuring all available licenses are in use at all time. However, there are also a couple of ways to speed up individual simulations. These include		We all want to get our TUFLOW simulations complete ASAP. TRIM is designed to aid in this process by clever queue management ensuring all available licenses are in use at all time. However, there are also a couple of ways to speed up individual simulations. These include

	==Auto Stop==		===Auto Stop===

	TRIM can automatically stop your simulation once it has safely passed the peak. This can save loads of time. For more information refer [http://www.csse.com.au/trim_online_help/index.php?trim_autostop.htm here]. Note, if your modelling PC is unattended, you may need to apply the fix at the bottom of the [http://www.csse.com.au/trim_online_help/index.php?trim_autostop.htm page] to get Auto Stop to work properly.		TRIM can automatically stop your simulation once it has safely passed the peak. This can save loads of time. For more information refer [http://www.csse.com.au/trim_online_help/index.php?trim_autostop.htm here]. Note, if your modelling PC is unattended, you may need to apply the fix at the bottom of the [http://www.csse.com.au/trim_online_help/index.php?trim_autostop.htm page] to get Auto Stop to work properly.

	==Hide Windows==		===Hide Windows===

	TRIM has an option to suppress the TUFLOW console display. Besides avoiding hijacking the screen when new windows are launched, we are investigating if this can improve performance (we have observed up to a 10% speed increase based on the tutorial model).		TRIM has an option to suppress the TUFLOW console display. Besides avoiding hijacking the screen when new windows are launched, we are investigating if this can improve performance (we have observed up to a 10% speed increase based on the tutorial model).

	='Automation of Post Processing=		==Automation of Post Processing==

	Fiddling around with batch files to post process your simulations is virtually a thing of the past with TRIM's automation of post processing. TRIM can automatically group your simulations (based on common ARIs), run dat_t_dat to extract peak results and run TUFLOW_to_GIS to convert to common formats. It can also automatically create other formats such as TAB / SHP / TIF and others. Detailed documentation can be found [http://www.csse.com.au/trim_online_help/index.php?automation_of_post_processing.htm here] but there are a couple tricks to using this tool.		Fiddling around with batch files to post process your simulations is virtually a thing of the past with TRIM's automation of post processing. TRIM can automatically group your simulations (based on common ARIs), run dat_t_dat to extract peak results and run TUFLOW_to_GIS to convert to common formats. It can also automatically create other formats such as TAB / SHP / TIF and others. Detailed documentation can be found [http://www.csse.com.au/trim_online_help/index.php?automation_of_post_processing.htm here] but there are a couple tricks to using this tool.

	==Removal of 1D Networks from results==		===Removal of 1D Networks from results===

	It's quite common to want to remove the underground 1d network from your 2D results. TRIM has a special command to do this, for example ''<remove_1d_net_match_"subsurface">''. This will remove any 1D network that has the text ''subsurface'' in its name. Firstly, for this to work correctly, you must have the ''Meshparts == ON'' command in your model. Secondly, since this works based on a text match set in the Post Processing template, it would be useful to adopt a naming convention in all TUFLOW projects where all 1D networks (that you want to remove from 2D results) share acommon code that is unlikely to be inadvertently used by accident.		It's quite common to want to remove the underground 1d network from your 2D results. TRIM has a special command to do this, for example ''<remove_1d_net_match_"subsurface">''. This will remove any 1D network that has the text ''subsurface'' in its name. Firstly, for this to work correctly, you must have the ''Meshparts == ON'' command in your model. Secondly, since this works based on a text match set in the Post Processing template, it would be useful to adopt a naming convention in all TUFLOW projects where all 1D networks (that you want to remove from 2D results) share acommon code that is unlikely to be inadvertently used by accident.

	==Auto-grouping of simulations==		===Auto-grouping of simulations===

	The power of automated post processing is at its best when used with Events and Scenarios models. These can be configured using the [http://www.csse.com.au/trim_online_help/index.php?events_and_scenarios.htm Events and Scenarios GUI]. The table icon button allows you to automatically add all combinations of ARIs and durations and automatically group them into suitable groupings for dat_to_dat processing. There are options available via right click to duplicate entire groups with a different scenario further streamlining your modelling.		The power of automated post processing is at its best when used with Events and Scenarios models. These can be configured using the [http://www.csse.com.au/trim_online_help/index.php?events_and_scenarios.htm Events and Scenarios GUI]. The table icon button allows you to automatically add all combinations of ARIs and durations and automatically group them into suitable groupings for dat_to_dat processing. There are options available via right click to duplicate entire groups with a different scenario further streamlining your modelling.

	=Reporting=		==Reporting==

	The reporting allows you to report at various levels within simulation names if your naming convention uses underscores '_' to distinguish between events and scenarios		The reporting allows you to report at various levels within simulation names if your naming convention uses underscores '_' to distinguish between events and scenarios