Jump to content

tuflow support

  • Content Count

  • Joined

  • Last visited

Everything posted by tuflow support

  1. Q: In multiple grid modelling in Tuflow, when a finer mesh is put on top of a coarser mesh, is it necessary to null all the cells in the coarser mesh underneath (CD, f=-1, or 0)? A: Yes, the cells in the coarser grid that are replaced by the active cells in the finer grid must be deactivated, usually using a Code of 0. You can easily see which cells (coarser and finer) are active and which ones aren't by viewing the 2d_grd_check layer and inspecting or thematically mapping the Code attribute. The 2d_grd_check layer will contain all active (Code 1) coarse and fine cells in the one layer. It will also contain any inactive null cells (Code -1) and boundary or link cells (Code 2). It doesn't contain the inactive Code 0 cells. Q: What happens if those cells in the coarser mesh that are replaced by the finer mesh are not deactivated? A: In this case the water can flow in both domains so you could be potentially doubling conveyance and storage in the overlapping areas. This should be evident in the results as velocity arrows would occur for both domains. Q: Would Tuflow automatically discount the coarser cells which are underneath the finer cells? A: No. The user controls the process of activating/deactivating cells using Code polygons and the corresponding commands in the .tgc files. Note: The above apply for the 2D-2D Linking feature and are not all applicable for the 2D-2D Nesting feature (when released) which, for example, will automatically turn larger cells into smaller cells and thus will not require the user to activate/deactivate cells in areas of overlapping domains.
  2. Q: We are running version 2007-07 of TUFLOW. Our IT department prefers our staff to have limited access rights to our PCs. We have noticed that TUFLOW writes a simulations log file both to the working directory (under the 'run' folder) and in addition, writes to a simulation log file specific to the license number on the C:\ route. Unfortunately this latter write command routes to a 'protected' area of our PCs and we would prefer that this latter write command is disabled. The alternative is that we provide modelling staff with full administration rights on modelling PCs, which IT would prefer not to do. Is it possible, through a command in the batch run file, to disable writing to the license simulation log whilst allowing the simulation log write in the working directory? A: Yes, you can change this folder. By default it writes to C:\, but by using the -slp option you can change this (see relevant section of Table 5.1 in the 2007 manual which has also been pasted below). This feature is intended for inter-office network dongles, but you can also use it to change from C:\ to say "C:\temp" or something like "C:\Program Files\TUFLOW\log". Please note that there is a limit of 64 characters for the path to the folder and that this information is stored on the dongle (so you only have to do this once). Extract from Table 5.1: -slp Simulation Log Path. To set the path to a folder on the intranet to log all simulations from the dongle, at a command prompt enter TUFLOW.exe -slp “<url_path_to_global_log_file>”. This information is stored on the TUFLOW dongle and should only be carried out by the organisation’s administrator of the TUFLOW dongle. Very useful for network dongles being accessed across an intranet so that the administrator can view who’s clogging up the network licences! Introduced for Build 2007-07-AA. See Section 7.1.3. For example: TUFLOW.exe -slp “\\water\projects\tuflow\log” will prompt to log all simulations started with that dongle to a _ TUFLOW Simulations.log file in the folder \\water\projects\tuflow\log.
  3. Q: One of the guys here has tried downloading and running the TUFLOW tutorial. When executing TUFLOW, a message appears asking for WDRVR.DLL. Any ideas? A: This means that the dongle drivers haven't been installed. Although a dongle isn't needed to run the Tutorial Model, the TUFLOW.exe does require that the dongle drivers (which are contained in the WDRVR.DLL file) are installed. Download the dongle drivers from http://www.tuflow.com/Downloads_Misc.htm, run ..\Drivers\Install\sl2inst.exe and click on Install. TUFLOW.exe should now start (you can test this by double clicking on TUFLOW.exe) and the Tutorial Model(s) should now run.
  4. Q: I would like to know the format for output binary files. Could you please direct me where I could find them in the manual. A: Please see http://www.tuflow.com/forum/index.php?showtopic=157 and also SMS_File_Formats.pdf.
  5. Apologies Richard as we've accidentally sent you an uncoded dongle. We've sent an email to Akin in your IT department on how to recode the dongle.
  6. Things to try/check are: 1. The CN and HX lines are definitely snapped correctly. 2. The CN lines from the 1D node are two separate lines (one to each HX line on each side of the river), and not one line (ie. check that the two CN lines haven't been digitised as one line). 3. There is only one CN line snapped to the same point on the HX line (you can have more than one as long as the weighting factors (f attribute) add up to exactly one). If you can't solve the problem, please email the relevant layers (2d_bc, 1d_nwk and _messages) to support@tuflow.com.
  7. Please see http://www.tuflow.com/forum/index.php?showtopic=309 for suggestions and ideas that may help. The 2008 release has a number of enhancements for steep shallow flow, and will also be offered as a single precision (4-byte reals or around 7 significant figures) and a fully double precision version. (The tcf Double Precision command only uses 8-byte reals for water levels and is known to be problematic. It is not planned to be supported after the 2008 release.)
  8. Please see http://www.tuflow.com/forum/index.php?showtopic=309 for suggestions and ideas that may help. Although this won't solve your problem now, the 2008 release has a number of enhancements in this area and will also be offered as a single precision (4-byte reals or around 7 significant figures) and a fully double precision version. (The tcf Double Precision command only uses 8-byte reals for water levels and is known to be problematic. It is not planned to be supported after the 2008 release.)
  9. Sam advised the following by email: "Thank you for your suggestions in lowering the high mass balance in our 2D only models. After further investigation we discovered that the single inflow QT had been placed in an inappropriate location, I.e not on the lowest ZPT C within the “channel”. We concluded that the location of the QT with low flows is very sensitive to the localized DTM. We also found that using a depth dependent roughness layer was very effective in lowering the mass balance for models with flat floodplains with low flows."
  10. As you maybe aware, the free trial version of the MapInfo / TUFLOW Productivity Tools expires on June 30, 2008. The official release of the tools as a commercial product is scheduled for August 2008. A free interim release to bridge the gap from June 30th to end of August 2008 has been uploaded to www.tuflow.com and can be downloaded using the link: http://www.tuflow.com/Downloads/Utilities/...ate_2008_06.zip This interim release includes further enhancements, bug fixes and new tools. Also included are two new versions of the cross-section viewer/editor. XS_Editor_2000.xls is designed to run in MSExcel 2000 (and should also work in 2003 / 2007). XS_Editor_2003.xls works in MSExcel 2003 (and possibly 2007), but definitely does not work in MSExcel 2000. The licensing and purchase price details for the MapInfo Tools are: 1. TUFLOW Licensees may purchase an organisation-wide licence. 2. The licence provides unlimited access to the tools within the organisation, the only requirement is that the user's machine has access to one of the organisation's TUFLOW dongles when starting up the tools. 3. They have no expiry date, but to be entitled to software upgrades and support, payment of an annual fee is required. 4. The purchase price (per organisation) is 10% of the current value of all TUFLOW Software Licence(s) held/purchased by the TUFLOW Licensee. 5. The annual software upgrades and support fee is 5% of the current value of all TUFLOW Software Licence(s) held/purchased by the TUFLOW Licensee, with the first installment pro-rated to end next June. The annual fee entitles the organisation to free software upgrades and minor support (but not training). For sales enquiries, please email GIS_Tools@wbmpl.com.au. To help gain the full benefits of the efficiencies that can be derived from using them, training options and costs can be provided upon request. As an additional service, custom applications (eg. for streamlining working with LiDAR/ALS DEMs, data and model conversion, data and model QA/QC, custom interfaces, etc) can be developed. For more information, please contact GIS_Tools@wbmpl.com.au.
  11. Q: I have been asked by a client to reduce our grid size from 50 to 25m for a broad scale model. When we tried this with a much older version of the TUFLOW executable there were so many wet cells it was not possible to compute the result. How many wet cells can the latest version handle, do we actually have a limit before the dat_to_dat or TUFLOW_to_GIS executables to produce results? A: The latter versions of TUFLOW, TUFLOW_to_GIS and dat_to_dat all use dynamic memory allocation, so the limit is controlled by the machine's RAM and operating system. For tips on how to rectify the problem, see http://www.tuflow.com/forum/index.php?showtopic=124. For extremely large models, a 64bit version is being developed to handle these models into the future (a 64bit machine will be needed to utilise this version).
  12. Q: Arch Bridges in TUFLOW? The standard method of producing bridge loss table in accordance with the procedure in The Waterways Design Guide falls down when I try to treat the arch supports as piers due to them being so wide relative to flow area. IS there another approach? I would in other 1D software model these brides as a series of arch culverts, but last time I checked TUFLOW could only do circular and rectangular; is this still the case? Using an equivalent area opening rectangular culvert will also be difficult given the range of flow events being run; from 5 year ARI to PMF. I have attached a couple of photos of the types of bridges we are dealing with. You will notice that one of the bridges completely changes construction type half way across the river. How should this be best approached? Is an average bridge loss value really reasonable given that flow will not be 1D through this bridge with flow choosing the easier side of the bridge to go through? Is it possible to split the channel in two and connect two ESTRY bridge channels in parallel? Any suggestions would be greatly appreciated. A: They must be about the only arch bridges in Australia! In the UK, where there are a lot of arch bridges, our understanding is that they have successfully modelled these using a B channel, and using a height vs width table to describe the geometry (see the 1d_tab Type HW or CS in Table 4.10 of the 2007 manual). Clearly, the width values will reduce with height. The one big tip at the moment is to not specify a zero width for the last value as this is known to cause TUFLOW to crash with a math error (should be fixed for next release). Instead, specify something very small like 0.001 or 0.01m. You'll also need to specify an energy loss versus height table using the 1d_tab Type BG or LC as per Table 4.10. Note, using the Bend_Loss attribute is not appropriate here as the losses will vary with height. Yes, irregular shaped culverts are on the list and getting close to the top - hopefully in for the 2008 release. Regarding the bridge of mixed type, you can either lump them together when working out the height vs width table, or you can model them as two or more separate parallel channels. As long as the overall flow area is correct, and appropriate energy loss coefficients are applied (which may need calibrating either to any recorded levels or by cross-checking with publications or, say, a local HEC-RAS model), a good representation of the bridges should be achieved. Also see http://www.tuflow.com/forum/index.php?showtopic=270 Any tips from the UK?
  13. Q: We have received a TUFLOW dongle as part of our ISIS-TUFLOW software package. While I have been able to get the ISIS part of the software working, I have not been able to get the dongle to be read by the security server for TUFLOW. What I see is in image1.bmp The dongle is currently in the machine (I have tested this on several). The dongle drivers are installed, and there is no problem with the computer finding the dongle (“New hardware installed and ready to use”). The server is set to broadcast from port 6666 of the host computer as shown in image2.bmp We are in quite urgent need of this software, there is a training course scheduled for next Monday by when it will need to be operational. If you can provide any help or advice as to server configuration, or you can identify the problem, please let me know. A: It is normal not to see any entry in the Security Server dialog when it first starts up. Once TUFLOW tries to access the network dongle, if successful then an entry indicating the number of "Licences in use" and the maximum available will appear in the dialog. To test, go to a machine that has the TUFLOW.exe on it. On this machine, ensure that the dongle drivers have been installed and the correct IP Address or Name of the Server has been set using nsl2set.exe (see relevant sections in Section 5.1 of the TUFLOW manual). Double click on TUFLOW.exe in explorer, and if all correctly set up TUFLOW should find the network dongle and an entry should now appear in the Security Server dialog. If TUFLOW doesn't detect the network dongle carry out the following checks/tests: (i) Check that the client machine can see the server by using the ping command from a DOS prompt. (ii) Some networks have ports blocked, so make sure the port you are using is free. 6666 is automatically blocked by some anti-virus software (popular with hackers apparently). (iii) IP addresses are preferable to using a computer name (in the past we have had the odd problem when a name has been used).
  14. Q: We are moving our license servers, and as such I need to move the Tuflow license server, it will be a new server and new IP address. Can you please advise on what would be involved in doing this. A: Follow the instructions in "TUFLOW Dongle Installation.pdf" in http://www.tuflow.com/Downloads/Releases/D...Drivers.003.zip to install on the new server (these are the same instructions as would have been used for the current server). This link also contains the latest dongle installation software, which is recommended to be installed on all computers (see http://www.tuflow.com/forum/index.php?show...7&hl=dongle for more info) if not already done so. Once the dongle has been shifted to the new machine, each TUFLOW user will have to change the TUFLOW server IP address to the new one by running nsl2set.exe and entering in the new IP address. The user can test whether they are picking up the new IP address by double clicking on TUFLOW.exe in explorer and seeing whether the dongle is detected. Needless to say, all TUFLOW simulations will have to be finished/terminated before shifting the dongle.
  15. In the 1d_nwk table the open channels at the end don’t have US or DS inverts (ie. they are set to 0). The default for TUFLOW from Build 2006-03-AB onwards is for all inverts to be used. Hence, these channels will be set at 0m and about 120m below the culverts. If you want to over-ride this default, use “Apply All Inverts == OFF” in the ecf file, particularly if the model was developed using a Build prior to 2006-03-AB. Alternatively, you can set the invert attribute(s) to -99999.0, which will ignore the attribute(s) and use the bed of the channel. If using end cross-sections, the invert attributes are usually set to -99999 so that the slope and inverts of the channels are set to those based on the bed of the connected cross-sections.
  16. Q: I need to produce two flood maps; one showing maximum flood levels, and the other maximum flood levels minus 0.5m. I have no problem with the first one which I can directly get from Tuflow result (_h.dat) at t99999. However, I have a problem with the second one. I use MapInfo to minus 0.5m from the water levels in all cells. I have problem to null those cells when water level goes below ground level. I am wondering if you have a utility which allows me to do what I indicate above? A: We don't have any utility that does this, but you should be able to use Vertical Mapper's Analysis, Grid Query dialog to null the cells in the VM grid or use similar functionality in other 3D surface modelling software if you don't have Vertical Mapper. You will probably have to generate a depth grid by subtracting the ground level grid from the water level grid, or by converting TUFLOW's _d.dat output to a VM grid and subtracting 0.5m from this. Use this depth grid in the Grid Query (ie. where depth is less than zero, then where true take the value from the water level grid and where false set to null).
  17. Q: Trying to install Tuflow obtained from the Tuflow website but get a message suggesting a dll file is missing, see attached screen shot. I've received a licensed USB dongle and have tried installing the software with this plugged in but am still getting problems. A: The missing WDRVR.DLL message as in the attached occurs if the dongle drivers have not been installed. Download the drivers from http://www.tuflow.com/Downloads_Misc.htm and follow the steps in Chapter 5 of the TUFLOW manual. TuflowProblems1.doc
  • Create New...