6.2 Core supported configurations
The three core supported configurations of TUFLOW CATCH are:
- Hydrology
- Pollutant export
- Integrated
The outputs of these are described in the following sections. In all cases, the TUFLOW CATCH control file is assumed to be named Model_001.tcc. It is strongly recommended that TUFLOW HPC and TUFLOW FV results that are to be used to create a TUFLOW CATCH *.json file for viewing in QGIS are output at the same timestep, referred to as <common_dt> below.
Units for all constituents, where relevant, have been set as standard (typically mg/L) to accord with commentary provided in Sections 4.5.3.1, 4.5.3.2 and 4.5.3.3.3.
6.2.1 Hydrology
6.2.1.1 Data types
It is recommended that the following data types be set, assuming salinity and temperature are included as constants/timeseries. If not, then catch (TUFLOW HPC) and , sal, temp (TUFLOW FV) can be omitted. If soil layers are not simulated then GW_QZ and GW_QZI should also be omitted (doing so will also reduce output file size if necessary):
TUFLOW HPC
TUFLOW FV
6.2.1.2 Files
The following output files are produced in the execution of a hydrology simulation with data types as above. Each is a 2D or 3D (TUFLOW FV) map output that varies in time:
- TUFLOW HPC
- Model_001_catchment_hydrology.xmdf
- Bed Elevation
- Depth
- Vector Velocity
- Velocity
- Water Level
- Time of Peak h
- GW QZ Layer 1
- GW QZI Layer 1
- Model_001_catchment_hydrology.xmdf
- TUFLOW FV
- Model_001_receiving_HD.nc
- Bed Elevation
- salinity
- temperature
- velocity
- vector Velocity
- water depth
- water surface elevation
- Model_001_receiving_HD.nc
6.2.1.3 Interrogation
The above output files can be viewed either:
- Individually via the TUFLOW Viewer (File -> Load Results -> Map Outputs), and interrogated using usual TUFLOW Viewer techniques, or
- Simultaneously via use of the Create TUFLOW Catch JSON function demonstrated in the eLearning material described in Section 4.3
6.2.2 Pollutant export
In this example, it is assumed that two pollutants are simulated (in addition to temperature and salinity), as:
- PFAS, Washoff1 pollutant export model
- Tailings, Shear1 pollutant export model
These models have been chosen because they produce different outputs.
6.2.2.1 Data types
It is recommended that the following data types be set:
TUFLOW HPC
TUFLOW FV is not activated.
6.2.2.2 Files
The following output files are produced in the execution of a pollutant export simulation with data types as above. Each is a 2D map output that varies in time. Hyperlinks are provided to detailed descriptions in the appendices for representative pollutants:
- TUFLOW HPC
- Model_001_catchment_hydrology.xmdf
- Bed Elevation
- Conc PFAS
- Conc TAILINGS
- Dry Mass PFAS
- GW Layer 1 Conc PFAS
- GW Layer 1 Conc TAILINGS
- GW Layer 1 MZ PFAS
- GW Layer 1 MZ TAILINGS
- GW Layer 1 MZI PFAS
- GW Layer 1 MZI TAILINGS
- Net Mass TAILINGS
- Depth
- Vector Velocity
- Velocity
- Water Level
- Time of Peak h
- GW QZ Layer 1
- GW QZI Layer 1
- Model_001_catchment_hydrology.xmdf
6.2.3 Integrated
In this example, it is assumed that one sediment fraction and inorganic simulation class water quality are simulated (in addition to temperature and salinity), as:
- oxygen, silicate, adsorbed phosphorus and phytoplankton as constants
- all other water quality pollutants, Washoff1 pollutant export model
- fines, Shear1 pollutant export model
- salinity, constant
- temperature, timeseries
These models have been chosen because they produce different outputs.
6.2.3.1 Data types
It is recommended that the following data types be set:
TUFLOW HPC
TUFLOW FV
6.2.3.2 Files
The following output files are produced in the execution of an integrated simulation with data types as above. Each is a 2D or 3D (TUFLOW FV) map output that varies in time. Hyperlinks are provided to detailed descriptions in the appendices for representative pollutants:
- TUFLOW HPC
- Model_001_catchment_hydrology.xmdf
- Bed Elevation
- Conc SED_FINES
- Conc WQ_AMMONIUM_MG_L
- Conc WQ_DOC_MG_L
- Conc WQ_DON_MG_L
- Conc WQ_DOP_MG_L
- Conc WQ_FRP_MG_L
- Conc WQ_NITRATE_MG_L
- Conc WQ_POC_MG_L
- Conc WQ_PON_MG_L
- Conc WQ_POP_MG_L
- Dry Mass WQ_AMMONIUM_MG_L
- Dry Mass WQ_DOC_MG_L
- Dry Mass WQ_DON_MG_L
- Dry Mass WQ_DOP_MG_L
- Dry Mass WQ_FRP_MG_L
- Dry Mass WQ_NITRATE_MG_L
- Dry Mass WQ_POC_MG_L
- Dry Mass WQ_PON_MG_L
- Dry Mass WQ_POP_MG_L
- GW Layer 1 Conc SED_FINES
- GW Layer 1 Conc WQ_AMMONIUM_MG_L
- GW Layer 1 Conc WQ_DOC_MG_L
- GW Layer 1 Conc WQ_DON_MG_L
- GW Layer 1 Conc WQ_DOP_MG_L
- GW Layer 1 Conc WQ_FRP_MG_L
- GW Layer 1 Conc WQ_NITRATE_MG_L
- GW Layer 1 Conc WQ_POC_MG_L
- GW Layer 1 Conc WQ_PON_MG_L
- GW Layer 1 Conc WQ_POP_MG_L
- GW Layer 1 MZ SED_FINES
- GW Layer 1 MZ WQ_AMMONIUM_MG_L
- GW Layer 1 MZ WQ_DOC_MG_L
- GW Layer 1 MZ WQ_DON_MG_L
- GW Layer 1 MZ WQ_DOP_MG_L
- GW Layer 1 MZ WQ_FRP_MG_L
- GW Layer 1 MZ WQ_NITRATE_MG_L
- GW Layer 1 MZ WQ_POC_MG_L
- GW Layer 1 MZ WQ_PON_MG_L
- GW Layer 1 MZ WQ_POP_MG_L
- GW Layer 1 MZI SED_FINES
- GW Layer 1 MZI WQ_AMMONIUM_MG_L
- GW Layer 1 MZI WQ_DOC_MG_L
- GW Layer 1 MZI WQ_DON_MG_L
- GW Layer 1 MZI WQ_DOP_MG_L
- GW Layer 1 MZI WQ_FRP_MG_L
- GW Layer 1 MZI WQ_NITRATE_MG_L
- GW Layer 1 MZI WQ_POC_MG_L
- GW Layer 1 MZI WQ_PON_MG_L
- GW Layer 1 MZI WQ_POP_MG_L
- Depth
- Vector Velocity
- Velocity
- Water Level
- Time of Peak h
- GW QZ Layer 1
- GW QZI Layer 1
- Bed Elevation
- Model_001_catchment_hydrology.xmdf
- TUFLOW FV
- Model_001_receiving_HD.nc
- Bed Elevation
- salinity
- sediment fraction 1 concentration
- temperature
- velocity
- vector Velocity
- water depth
- water surface elevation
- Model_001_receiving_WQ.nc
- Bed Elevation
- WQ_AMMONIUM_MG_L
- WQ_DISS_OXYGEN_MG_L
- WQ_DOC_MG_L
- WQ_DON_MG_L
- WQ_DOP_MG_L
- WQ_FRP_ADS_MG_L
- WQ_FRP_MG_L
- WQ_NITRATE_MG_L
- WQ_PHYTO_FDIAT_CONC_MICG_L
- WQ_POC_MG_L
- WQ_PON_MG_L
- WQ_POP_MG_L
- WQ_SILICATE_MG_L
- Bed Elevation
- Model_001_receiving_HD.nc
6.2.3.3 Interrogation
The above output files can be viewed either:
- Individually via the TUFLOW Viewer (File -> Load Results -> Map Outputs), and interrogated using usual TUFLOW Viewer techniques, or
- Simultaneously via use of the Create TUFLOW Catch JSON function demonstrated in the eLearning material described in Section 4.3