Jump to content
TUFLOW Forum

dicky203

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dicky203

  • Rank
    Member
  1. Hi, I have a 2D/2D link in my model that's appears to be stable, but once the depth to about 2m the water levels upstream and downstream of the link start to diverge. To the point where the water level upstream is 0.5m higher across the link. I'm using "Link 2D2D Approach == Method B". I'm going from a 10m grid upstream to a 20m grid downstream using d=100 and a=3. I've included extra nodes where there is a change in grade. Has anyone experienced this before? Know of any reason why it's doing this? Cheers
  2. Hi Peter, I'm having issues installing the plugin. "After it installs it says Crayfish Viewer Library Not Found", but then when I click yes to download from developer website, it comes up with "Failed to Determine Installation Path." Has this happened to anyone else. We've been able to install it on other machines running Windows 7 64bit and Windows XP 64bit. This problem is unique to me (I'm running Windows 7 64bit). Cheers, Richie
  3. We've just started using SMS to create TUFLOW models and we couldn't find an option in the TUFLOW interface to create a 2d_po file to record discharge lines. Is there a way to do this in SMS or do we have to go back to MapInfo to create the file? I know there's a way to calculate discharge lines in SMS, but the PO lines would be preferable. Cheers, Richie
  4. Well, turns out it's not a TULFOW thing, it's windows xp 64bit explorer that didn't find it. The file is being written out, explorer just doesn't see it
  5. Hi, I have two tcf files that are identical except for the "BC Event Name". When they're run, one of them writes out the tlf file, messages mif/mid and csv files, the other one only wirtes out the messages mif/mid files. Is there any logical reason for this?
  6. Hi I've come accross a problem with our standalone dongle, when you close the dos shell straight after starting a simulation starts, the next time you start a TUFLOW run it can't find the dongle and just hangs after "Looking for Standalone dongle..." The only way I've found to solve this issue is to restart the computer, which is fine, unless we have other runs going using other software. It seems not everyone remembers to use ctrl+c to stop a simulation. Has anyone else had this problem? I'm using the latest version of TUFLOW, and I've tried reinserting the dongle and reinstalling the dongle drivers to no avail.
  7. Thanks for the advice. I used the 1st approach you suggested Bill and it worked very well. There's virtually no mass balance errors now at the inflow boundary. It seems to work out the flows between the 1D and 2D very nicely. I haven't tried the READ MI SA PITS but I plan to. It looks like it will achieve what I plan to. Still waiting on the hydrology.
  8. Hi Phillip, I was refereing to the top arrangement in the figure. I've attached a screenshot of my setup, hope it's clear. I've simply modelled the inflow point as a node in the 1d_nwk file. Would it work better as a pit with specified dimensions? As this first section of pipe is only conceptual to balance the flows between the 1D pipe network and 2D surface, there is no actual manhole structure that needs to be correctly replresented.
  9. I have a simple 1D/2D model which is basically a small 2D catchment with a large pipe down the middle. For my upstream boundary I want to put all the flow into the 1D pipe and allow it to surcharge onto the 2D floodplain.To do this I put a 1D QT boundary with all the flow at the node at the top of the pipe. I then connected a HX line to the same node using CN lines (figure 4-8 in the manual). This method without any additional storage at that node is very unstable. Adding additional storage stabilises the inflow a bit, but the model is still inherently unstable. Is this the correct approach to model my inflow, and if so, how do I make it stable? I also will want to add additional inflows further down the pipe. If I use the 2d_SA approach specifying [PITS] will that allow me to add an inflow to a node (or multiple nodes) whilst still allowing that node to surcharge to the 2D using the SX flag? Thanks for your help in advance
  10. I'm putting together a 1D/2D model of a large area about 14km by 4km. I'm still constructing the 2D domain and trying to get it to run with just a uniform flow. I need to use a grid size of around 5m, which makes the grid about 2800 x 800 cells. Tuflow can create the grid and read it in and process it. But when I try to use 'Read MI Zpts' to read in polygons to alter the grid, it will alter the values inside the polygons but convert all other values to 99,999. When I do exactly the same thing with a smaller grid it works fine. We don't currently have the license for multiple 2D domains. I was wondering what the best solution to this problem might be. Either splitting the model into multiple models and using the downstream boundary from one model as the inflow into the next model, or somehow getting Tuflow to process the single large grid. Any help would be appreciated.
  11. Thanks Joel, you were right. For some reason I exported the raw data.
  12. I have a large number of cross section in M11 format that I want to use in TUFLOW as part of my 1D network. I've saved the cross sections as processed data in a text file. TUFLOW opens the file and seems to be able to find the correct cross sections, but can't read the processed data. Is there something I need to do to the text file before I use it in TUFLOW rather than just using the exported data from MIKE11? An example of a cross section straight out of MIKE11 is below: topo_id1 STONY CREEK 7050.000 COORDINATES 0 FLOW DIRECTION 0 DATUM 0.00 RADIUS TYPE 2 SECTION ID PROFILE 13 0.000 25.960 1.000 <#1> 8.120 25.790 1.000 <#0> 8.710 25.860 1.000 <#0> 9.190 25.850 1.000 <#0> 10.210 25.830 1.000 <#0> 11.140 23.690 1.000 <#2> 11.220 23.750 1.000 <#0> 12.010 24.420 1.000 <#0> 13.380 25.310 1.000 <#0> 18.500 25.720 1.000 <#0> 19.040 25.700 1.000 <#0> 20.000 25.760 1.000 <#0> 27.000 26.400 1.000 <#4> *******************************
×
×
  • Create New...