TUFLOW Forum

tuflow support

142

0 Neutral

• Rank

Recent Profile Visitors

13224 profile views

2. Upcoming TUFLOW Training (AU, NZ, UK, USA) and Conferences

TUFLOW 2017 – Additional Australian Introductory and Advanced Training Sessions - Filling Fast!!! Hi All, The 2017 version of TUFLOW has some of the most exciting new computational features for several years. Following the sell-out of our mid-year training and workshop days we will be re-visiting Brisbane, Sydney and Melbourne in late November and Early December showcasing the new features of TUFLOW and offering ‘hands on’ introductory and advanced training sessions. Please note that our Melbourne Introductory training day is now FULL. Other sessions are also filling up quickly but there’s still time to get involved. For more information check out our flyer or email training@tuflow.com. https://www.tuflow.com/Download/Training/L.TPS000.0_2017_TUFLOW_Extra_Sessions.pdf Cheers, Mitch.
3. Plot Output flow line along a HX 1D/2D boundary

Q: I want to output the flow between my 1D channel and the adjacent 2D overbank area. Will drawing a Plot Output line exactly along the 1D/2D HX boundary line provide the correct flow information? A: If you draw the Plot Output (PO) line directly on the HX line, the output may not include some of the flow that is crossing the boundary. This is because the HX line selects an entire row of cells, where one side is “active” in the 2D domain, and the other side is “inactive” in the 1D domain. The "Q_" type PO line on the other hand will select a polyline that goes along cell edges (see Figure 9-2 of the 2016-03-AE TUFLOW Manual), and there is the potential that it will select one of the sides of the HX cell where it is inactive for the 2D domain. This is demonstrated in the image below where a PO line (blue) exactly overlaps an HX boundary. The HX boundary would select entire cells (pink), where one side is inactive in the 2D domain (marked "x"). The "Q_" type PO line would select the cell sides (dashed black line). You can see that here are some locations where the PO line is selecting cell sides that aren’t active (highlighted yellow). Try digitising the PO line adacent to the HX boundary, just into the 2D domain. This should avoid selecting these inactive cell sides. Use the _TS.mif or _TS_L.shp results files to confirm which cell sides have been selected by your PO line.
4. Global Rainfall Boundary

Q: When using a Global Rainfall boundary (via the "Global Rainfall BC == " command) do the spatially varying losses via the materials file apply, or only the Global Rainfall losses ("Global Rainfall Continuing Loss == " and "Global Rainfall Initial Loss == " commands)? A: When using a Global Rainfall BC the approach is more simplistic than the one than used for a 2d_rf layer. No memory is allocated for spatial losses and the global rainfall losses are the only ones that apply. These global losses are subtracted from the rainfall before the simulation and each cell gets the same rainfall applied. Therefore: The global rainfall losses commands only apply to global rainfall boundaries and not to 2d_rf polygons. The material losses do not apply to global rainfall boundaries. We will issue an updated 2016-03-AE manual in the coming weeks and this behaviour has been clarified. For future versions we will likely; add some warnings if either of the above configurations is specified, we will also look at supporting spatial losses for global rainfall, but will likely make a new command for doing so, to keep the existing behaviour.

Hi dsheehy, Out of interest, how big are the result files you're trying to open up? We think Crayfish is a great product and are certainly interested to explore options to help out the Lutra team. At the moment we haven't planned on expanding TuPlot to read in 2D results, mainly because Crayfish has proven itself an excellent plugin for these purposes. Can you send us an email @ support@tuflow.com and we'll get in touch to discuss further. Cheers, Mitch.
6. Decimal Values in Hazard Outputs

Question: Why can I see decimal values in my hazard results? How should these values be categorised? Answer: The hazard results in TUFLOW will be output as integer values in the .xmdf and .dat files at the cell corners. However, when exporting to grid (in either .flt, asc or .nc format), the raster output is north south aligned and a regular grid (but your TUFLOW model may be rotated, may have 1D triangles and may have multiple domains). Therefore, the TUFLOW results are interpolated onto a north-south grid when directly writing grids from TUFLOW or when using the TUFLOW_to_GIS utility. Since TUFLOW build 2013-12-AD when directly writing a gridded output (e.g. .asc, .flt, .nc) the hazard outputs (except for z0, which is the velocity - depth product) are always output as an integer value, i.e. you only get a value 1,2,3 or 4 when directly writing hazard output to .asc . This is done in by rounding to the nearest integer, e.g. when interpolating a hazard value of 3.05 this is output as 3.0. If using an older version of TUFLOW, or using TUFLOW_to_GIS to post process, this can result in decimal values in the .flt or.asc grids between the desired integer values for hazard classification. To be consistent with how the latest TUFLOW Build is categorising floating point decimal values to integers when it directly outputs hazard grids (described above), the approach would be to categorise to the nearest integer value, e.g. 1.500-2.499 as 2 etc. If you did wish to reclassify 1.001-2.000 as 2 etc, this would provide a conservatively high hazard classification for decimal values, as you would be counting anything greater than the absolute integer in the next band.
7. TUFLOW GPU: Gridded Rainfall Input

