tuflow support

Administrators
  • Content count

    139
  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About tuflow support

  • Rank
    Advanced Member
  • Birthday

Contact Methods

  • ICQ
    0

Recent Profile Visitors

2555 profile views
  1. 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.
  2. 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.
  3. 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.
  4. 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).
  5. 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.
  6. Pre-release testing for the forthcoming update to the 2016 version of TUFLOW has identified a potential issue in the 2016-03-AA version of TUFLOW when using TUFLOW GPU with SA inflows and the latest version of the NVidia drivers (368.81). The issue occurs when the SA inflows are proportioned to depth (which is the default behaviour). Previous versions of the NVidia driver show the correct flows, but for the latest driver, an issue can occur when there are cells wetting / drying within the SA boundary causing an incorrect inflow volume. The NVidia drivers were released on the 14th of July 2016 and the 2016-03-AA version of TUFLOW was released in March 2016. Our SA inflow test results are shown below, for the same model with the NVidia latest drivers (368.81) and an older set of drivers. The results highlight how artificial volume is being created by the simulation run using the new NVidia drivers (368.81). Our testing has shown this error is resolved by using the “Read GIS SA ALL ==“ command, instead of “Read GIS SA ==”. If you are using the 2016-03-AA version with SA inflows within a TUFLOW GPU model, the following is recommended: 1) Quality check you flow / volumes results to determine if the NVidia Drivers your computer uses creates the above mentioned issue. 2) Use the “Read GIS SA ALL” option. An 2016-03-AB update is to be released shortly which will address the issue. For future NVidia driver updates, we are planning on running a series of benchmark models to check compatibility of the drivers. Please contact support@tuflow.com if you have any questions about the above. Regards TUFLOW Team
  7. 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
  8. 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
  9. 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
  10. Welcome to the TUFLOW Forum This forum connects the TUFLOW community through announcements, questions, knowledge sharing and users experiences. The forum has a technical and applications focus, and is moderated by the TUFLOW Support Team. Here are some guidelines to get you started: 1) Register as a forum user Before you can post, please register as a forum user. You need to validate your email address and then be approved by a forum moderator. Using your organisations email address is preferable as we can approve you straight away. This process is needed to prevent spammers and advertisers from registering. 2) Publish a post or ask a question The forum is organised into forums and sub-forums, from which users are able to post questions and comments as topics. Before creating a new topic, it can be worthwhile checking whether a similar one already exists – it may even answer your question! The easiest way to search the forum is to use Google (eg. ‘Tuflow Forum, boundary error’). You can also add your comments or questions to an existing thread in response to other user’s post. When you post a topic, please only click the ‘Submit Topic’ button once, even if the forum pauses for a while (clicking a second time will submit the post twice). The pause is due to email notifications being issued and is a characteristic of the Forum software. 3) Share Your Knowledge Help others by answering their questions and sharing your experience. Sharing tips, resources and ideas contributes to the community user base that TUFLOW has become well known for. 4) Get Updates Under a forum or sub-forum, click ‘Follow This’ on the top right to subscribe to email updates to your favourite TUFLOW topic feeds. 4) Get Started Go the Forum Main Page, have a look around and if you're keen get involved start posting. If you have any queries please don't hesitate to drop us an email at support@tuflow.com and we'd be more than happy to help you out. Regards, the TUFLOW Team.
  11. Q: When using the "J" junction type manhole which losses / equations are applied? A: When using the Engelhund method, the J type 'manhole' uses the same equations as for the R and C type manholes in for the losses associated with change in direction (K-theta) and change in elevation (K-drop) at the junction. However, for expansion and contraction losses at the junction, these are recalculated every timestep according the departure/approach velocities of the downstream/upstream culvert (see Equations in Section 4.7.4.1 in the 2010 manual. These equations are essentially the same as used the manhole expansion/contraction losses, however, instead of using the manhole area for the term Am, the area of the downstream/upstream culvert is used. The applied entry and exit losses at a J 'manhole' are therefore a function of the approach and departure velocities which are derived from the incoming and outgoing pipe respectively. The calculated losses throughout the simulation can be reviewed in the _TSL output layer.
  12. We’re pleased to announce the forthcoming TUFLOW FV New Features and Application Seminars. The seminars are free to attend and will be led by Dr Ian Teakle, the primary developer of TUFLOW FV. The next seminars will be held in: Melbourne on Tuesday, 12 May 2015 Sydney on Wednesday, 13 May 2015 Please refer to the TUFLOW website for more information about the seminars: http://www.tuflow.com/Training.aspx?ws To register for one of the events please contact training@tuflow.com and specify your city
  13. Dear TUFLOW users, The agenda for the TUFLOW FV New Features and Applications Seminar in Brisbane on Thursday 19 March 2015 is now available via the TUFLOW website: http://tuflow.com/Training.aspx?ws There are only a few places still available for the Brisbane event so please register by contacting training@tuflow.com. Dates for other capital cities will be announced shortly. Regards TUFLOW Team
  14. Hi Chris, If the change in elevation is linear then you could use the Variable Z Shape. If not you may need to use the "VG" type in the 2D_bc layer, in this you can specify a timeseries of elevation over time. Are you running the model for long periods of time (years), or are you running the model at discrete climate conditions. E.g. a simulation with 2050 and 2100 conditions? Regards Phil
  15. Hi All, Thanks for pointing this out. It appears that in the TUFLOW GPU updates for the 2013-12-AC release a newer function is called and this is not available in Windows XP (only in Vista and newer): http://msdn.microsoft.com/en-us/library/windows/desktop/dd318702%28v=vs.85%29.aspx We are looking to issue an update which resolves this issue. Regards TUFLOW Support Team