E.4 Possible workflow #2
The following is a possible addition to the workflow presented in Section E.3 for the two modellers delivering the same use case. Instead of the modellers working entirely independently until post calibration, it includes occasional provision of interim catchment inflows from the TUFLOW HPC modeller to the TUFLOW FV modeller to assist in calibration of the latter under wet conditions. This is accomplished by:
- Merging sufficiently complete HPC and FV branches into the main branch to produce a TUFLOW CATCH Integrated configuration simulation from time to time, instead of only at the end of individual calibration tasks
- Executing TUFLOW CATCH in Integrated configuration to produce all spatially and temporally resolved boundary inflows for TUFLOW FV
- Add, commit and push the boundary files to the main branch
- Copy the boundary files (including header blocks (.fvcatchbc) and data files (.csv)) to the
\TUFLOWCATCH\bc_dbase\ folder in the FV branch being used by the TUFLOW FV modeller for subsequent access - Rename the *.fvcatchbc file to be the same as the TUFLOW FV modellers *.tcc file name so that it is automatically found by the current *.tcc simulation
- Rerun the TUFLOW FV modeller’s *.tcc simulation, adding the command below inside the Receiving Model block so that blank catchment boundary files (the default) are not produced and so do not overwrite those developed in the above Integrated TUFLOW CATCH simulation
- The TUFLOW FV modeller can then continue the calibration process with revised inflows. The above process can be repeated at intervals that suit the modelling project and timelines.
- Once complete, the HPC and FV branches can be finally merged, and the full TUFLOW CATCH simulation executed
