Jump to content
TUFLOW Forum

Search the Community

Showing results for tags 'qpc'.



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 1 result

  1. The 2017 TUFLOW release notes mention that input grid extents are checked when using the "Read GRID ==" command. If the extent is outside the 2D domain the grid is skipped to reduce simulation startup. I have noticed that for quadtree models with nesting, that inputs grids are processed for each refinement level even if some grids do not fall in the refinement region. For example, a quadtree model with base 10m grid size and one 5m refinement area using DEM tiles to set Zpts. Each tile in the DEM will be processed to the 5m refinement level (GRID_TILE_X.5m.xf4) even if that tile does not fall within any part of the 5m refinement region. Does this unnecessarily increase startup times by generating xf files that aren't needed?
×
×
  • Create New...