Jump to content

Rohan King

  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About Rohan King

  • Rank

Profile Information

  • Gender
  • Location

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. -- Update -- The WDRVR.dll issue is occurring as the 2005 version of the executable requires the softlok dongle drivers to be installed (we now use WIBU dongles). The download for these can be found here: https://www.tuflow.com/Download/Drivers/SoftLokDongleDrivers.003.zip However, in order to be able to run simulations, the user will also need to have an old softlok dongle – there is a chance that this is a USB dongle, but for the 2005 build this is most likely a parallel port dongle. The latest versions of the TUFLOW executables back to 2006-06 have been released as WIBU compatible builds. We can’t modify builds prior to 2006-06 to be compatible with WIBU, however we do keep a number of older dongles available at standard rental rates if required. The default approach would be to try the 2006-06-DB version (which supports Wibu dongles), there may be some minor model changes required to update the model to this version. Defaults == PRE 2006-06 can be used to force the 2006 version to use the 2005-05 default parameters. Section 14.5 & page A-15 within the 2018 TUFLOW manual are worth reading to familiarise yourself with the default settings. Happy modelling! Rohan
  2. Hi Tom, Without knowing much about the setup of your model I would be inclined to run through the following checks first; Open your BC tables check file and ensure that you have a sensible stage-discharge relationship at your boundary; Generate a terrain cross section along your HQ boundary. HQ boundaries are typically used for defined channels as they work by applying a constant water level along the whole boundary based on the incoming flow. If you have undulating terrain along the boundary the water level will most likely be different, especially for long HQ boundaries, and TUFLOW is trying to apply a constant level to the boundary line which can cause issues; and View a time series of your 2D results at the boundary and check for circulations. I suspect the issue has to do with your HQ boundary setup. Cheers, Rohan
  3. Hi Rohan, In the recently released 2016 TUFLOW manual you will find a 'Limitation and Recommendations' write up (see section 1.4). I have provided a link to the downloads page on the TUFLOW website where you can get the manual if you haven't done so already. http://www.tuflow.com/Tuflow%20Latest%20Release.aspx Also, there has been a few benchmarking studies conducted over the years using TUFLOW, a number of which have been collated on the TUFLOW wiki (http://wiki.tuflow.com/index.php?title=TUFLOW_Benchmarking). Off topic slightly, Rachel Jensen wrote an interesting post on the impact the different schemes have on run time http://www.tuflow.com/forum/index.php?/topic/1574-parallelisation-of-tuflow-classic/#comment-3965 - perhaps a different perspective on TUFLOW limitations than what you originally enquired about but it's still a good read. Which particular limitations are you interested in? 2D Shallow water equations, 1D or 2D structures in TUFLOW, etc? Cheers, Rohan
  • Create New...