Jump to content
TUFLOW Forum

Recommended Posts

Similar to using events or scenarios, any number of Output Zones can be defined. The “Model Output Zones ==”“ command is used to select which output zones are to be used in the simulation.
There is no requirement to have a separate file containing the output zone definitions. However, if there are numerous output zones, it would be good practice to place these in one or more separate files and use the “Read File ==” to reference these file(s) so as to keep the size of the .tcf file minimal. 
 
If you want to use multiple output zones for a particular simulation your control file should use the “Model Output Zone ==” command with a vertical bar (pipe) between output zone definitions, like this:
Model Output Zones == ZoneA | ZoneB 
 
Please note, if you repeat the Model Output Zones command then only the last command will be used to define the output in TUFLOW. For example, if you set out your commands as below, only Zone 2 will be output to your results files.
Model Output Zones == Zone1
Model Output Zones == Zone2
 
Each output zone is defined using a definition block as follows:
Define Output Zone == <oz_name> 
….. 
End Define
 
With the exception of “Read GIS Output Zone ==”, all commands are optional. 
Note that the output zone must be a polygon shape, not a rectangle or square shape. If Tuflow detects a shape that is not a polygon, WARNING 2073 will be in the messages layer.
 
Refer to the 2013-12 Release notes, sections 35 to 37 for commands that can be used within an output zone. An example out an output zone setup is as follows:
 
 
Model Output Zones == ZoneA | ZoneB
 
Define Output Zone == ZoneA                                                      !Zone at the river mouth
  Read GIS Output Zone == ..\model\gis\2d_OZ_ZoneA.shp      !GIS layer that contains polygon(s) of region to be output
  Map Output Format == XMDF                                                     ! Options: DAT XMDF WATERRIDE GRID BLUEKENUE and SMS TRIANGLES
  Map Output Interval == 300                                                        ! Seconds 
  XMDF Map Output Data Types == h v d q
  Output Folder == ..\results\<<~s1~>>_<<~s2~>>\zones
  Maximums and Minimums == ON MAXIMUMS ONLY  
  Map Cutoff Depth == 0.05
End Define
 
Define Output Zone == ZoneB                                                         !Zone near the development
  Read GIS Output Zone == ..\model\gis\2d_OZ_ZoneB.shp         !GIS layer that contains polygon(s) of region to be output
  Map Output Format == XMDF DAT GRID                                       ! Options: DAT XMDF WATERRIDE GRID BLUEKENUE and SMS TRIANGLES
  Grid Format == ASC
  Map Output Interval == 300                                    ! Seconds 
  XMDF Map Output Data Types == h v d q MB1 MB2 
  Output Folder == ..\results\<<~s1~>>_<<~s2~>>\zones
  Maximums and Minimums == ON MAXIMUMS ONLY  
  Map Cutoff Depth == 0.05
End Define
 

Share this post


Link to post
Share on other sites

I am trying to map different cutoff depths in different output zones. ie for the entire model, have a Map Cutoff Depth == 0.0 and for output zone Filt, Map Cutoff Depth = 0.05.

 

Both sets of results produced are for a Map Cutoff Depth = 0.05. It seems as if it applies the last cutoff depth read in to all zones regardless of whether or not the command sits within Define Output Zone - End Define.

 

I note that in the .tlf the Map Cutoff Depth is not defined for each individual zone. Is there a specific command that does this that I may have missed in the release notes? 

Share this post


Link to post
Share on other sites

Hi Tom,

 

Unfortunately the "Map Cutoff Depth" command was documented as being available for different output zones.  This was incorrect, the command is still a global command, ie. all output zones will use the same map cutoff depth if specified.).  The documentation has been corrected in the latest release notes: see point 36(G).

 

However, this can be post-processed with the asc_to_asc utility as descriebed here:

http://wiki.tuflow.com/index.php?title=ASC_to_ASC#Cutoff_Depth

 

Apologies for the confusion.

 

Cheers

Phil

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...