Jump to content
TUFLOW Forum

Search the Community

Showing results for tags 'source'.



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 2 results

  1. I am currently testing existing regional flood models using the HPC solver. Most of these models have source inflows applied using traditional SA inflows. While switching to the HPC solver in the control files is easy - overcoming the limit applied to source inflows on individual cells (4 source inflows in total) becomes problematic, especially when the messages layer in the log files does not show specifically where there are too many inflows applied. Can anyone suggest a quick workaround?
  2. I am currently testing existing regional flood models using the HPC solver. Most of these models have source inflows applied using traditional SA inflows. While switching to the HPC solver in the control files is easy - overcoming the limit applied to source inflows on individual cells (4 source inflows in total) becomes problematic, especially when the messages layer in the log files does not show specifically where there are too many inflows applied. Can anyone suggest a quick workaround?
×
×
  • Create New...