Just an update to the above post, we are in the final stages of testing for a 2016-03-AB update, which will hopefully be available shortly. Also a word of caution about the work around above, if the boundary update interval is rounded number e.g. 5min / 60min per hour = 0.0833, then rounding in the grid time may also cause the boundary not to be updated and the rainfall rate / cumulative rainfall outputs (as described above should be used to confirm the rainfall depth applied).
8. TUFLOW GPU: Latest nVidia drivers (368.81)

Further to the above - the latest Quadro drivers (10.18.13.6886) which were also released mid July also appear to exhibit the same issue.

10. TUFLOW GPU: Gridded Rainfall Input

We have recently become aware of an issue affecting TUFLOW GPU simulations using the new gridded rainfall inputs. If the map output interval exceeds the interval in the rainfall grids, then the applied rainfall boundary condition is not updated. Choosing a map output interval that matches or divides into the boundary rainfall data interval will alleviate the issue. For example, if the gridded rainfall has a grid every 30 minutes, a Map Output Interval of 30, 15 or 10 minutes will all work. It is also important that the start map output time matches the gridded rainfall input start time. This will occur by default, though may be altered if a user defined Start Map Output time is specified. This does not affect TUFLOW “classic” simulations and the issue will be corrected in the 2016-03-AB release which will be available within the next month. If you're concerned about large file sizes resulting from your map output interval being reduced to fit your rainfall data interval you can use an output zone. For example with a 10 minute rainfall interval an output zone can be defined with an output interval of 10 minutes and the entire model output can be 1 hour. Again this work-around will only be required until the 2016-03-AB release. The 2016-03-AA release has the option to output the instantaneous rainfall rate and cumulative rainfall can be output with the RFR and RFC output types respectively. These can be used to cross-check the results. For example to output the depth, levels, velocities, rainfall rate and cumulative rainfall the .tcf command would be: Map Output Data Types == d h V RFR RFC Please contact support@tuflow.com if you have any queries relating to the above. Regards TUFLOW Support Team
11. Percentage Sign (%) in filenames

Q: When trying to run a batch file to convert a maximum water level from .dat format into .asc format I get an unexpected error. The batch file line is: C:\TUFLOW\Utilities\w64\TUFLOW_to_GIS_w64.exe -asc -b -t99999 M01_5m_1%AEP_001_h.dat A: This is most likely that the percentage character is treated as a special character in a batch file. For a description on this, please see the Microsoft site here: https://support.microsoft.com/en-us/kb/75634 In general I would tend to avoid special characters such as % in filenames where possible, for example there is a list here: http://www.mtu.edu/umc/services/web/cms/characters-avoid/ Whilst the % characters should generally fine in TUFLOW, are supported by Microsoft, however, they may require additional effort in batch files, e.g. may need to be wrapped in quotes (“) or have escape characters ignored. Another thing to note is that TUFLOW can directly write the outputs to .asc grid. You can output multiple file formats from TUFLOW and can set the data types, output interval etc based on the output format. For example in the below, the model will output dat and asc formats with only the maximums for the asc. Map Output Format == dat asc Map Output Data Types == h V q d Map Output Interval == 300 ASC Map Output Interval == 0 !only maximums for asc format ASC Map Output Data Types == h V d Z0
12. 1D/2D pit flow transfer

Question: I am receiving different opinions about the flow transfer rate regarding flow from the 2D terrain to a 1D subsurface element. Group 1 says that flow is transferred from 2D terrain to 1D catch pit using the weir equation. Group 2 says that the user can enter the capture rate using a depth (m) to hydraulic capture (m^3/s) chart. All flow will be tranferred from the 2D terrain to the 1D catch pit according to the parameters of the chart. Which of these two groups is correct? How does TUFLOW transfer flow from 2D to 1D? Answer: In TUFLOW a pit channel is designed to convey water to/from a 2D overland domain to a 1D pipe network. There are multiple options available for calculating flows, these are: Depth-discharge curve ("Q" type pit)Weir flow ("W" type pit)Rectangular culvert ("R" type pit)Circular culvert ("C" type pit, this one is rarely used)For more information on setting these up please see the Chapter in the TUFLOW manual on Pits and Pit Channels. Regards TUFLOW Support Team