Jump to content
TUFLOW Forum

Search the Community

Showing results for tags 'BOUNDARY'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • About This Forum and Announcements
    • How to Use This Forum
    • Forum Feedback
    • Announcements
  • TUFLOW Modelling
    • 1D/2D Linking
    • 1D Domains
    • 2D/2D Linking
    • 2D/2D Nesting
    • 2D Domains
    • Boundaries
    • Documentation & Tutorial Model
    • Dongles/Licensing/Installation
    • Ideas / Suggestions / New Features
    • Mass Balance/Mass Error
    • MATH Errors & Simulation Failure
    • Restart Files
    • Post-Processing
    • Software/Hardware Requirements
    • Text Files (.tcf, .tgc, .tbc, .ecf)
    • Utilities
    • Miscellaneous
  • Other Software
    • ISIS-TUFLOW
    • MapInfo/Vertical Mapper
    • miTools
    • Other GIS/CAD
    • SMS
    • XP-SWMM2D
    • UltraEdit/Excel
    • TUFLOW Apps

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 7 results

  1. Running the new 2020 release and have just come across the following error: 2807 trying to apply more than 1 level boundary. Can not find any literature on this error. 😞 Any guidance on rectifying this issue would be greatly appreciated. 🙏 Cheers 👽
  2. Is there any documentation on the n/m offset that can be applied to SX boundaries? Table 7-5 has the following entries: Flag f : SX: n offset for determining cell invert levels for distributing flows. Flag D : SX: m offset for determining cell invert levels for distributing flows. I can't see any other information on this in the manual or on the forum. What is it intended for and how does it work? Thanks!
  3. Hi, I've been tweaking a model over the last few months and I've just realised I have a discrepancy regarding the 2d_bc_code layer. I updated this layer to widen the model domain in a specific section of the model to improve our understanding of overland flow paths, however I have recently realised that the 2d_bc_code layer is referenced in both the .tgc and .tbc model files. I am now in the scenario of having the updated 2d_bc_code layer referenced in the .tgc file and the older superseded file referenced in the .tbc file. From the model output, Tuflow seems to be using the updated 2d_bc_code layer (so the command in the .tgc file), which I guess is why I never picked up on this oversight until now. But that raises a few questions: Is the above assumption (that the model seems to prioritise the command in the .tgc file) correct? Why are no errors raised when two different 2d_bc_code layers are referenced in the same model? Does the 'Read MI BC ==' command need to be stated in both .tgc and .tbc files and if so, why? The only variation I can find is in the .tgc file, the command is 'Read MI Code BC ==', however in the .tbc file the command is as above in the last bullet point. Is this a relic from a previous version? As above, the model output seems sensible in conjunction with the updated 2d_bc_code layer, so I am unsure of the purpose/authority of the command in the .tbc file. Any clarification would be greatly appreciated. Thanks.
  4. I've set up downstream boundaries in GPU models a number of times now using a 2d_bc HT boundary where a fixed water level below ground level is used. According to the documentation, this causes the model to apply 'normal flow' at this point, effectively behaving as an automatic HQ boundary. However, the results usually look like water is simply pouring out of the boundary, with water level and depth decreasing as they approach the boundary. This does not look like normal flow as I would have expected it and can have effects quite some distance upstream. The attached image illustrates the point. Is someone able to expand on how exactly this boundary works?
  5. jheald

    AD BC linking

    Please could you let me know if it is possible to link a 2d_bc boundary to the source term refered to in the AD BC Database so that thermal recirculation can be modelled? I would like to be able to set the temperature of an inflow (one 2d_pc point) to the temperature of an abstraction (another 2d_bc point) plus an constant value (say 7 degrees C). Many thanks, John
  6. Hi Tuflow Not sure why we are getting this error: ERROR 0103 - BC Groups not supported for .csv formats have not come across this before. our 2D GPU model bcbase files are setup the same. we are using 2d_sa buffers. thanks O-Dogs
  7. Our BC QT hydrograph is spread across a number of cells to replicate a wide floodplain flow. The flows are entering at the lowest cell along this BC. We would like to distribute the hydrograph evenly across all the cells so that the numerous flow paths are considered.
×
×
  • Create New...