TRIM Tips

This page is currently under construction.

TUFLOW Run Interface Manager (TRIM) is a TUFLOW simulation manager developed by Catchment Simulation Solutions. Detailed documentation can be found at: http://www.csse.com.au/trim_online_help

Some specific tips and tricks include:

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

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 here. Note, if your modelling PC is unattended, you may need to apply the fix at the bottom of the 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 have observed up to a 10% speed increase (based on the tutorial model).

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 here but there are a couple tricks to using this tool.

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.

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 Events and Scenarios GUI. The table button File:Http://www.csse.com.au/trim online help/clip0047.png

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

For more information please see:
http://www.csse.com.au/