2.2 Intention

The intention of the execution coordination sequences described below is that they provide a robust means to automatically link catchment and receiving waterway models within three overarching configurations to support integrated environmental assessment. It is noted that this architecture deliberately:

• Supports multiple users working on a project simultaneously by allowing (from the same TUFLOW CATCH control file, see Section 4.5):
  • Simulation of TUFLOW HPC without needing to execute TUFLOW FV, and/or
  • Simulation of TUFLOW FV without needing to execute (or repeatedly execute) TUFLOW HPC
• Aligns with the use of version control platforms to support multi-user co-development. Such use was intended as part of designing TUFLOW CATCH’s architecture, and it means that the same TUFLOW CATCH control file can be used by multiple users to initially independently drive TUFLOW HPC and TUFLOW FV model builds. When appropriate, version control techniques can then be used to unify model builds. This approach avoids the need to build disparate TUFLOW HPC and TUFLOW FV models, and then recast these into a TUFLOW CATCH control file framework: co-development is a core design feature of TUFLOW CATCH.