Jump to content

tuflow support

  • Content Count

  • Joined

  • Last visited

Everything posted by tuflow support

  1. Q: We have a standalone dongle but it seems to be looking for a server in the middle of the run. The message is "TUFLOW Engine Server could not be found". Why is TUFLOW looking for a server and how can I fix this? A: The message that the server isn’t found refers to the codemeter server (not a network server). This can happen when the connection to the dongle is lost. We have noticed that some issue have occurred with the USB ports on the front of the computer or via a USB hub and this is rectified by plugging the dongle in at a USB port at the back of the computer. This USB ports at the back of the computer are directly on the motherboard and are prefferable to ones on the front. If this error occurs, we would recommend unplugging the dongle and trying a USB port at rear of computer. The CodeMeter server should pick up the dongle and hopefully the TUFLOW simulation will continue.
  2. Further to the post above. Q: So you can still run MapInfo and other software on a 64 bit O/S? That is, we don't need special versions of all our other software? A: That is correct, I am running a 64-bit laptop, on which I run all TUFLOW related software: MapInfo, UltraEdit and SMS and general software (office, ArcGIS, Matlab etc). Some of these do offer 64-bit versions, for example SMS, Matlab and even internet explorer! I suspect that 64-bit software will become more prevalent as computers transition to 64-bit. A 32-bit system can only recognise ~4Gb of RAM (2^32) and so I think the future of computing will be 64-bit!
  3. Q: We are in the process of updating our hardware. While we can get high spec machines from our supplier, we also have the option of buying a PC externally as we are keen to optimize performance. I'm wondering if TUFLOW is perhaps optimized for a particular types of processor, RAM, motherboard, etc, etc. Based on the 2010 release, what is the best PC specification to run TUFLOW? A: The best PC spec for TUFLOW is a much asked question (and there are a number of posts here on the TUFLOW forum in the hardware requirements section). TUFLOW is not optimized for a particular type of processor, MB or RAM. We investigated different CPUs here when we brought a modelling computer recently. We tested a number of computers here to guide our decision making, basically the long and short of it is, the faster the CPU (clock frequency) the quicker the models will run, the more cores available the more concurrent simulations you can run (limited by the number allowed with your TUFLOW licence). Depending on the amount and size of the models running you will need to ensure you have adequate RAM available to process these. The 2010 version of TUFLOW is released as both a 32-bit and 64-bit executable. To access larger amounts of RAM (more than ~1.8GB per simulation) you will need the 64-bit version of TUFLOW. To run this you will need a 64 bit operating version of Windows. There is also a run-time advantage with the 64-bit version compared to the 32-bit version. The 2010-10 64-bit version of TUFLOW is typically 30-50% faster than the 2009-07 32-bit version of TUFLOW. The computer we decided on was a dual 6-core i7-980x (12 physical cores, with Hyper-threading enabled this runs 24 processes). As we had a number of very large simulations using multiple GB of memory each we got a large amount of RAM installed (96GB). We haven’t overclocked any of our modelling PCs (our IT dept. has been a bit hesitant about this). However, if you know what you’re doing, I’m sure that overclocking the CPU (increasing the clock frequency) should allow simulations to run faster. I know some high end PC builders will sell overclocked machines (some even offer water-cooled systems). I can’t really comment on this as I haven’t had experience running TUFLOW on anything like this! So in summary I would definitely recommend a 64 bit O/S, enough memory for your requirements (keeping in mind your models will probably increase in RAM requirements), if you are planning on running 4 concurrent simulations using 2GB of RAM, I would look at getting 12GB not 8Gb (the OS will use some as will MapInfo and other open software). The clock speed will affect how fast the simulations run.
  4. Hi All, TUFLOW Support has been in contact with Anita about the decreasing flows along the 1D network, the issue was caused by the downstream end of the pipe network not being connected to either the 2D domain or an external boundary. Thus the end of the pipe was sealed, causing water to surcharge from the pipe to the 2D domain in the upstream pits, resulting in the diminishing flow in the pipe network. Once this was rectified the model began behaving as expected. Regards TUFLOW Support Team
  5. Q: We are currently using XP machines, and are upgrading all of our machines to Windows 7 - is this going to be a problem with the TUFLOW software. A: TUFLOW should be compatible with Windows 7, the only known issues with running TUFLOW on windows 7 are: Right Click Functionality The right click functionality in Windows 7 is a bit different to previous version of Windows. Thus the process is different to setup than is detailed in the TUFLOW manual. It can be setup by manually editing the registry. However, there is a free utility called FileMenu Tools which is a very simple way of setting up this functionality. For more info see this forum topic: http://www.tuflow.com/forum/index.php?showtopic=764 Simulation Log Path Windows 7 has some additional levels of security. Earlier versions of TUFLOW wrote a log file to the C:\ (root directory of the C drive), this can cause issues with Windows 7. This may require the user to change the directory this log files is written to (it can be disabled) or run TUFLOW as administrator. The simulation log file can be changed in TUFLOW and by default the 2010 release writes this file to C:\BMT_WBM\log\ to avoid this problem. For discussion on this issue see this post on the TUFLOW forum: http://www.tuflow.com/forum/index.php?showtopic=692 64-bit TUFLOW If you are running windows 7 64-bit and wish to run a 64-bit version of the TUFLOW executable, you will require a 64-bit compatible Wibu (metal) dongle. Please see here for more information: http://www.tuflow.com/forum/index.php?showtopic=781 As mentioned in that thread the SoftLok dongles and 32-bit versions of TUFLOW work fine on 64-bit Windows platforms, so if you're upgrading your hardware to a 64-bit machine, you do not have to upgrade to a WIBU dongle unless you want to utilise 64-bit versions of TUFLOW. Regards TUFLOW Support Team
  6. Hi All, We have been in contact with Anita about this and the issue is occuring because no "Name" column is being found in the Pit Inlet Database. In the TUFLOW manual (which Anita was following) the first column header is "Inlet_Type", this should match the inlet type in Inlet_Type attribute of the 1d_nwk layer. However, TUFLOW is searching for a "Name" header not "Inlet_Type". Once this was changed, the model started. In the attached image, cell reference A1 should be"Name", not "Inlet_Type". This will be corrected, so that either TUFLOW accepts Inlet_Type or the TUFLOW manual is updated. Regards TUFLOW team.
  7. Q: I thought I could put 1d inflow anywhere along the length of a pipe and not at the start or end of the pipe in Tuflow. When I attempt to do that, an error occurs. I thought I had tried that using a very old version of Tuflow and it worked. Now, the latest version doesn’t allow it. Is that right? A: No, inflows have always only been allowed at the ends of channels/pipes. This is because the mass equation (which deals with in/outflows) is applied at the nodes (channel ends) and the momentum or structure equation is applied along the length of the channel. You can break a channel up into segments (thereby creating more nodes for inflow points), by simply breaking up the channel into two or more lines. Since the 2008-08 release, cross-sections and inverts are automatically interpolated making it much easier to do this. For pipe networks, usually the pipe channels extend from one inflow point (or manhole) to the next (eg. from a pit inlet chamber to the next one), so the need for breaking up the pipe line is usually not needed. You can easily distribute a hydrograph to two or more nodes by using a polygon (instead of points) in a 1d_bc layer.
  8. Q: I'm getting the message below. It works fine in the 2009-07 release, but not in 2010-10-AA. ERROR 0252 - .\model\ is not a supported file format for the last command. A: If you add ".mif" to the GIS layer in the line below from your .tgc file it should work fine in 2010-10-AA (there may be other files as well). (Also see note below for 2010-10-AB which will allow you to leave the line below as is.) Read MI Z line THICK MAX == mi\2d_zline_banks_001 In 2010 TUFLOW uses the file extension to decide which format the layer is (eg. .mif or .shp). Leaving as a blank extension is theoretically still allowed (TUFLOW assumes it is a .mif format if blank), except this doesn’t work if there is a “.” anywhere in the pathname. Whilst there is no "." in the pathname above, the folder path to the control file (eg. .tgc file) is added to the the GIS pathname and a "." can occur if you have a “..\..” in the relative pathname to the .tgc file or if there is simply a “.” in the folder or file name. For 2010-10-AB, the extraction of the file extension has been improved so that it only considers the filename (ie. excludes any folder names), therefore so long as there is no “.” in the filename besides the one defining the extension, you can leave the .mif off in your TUFLOW command if you so choose for Build 2010-10-AB or later.
  9. Q: I'm getting the error below when running the 2010-10 release, but not with the 2009-07 release when processing a Read MI Z Shape command. “ERROR 2232 - Failed to complete triangulation. Check region perimeter does not cross or snap onto itself.” A: This was due to a polygon being digitised so that it’s perimeter crosses onto itself as shown in the attached image (the blue circles highlight the problem areas). The 2010-10 release tests for this more thoroughly than the 2009-07 release, hence why it occurs in 2010 and not 2009. With the polygon perimeter cleaned up, the 2010-10 release works fine.
  10. Q: Is an updated TUFLOW tutorial model planned? A: We have been working on the tutorial model; there have been a number of improvements in TUFLOW since the tutorial model (version 003) was created. We are updating the tutorial model to take into account the additional features of newer TUFLOW builds and also to include additional modules, such as direct rainfall modelling, source area inputs from a hydrological model (such as RAFTS), urban modelling (inlet pits), variable z shape modelling of a “levee breach”, modelling of pumps and advanced modelling of boundary databases (e.g. one .tcf for multiple simulations). If you have any specific things you would like to see in the updated tutorial model, now would be a good time to provide suggestions below! However, before we complete the tutorial model we are finalising a Wikipedia (“wiki”) database of all TUFLOW messages (error, warning and check messages). This database has been planned for a while, and will include a description of why the message occurs and suggestions on correcting the issue. We are trying to get the wiki database finalised before finishing the tutorial model. Once we have the wiki finalised, we will progress the tutorial model and an announcement will be made on the website and TUFLOW forums when the updated tute model is available for download. See attached image for example of the TUFLOW wiki. Regards TUFLOW Team
  11. Q: When I try and run the 64 bit version of the 2010 release of TUFLOW I get the following error: The application has failed to start because wibucm64.dll was not found. Re-installing the application may fix the problem. A: This occurs if you try and start a 64 bit version of TUFLOW without the Wibu dongle drivers installed. In order to run a 64 bit version of TUFLOW you will need to be using a Wibu dongle. The previous (softlok) dongle providers failed to provide 64 bit support (one of the main reasons we have changed dongle providers). The Softlok (blue) dongles will continue to be supported for future 32 bit versions of TUFLOW. For more info on the dongle exchange process please see: http://www.tuflow.com/forum/index.php?showtopic=781
  12. We have recently come across an old parallel port TUFLOW dongle not being recognised when the Dongle Drivers 003 are installed (despite the dongle working on other computers). Uninstalling the 003 version of the drivers and installing the previous Dongle Drivers 002 fixed the problem. If you are having trouble with an parallel dongle this might be worth a try. The 002 drivers can be downloaded from http://www.tuflow.com/Downloads/Releases/D...Drivers.002.zip
  13. Just to update the forum, we had a look at this issue and the cause was the the Map Output Format == SMS High Res (in the tcf). This higher resolution output is not yet not yet recognised by the TUFLOW_to_GIS.exe (but we are looking to update this). Regards TUFLOW Support
  14. Hi Simon, Can you please email support@tuflow.com and I will give you some FTP details for you to upload the relevant files and I'll take a look. Thanks TUFLOW Support team
  15. Q: I am enquiring about the computer requirements needed to run TUFLOW. I want to know what the minimum and the recommended requirements are. A: In terms of minimum computer specs this is highly dependent on the size and number of TUFLOW models being run. You can still, for example, run a small (by today's standards) TUFLOW model on an old Pentium 3 with Windows 95! If purchasing a new computer as of 2010, the preferred option is probably a recent Core 2 Duo if buying a 32-bit machine and the number of TUFLOW runs is small, otherwise for large models (millions of cells) and/or many simulations, run with a 64-bit machine with 64-bit operating system and 4 or more cores (the i7 and AMD chips are worth considering). One thing to note if using a standard TUFLOW standalone licence is that the number of cores exceeds four TUFLOW limits the number of simulations to four at any one time. Standalone licences can be increased to cater for 8, 16, ... cores at an additional cost. If using network licences the limiting of the number of TUFLOW runs on one machine does not apply, but you might be limited by the number of available network licences (ie. one network licence per simulation). As a general rule, if running very large models that exceed around 1.8Gb in RAM, then you'll need to move to a 64-bit machine with a 64-bit O/S. If running several large models at once and you exceed your RAM limit, the runs will slow down markedly as the computer starts using Virtual (HDD) memory. A user the other day indicated that running TUFLOW 64-bit was 30 to 50% faster than TUFLOW 32-bit, so there may well be some speed gains starting to appear if using 64-bit. We'll be doing our own benchmarking on this with the release of the 2010 64-bit TUFLOW. For the HDD, generally the standard issue are usually more than fine. The exception would be if producing a huge amount of output, in which case go for the largest HDD size. Solid-state drives may give some nominal speed gains. For RAM always have plenty even if running small TUFLOW models because other software (eg. MapInfo/ArcGIS/SMS) can use large chunks of RAM, especially if aerial photos and Lidar data are open. Minimum RAM for 32-bit is 2Gb, but would recommend 4Gb and for 64-bit have a minimum of 4Gb, but recommend 8Gb or possibly more if running very large models or a lot of simulations. (Also see http://www.tuflow.com/forum/index.php?showtopic=62).
  16. Q: TUFLOW has errors with the memory being allocated on the x64 Windows 2003 server as shown in the attached image . The server physically has 8Gb of RAM, and the windows page file is set to double that physical size. How does TUFLOW utilise system memory? A: If TUFLOW is trying to allocate a negative memory as in the case shown, this will occur for VERY large models using TUFLOW builds prior to the 2009-07 release (see Point 16 in the 2009-07 release notes which is copied below). In these situations, you'll most likely need to be running on a x64 O/S (to access extra RAM), and will need to be using Build 2009-07 or later. If memory allocation exceeds around 2.5Gb, you may need to use the 64-bit compiled version of TUFLOW available from TUFLOW Executables. Point 16 from 2009-07 Release Notes: "Integer pointers for memory allocation have been increased from 4-bytes to 8-bytes, which was necessary for correct RAM allocation for HUGE models (these models would typically request a negative memory amount in previous builds). The 8-byte pointers allow models to have up to 9,223,372,036,854,775,807 real values rather than the 2,147,483,647 values previously using 4-byte integers. (When the pointers were first coded in 1989, it was never imagined that they would be exceeded!!!! The question now is will we ever exceed 9,223,372,036,854,775,807 values?)."
  17. Q: I have an ISIS/TUFLOW model that runs fine using version 2008-08-AI-iSP. However, once I include a ZSH polygon the model refuses to start up and comes up with the following error: ERROR 2220 - Read MI Shape commands can only be used if "Z Line Cell Selection == Method D". I have tried setting the Z Line selection to method D however, this has no impact. A: In the .tlf provided it would appear that “Line Cell Selection == METHOD A” is being used, the default for the 2008-08 build is Method D. This command is not being read into the .tcf. However this command is also set if you have the Defaults == pre 2006-06. To overcome this you can add either the “Line Cell Selection == Method D” (which will change both boundary cells and Z line cells) or “Z line Cell Selection == Method D” which will only change Z lines. I would recommend adding the first, this way any HX Lines with Z lines will select the same cells. These commands need to be read after the Defaults == pre-06-06 and will cause the model to use the new cell selection process (Method D).
  18. Q: I need to download some old versions of Tuflow, however, I cannot find them on the website. Please can you direct me to where I can download these versions of Tuflow from? A: Most old versions of TUFLOW remain available. To see if you can download one, follow these steps: 1. Right click on one of the current TUFLOW downloads and select "Copy Shortcut" or "Copy Link" (depends on your browser). 2. In the address bar of your browser, paste in the link. For example: "http://www.tuflow.com/Downloads/Releases/TUFLOW.2009-07-AE-iSP.zip". 3. Edit the link to the build you are after, for example, if you are after Build 2008-08-AF-iDP, edit the link above to "http://www.tuflow.com/Downloads/Releases/TUFLOW.2008-08-AF-iDP.zip" and press return. If the download exists, you will be prompted to open or save the .zip file. If so, proceed as per usual to setup that build of TUFLOW. Note that for builds prior to 2008 there is no iSP or iDP in the Build ID. Clearly, the use of old builds should be confined to established models where there is a requirement to be consistent with simulations previously carried out.
  19. The below is from an email chain in April 2008: Q: Our ten user network dongle has stopped working. Please could you help? When we run TUFLOW we receive the following error message: Looking for Network Dongle Server...started...Serial no: 7049595 ERROR – Dongle is invalid for this build or model, or is unmaintained. Please contact support@tuflow.com and provide dongle details above. Is this associated with a maintenance agreement for the dongle? Please could you let me know what we need to do to get the dongle working again? [Further investigation showed that an incorrect serial number was being returned. After sending the response below through the reply was "We completed step 1 of your instructions. It was only necessary to update wdrvr.dll on the server machine. Everything then worked fine so we did not need to proceed any further." ] A: This is a rare problem that we've had and that the dongle providers believe they have sorted with the release of Dongle Drivers.003 (see http://www.tuflow.com/forum/index.php?showtopic=307). Can you (or IT) please do the following. 1. Either download and reinstall the dongle drivers from Dongle Drivers.003.zip. Reinstall the drivers or you may have to follow the following advice from the dongle providers: "Essentially you need to replace the wdrvr.dll with the new one (dated 19/2/2008). Normally this is in the windows/system32 folder but make sure there are no ther copies of wdrvr.dll elsewhere. It is also worth rebooting afterwards." You'll probably need to do this to both the server and client machines. See if this has solved the problem. If not, also try the next step. 2. Change the following registry setting (probably on both server and client machines to be safe) to see if it solves the problem. HKEY_CURRENT_USER/Software/SIL/Wd/1.0/OPT4 Set the OPT4 value to be binary type with just one hex byte of FF Note that you may not see an OPT4 key and that another site changed the OPT2 setting to FF to solve the problem.
  20. Q: I wish to represent the culvert exit losses from a flap valve using the following equation. HL = 0.3*V*V/(2g) + 0.125 At the moment, this culvert is 60m long and represented in Estry within TUFLOW as Rectangular unidirectional culvert. Are the only parameters we can adjust in estry to represent a flap valve on the downstream end of the culvert is to adjust the exit loss coefficient? And how do I represent a constant head loss which doesn’t vary with velocity? A: To apply the 0.3*V2/2g component of the exit loss you'll have to specify 0.3 for the 1d_nwk Exit_Loss attribute. Note that if you are using the default TUFLOW settings then "Structure Losses == ADJUST" is used, which will reduce the 0.3 value according to the culvert and downstream velocities (see Section of the 2008 TUFLOW manual). This is not what you want, so either "Structure Losses == FIX" needs to be specified in the .ecf file (this will affect ALL culverts), or add an "F" to the 1d_nwk Type attribute (ie. use "RUF" instead of "RU") to fix the losses just for that culvert. It's not possible to simply apply a 0.125m head loss (head or energy loss at a culvert exit must be a function of V2/2g).
  21. Q: On trying to run an ISIS TUFLOW linked model I am receiving an error saying "Initializing libiomp5md.dll, but found libguide40.lib already initialized". This error appears in a DOS window and is followed by further text regarding performance degradation and forcing the model to run. I am using ISIS version and TUFLOW build 2009-07 iSP. A: You'll probably have to run ISIS 3.3 with TUFLOW 2009-07. We haven't heard of any issues, but ISIS 3.1 and TUFLOW 2009-07 maybe incompatible due to changes made to both software as mentioned for Build 2009-07-AB (see http://www.tuflow.com/Release_Notes_2009_07.htm#2). See http://www.isisuser.com/forum/topic.asp?co...ast&tid=121 regarding the conflict between the two dlls.
  22. Q: I am having difficulty using the TUFLOW_to_GIS.exe executable with the –cp command. Regardless of what I try I always receive an error stating: ----------------------------------------------------- ERROR – Could not read the following line in .mid file – check for correct attributes 0 Press Enter to Close ---------------------------------------------------- Would it be possible to either obtain a point file which works with the –cp command, or be informed of the required structure of the point file? A: This will be due to using a long dash "–" as opposed to a short dash (minus sign) "-". When copying and pasting from Word in particular tends to replace short dashes with long dashes. Also see: http://www.tuflow.com/forum/index.php?showtopic=491 and http://www.tuflow.com/forum/index.php?showtopic=278
  23. Note that as of Build 2007-07-AA, the Security Server can be exited and restarted while there are simulations (of this build or later) underway. This allows any ghost licences to be cleared (ghost licences are unreleased licences that occur on some networks when the network is disconnected from a computer running a TUFLOW simulation). TUFLOW Build 2007-07-AA or later enters a 3 minute holding pattern until a spare network licence becomes available. At present the only way to remove these ghost licences is to restart the TUFLOW Security Server (which can be done even if there are simulations running as TUFLOW, Build 2007-07-AA or later, keeps checking for a network licence until it finds one). Different networks seem to yield different outcomes in terms of the generation of ghost licences.
  24. Q: I have been trying to setup Tuflow on a new computer with a standalone dongle. I believe that Tuflow has been installed correctly however I think there may be a problem with the dongle drivers. I have been able to create empty files using Tuflow so am confident that the Tuflow side of things isn't the issue. When I go to the next statge of trying to create z points, an error message comes up saying that no standalone dongle could be found (or network dongle but since we are not using a network dongle then that is irrelevent to this querry). I have looked at the manual which suggests reinstalling the dongle drivers. I have downloaded the latest dongle drivers from the website but when I try to install (or uninstall), a message saying "error installing driver" pops up. Note that i have tried using various USB ports for the Tuflow dongle. If you could let me know what I can do to overcome this then that would be greatly appreciated. A: The only known reason for the above to occur is that you need to have Administrator privileges to install the dongle. Please check that you have this and try again. If the problem persists, please get back to us.
  25. Q: Have I interpreted the instructions correctly to copy a model? I started Tuflow the way I normally do and as instructed in the Manual/Tutorial, ie set Windows up such that right clicking on the .tcf filename in explorer brings up a floating menu that contains the option to Run Tuflow at the top. Normally, just pasting my .tcf filename into the command line would start a simulation on my workstation setup. A: If you're using the right click option you should have in the New Action dialog something like the below to run TUFLOW. Note by adding "%1" (including the quotes) after the path to TUFLOW.exe (make sure there is space in between) this inserts the .tcf filename in automatically for you, ie. you don't have to enter/paste the .tcf filename in the DOS prompt as you have been doing. To set it up to copy a model add another action something like the below noting the -c option must have spaces either side. Once you've done this, when you right click you should have both the Run and Copy options available to choose from. You can also add as many other options as you want (eg. to run other TUFLOW builds such as the iDP build or an older build).
  • Create New...