par

Administrators
  • Content count

    371
  • Joined

  • Last visited

Community Reputation

0 Neutral

1 Follower

About par

  • Rank
    Administrator
  • Birthday

Profile Information

  • Gender
    Male

Recent Profile Visitors

1275 profile views
  1. Hi Michael, If you have grid output directly from TUFLOW (in either .asc, or .flt format) and you have the maximums on (which is the default), this should already be output directly from TUFLOW. In your grids folder you should see a number of maximum grids: _h_Max - the maximum water levels _V_Max - the maximum velocities _TMax_h - the time of maximum water level _TMax_V - the time of maximum velocity. Hope that helps, get back to use if you have any questions. Phil
  2. Please note for the 2016-03-AD there have been a number of changes / enhancements to the GPU boundaries. Please refer to this post and the release notes:
  3. Hi Melodea, It depends on the type of pit that you are modelling. If you are modelling with an "R" type pit then these dimensions are used for defining the pit as a rectangular culvert. If you are specifying a "Q" type pit a user defined depth-flow relationship is provided and these attributes are not used. Phil
  4. Hi Melodea, In the pit database a width and an area can be specified. Are these the attributes you are referring to? Or are you referring to the width / height in the 1d_nwk attributes? Regards Phil
  5. By variable Manning's n, do you mean depth varying Manning's n, as opposed to spatially varying Manning's n? Cheers Phil
  6. Hi Adam, Are you able to clarify what it is you are trying to do? Is it to take an asset database and convert it into a 1d_nwk format? Cheers Phil
  7. Great, thanks for the update Robin. FYI, we are doing some final testing and are planning to release an 2016-03-AC update, in the next week or so. This has some cool new features (mainly in the GPU) . Cheers Phil
  8. Hi Robin, There was an issue with 2016-03-AA for an TUFLOW-Flood Modeller where water level lines were being used. If you update to the 2016-03-AB version this should resolve the issue. Please see the forum announcement for details and download links. Cheers Phil
  9. An update to the 2016 version of TUFLOW (2016-03-AB) has been released. This addresses the above issue and all GPU models using the 2016 release should move to this build. Please see the following forum post for more information and download links:
  10. An update to the 2016 version of TUFLOW (2016-03-AB) has been released. This addresses the above issue and all GPU models using the 2016 release should move to this build. Please see the following forum post for more information and download links:
  11. We are pleased to announce an update to the 2016-03 TUFLOW Release (Build 2016-03-AB) is now available. It is recommended that all users of Builds 2016-03-AA update to this build. The release notes provide a complete description of the 2016-03-AB improvements. The most significant updates include: Enhancements and bug fixes to the GPU Solver: The recent nVidia driver update issue has been fixed. A gridded rainfall boundary condition input bug has been fixed. Matrix blockage options. Models can vary the culvert blockage definition based on the event magnitude (ARI). Tracking of maximum bed shear stress and stream power. Additional model template empty files are now output. Links to download: Downloads Page Release Notes 2016 Manual (*.pdf) Any queries or issues, please don't hesitate to email support@tuflow.com. And enjoy! Best Regards TUFLOW Team
  12. Hi Katie and Peter, We are aware (and have fixed) an issue with the reporting locations, if the flow line does not cross any 1D channels, this could cause the model to crash. This has been updated and will be available in the 1st update to the 2016 release. However, using the PO lines should resolve this issue! Katie, are you able to email the RL and PO layer(s) and the .tlf file through to support@tuflow.com and we can take a closer look. Thanks Phil
  13. HI David, The critical bed shear at which erosion starts to occur is very dependent on the size of the particles. There is a lot of literature on this if you have a search, just make sure that the units match as a some of the guidance is in US Customary units! See also this post on the units output by TUFLOW: The higher values (>2,000) are likely due the equation which has a divide by depth, so at shallow depths these can get quite large. See also the "BSS Cutoff Depth == " .tcf command in the manual. Cheers Phil
  14. Hi Simon, From memory the 1st dot point resolved the issue (although it was few years ago my memory may be failing me). Is the licence you are having issue with a local or network dongle? You can monitor the licence usage using the CodeMeter "Webadmin". This can be accessed by pointing a web browser to:http://localhost:22350/ and then heading to the licence monitoring as per the attached image. The cmdust diagnostic file also contains a record of all the licence attempts. If you can send that through to support@tuflow.com we can have a look at what might be happening. Cheers Phil
  15. An update for other users: This error is being reported as the model has 1D commands specified in the .tcf. This causes TUFLOW to check that a valid 1D model has been specified. For more information on this error please see Error 1301 on the wiki.