Jump to content
TUFLOW Forum

ottreyg

Members
  • Content Count

    5
  • Joined

  • Last visited

Community Reputation

0 Neutral

About ottreyg

  • Rank
    Member
  1. Have found out what the issue was, vertical mapper was installed but not properly loaded when trying to use the tool. its now working exactly as it should.
  2. Hi I have tried using the create csv from vertical mapper grid tool to create ~60 cross sections. each of the cross sections is named "XS1.csv, XS2.csv etc" with the type specified as XZ. i have set the mannings roughness to "Don't Vary Roughness" and the distance between sampling spacing to 0.2 m. Vertical mapper is installed and working on the computer and many of the other mitools have also worked however i get the attached error message when trying to use the csv from VM grid tool. I have done a search for the file mentioned and it is located in "C:\Program Files (x86)\MapInfo\VerticalMapper" folder which seems like a logical enough spot for it to be. The computer is a 64 bit machine running Windows 7 and mapinfo version 10.0. Has anyone else had this problem or have any ideas on how to fix it? Cheers Glenn
  3. Hi Phillip Thanks for the quick reply. its always the simple things - updated everything expect the reference in the tcf to the updated tgc *facepalm*. appears to be working a treat now. Cheers Glenn
  4. Hi All I'm having some trouble with an automatic slope specified HQ boundary. At the downstream end of the model I have set up a couple of HQ boundaries type boundaries with a b attributes of 0.01 (aiming for a 1 in 100 slope). no other attributes have been used. i had this boundary condition working, however after running the model decided that it was not in quite the right place and tried to move it ~30 m Down Stream to a different location. Tuflow is now giving the error "ERROR 2194 - Column 1 values not ascending in HQ table". given that Tuflow is calculating the flow values i'm not sure how to overcome this and get them into ascending order? i have placed the boundary conditions in localised gullies and have them snapped to the code layer. i was able to get one of the boundary conditions to work by copying the data from the 2d_bc_table_check.csv into a boundary condition file and changing the second flow value from 0 to 0.001 so that they all did increase, then manually setting it in the bc database. the other boundary however cannot be fixed in the same way as the info below from the 2d_bc_table_check.csv shows that the flow does not increase at all (see below). has anyone encountered this problem before or have any further information on how Tuflow calculates the automatic boundary conditions? i have used tuflow build 2010-AF double precision. BC000022: HQ BC Automatically generated using a water surface slope of 0.01 Point Flow (m3/s) Water Level (m) 1 0 11.502 2 0 11.512 3 0 11.522 4 0 11.532 5 0 11.542 6 0 11.553 7 0 11.562 8 0 11.572 9 0 11.582 10 0 11.592 11 0 11.602 12 0 11.612 13 0 11.622 14 0 11.633 15 0 11.643 16 0 11.652 17 0 11.662 18 0 11.672 19 0 11.682 20 0 11.692 21 0 11.702 22 0 11.713 23 0 11.723 24 0 11.732 25 0 11.742 26 0 11.752 27 0 11.762 28 0 11.772 29 0 11.782 30 0 11.792 31 0 11.803 32 0 11.812 33 0 11.822 34 0 11.832 35 0 11.842 36 0 11.852 37 0 11.862 38 0 11.872 39 0 11.883 40 0 11.893 41 0 11.902 42 0 11.912 43 0 11.922 44 0 11.932 45 0 11.942 46 0 11.952 47 0 11.963 48 0 11.973 49 0 11.982 50 0 11.992 51 0 12.002 52 0 12.012 53 0 12.022 54 0 12.032 55 0 12.043 56 0 12.053 57 0 12.062 58 0 12.072 59 0 12.082 60 0 12.092 61 0 12.102 62 0 12.112 63 0 12.122 64 0 12.133 65 0 12.143 66 0 12.152 67 0 12.162 68 0 12.172 69 0 12.182 70 0 12.192 71 0 12.202 72 0 12.212 73 0 12.223 74 0 12.232 75 0 12.242 76 0 12.252 77 0 12.262 78 0 12.272 79 0 12.282 80 0 12.293 81 0 12.303 82 0 12.312 83 0 12.322 84 0 12.332 85 0 12.342 86 0 12.352 87 0 12.362 88 0 12.372 89 0 12.383 90 0 12.393 91 0 12.402 92 0 12.412 93 0 12.422 94 0 12.432 95 0 12.442 96 0 12.452 97 0 12.462 98 0 12.473 99 0 12.482 100 0 12.492 101 0 12.502 102 0 12.522 Thanks Glenn
  5. Hi all I have a model where i have setup a HQ boundary using the b attribute to generate a slope (0.01 for an approximate 1 in 100 slope) on one of the downstream edges of the model. At one location the boundary is adding water to the model at the same time as removing it in another spot. The HQ boundary is fairly long ~1000 m on a 3 m grid and i am using a depth variable mannings due to the top of the catchment being very steep. I tried trimming the end off it where it was adding water but it has just moved a bit further up the boundary to another spot. I have attached a screenshot from SMS which shows vectors and depth, showing that flow is both leaving and entering the model from the same boundary. Does anyone have any ideas how/why this happens? I wanted a boundary condition that will remove the flow from the model, while the exact rate of removal is not massively important as i have moved the boundary away from the area i am interested in mapping (~100 m horizontally and a few meters vertically) - I would like it to be in the right order of magnitude but as long as water leaves that would be fine. Should I be using a different boundary type? A HT would be difficult as the ground is not at one level along the whole length of the boundary. i notice that other people have had some queries with understanding HQ boundaries on the forum as well. http://www.tuflow.com/forum//index.php?showtopic=182&st=0&p=2313&hl=+hq%20+boundary&fromsearch=1&#entry2313 any ideas or insight into why the boundary might be behaving in this way would be appreciated. Glenn
×
×
  • Create New...