Terminology - Revision history

Julia Glenday: /* Aquifers & groundwater flows */

2023-11-27T12:39:19Z

Aquifers & groundwater flows

Julia Glenday: /* Soil & unsaturated zone terms across tools */

2023-11-27T12:39:08Z

Soil & unsaturated zone terms across tools

Julia Glenday: /* Evapotranspiration terms across tools */

2023-11-27T12:38:55Z

Evapotranspiration terms across tools

Julia Glenday: /* Runoff & streamflow terms across tools */

2023-11-27T12:38:44Z

Runoff & streamflow terms across tools

Julia Glenday: /* Spatial unit terms across tools */

2023-11-27T12:38:28Z

Spatial unit terms across tools

Julia Glenday: /* Hydrological process and parameter terms across tools */

2023-11-27T12:37:31Z

Hydrological process and parameter terms across tools

Julia Glenday: /* Models vs Modelling software tools */

2023-11-26T12:50:14Z

Models vs Modelling software tools

Julia Glenday: /* Aquifers & groundwater flows */

2023-11-24T16:21:22Z

Aquifers & groundwater flows

Julia Glenday: /* Soils & unsaturated zones */

2023-11-24T16:20:47Z

Soils & unsaturated zones

Julia Glenday: /* Evapotranspiration */

2023-11-24T16:16:18Z

Evapotranspiration

@@ Line 694: / Line 694: @@
 === Aquifers & groundwater flows ===
-Formatting notes:
+<small> Formatting notes:
 *'''equivalent terms are bold''';
 *similar / related terms are not bold & are starred*;
-*''notes on term usage in tool texts & interface are given in italics''
+*''notes on term usage in tool texts & interface are given in italics'' </small>
 {| class="wikitable"
 ! scope="col" | General term

@@ Line 487: / Line 487: @@
 ===Soil & unsaturated zone terms across tools===
-Formatting notes:
+<small> Formatting notes:
 *'''equivalent terms are bold''';
 *similar / related terms are not bold & are starred*;
-*''notes on term usage in tool texts & interface are given in italics''
+*''notes on term usage in tool texts & interface are given in italics'' </small>
 {| class="wikitable"
 ! scope="col" | General term

@@ Line 337: / Line 337: @@
 ===Evapotranspiration terms across tools ===
-Formatting notes:
+<small> Formatting notes:
 *'''equivalent terms are bold''';
 *similar / related terms are not bold & are starred*;
-*''notes on term usage in tool texts & interface are given in italics''
+*''notes on term usage in tool texts & interface are given in italics'' </small>
 {| class="wikitable"
 ! scope="col" | General term

@@ Line 223: / Line 223: @@
 ===Runoff & streamflow terms across tools===
-Formatting notes:
+<small> Formatting notes:
 *'''equivalent terms are bold''';
 *similar / related terms are not bold & are starred*;
-*''notes on term usage in tool texts & interface are given in italics''
+*''notes on term usage in tool texts & interface are given in italics'' </small>
 {| class="wikitable"
 ! scope="col" | General term

@@ Line 123: / Line 123: @@
 === Spatial unit terms across tools ===
-Formatting notes:
+<small> Formatting notes:
 *'''equivalent terms are bold''';
 *similar / related terms are not bold & are starred*;
-*''notes on term usage in tool texts & interface are given in italics''
+*''notes on term usage in tool texts & interface are given in italics'' </small>
 {| class="wikitable"
 ! scope="col" | General term

@@ Line 119: / Line 119: @@
 * [[#Soils & unsaturated zones|Soils & unsaturated zones]]
 * [[#Aquifers & groundwater flows|Aquifers & groundwater flows]]
 <br />
 <br />
 === Spatial unit terms across tools ===
 Formatting notes:

@@ Line 10: / Line 10: @@
 * ''"Model"'' can also refer to a ''specific model set-up'' of a specific catchment area built in a software tool, e.g., it is also common to read something like “an ACRU model of the Umgeni catchment” referring to a model of a given catchment built using ACRU, including the specific structure of subcatchments, hydrological response units, connections, parameter values, etc. that a modeller has selected for this catchment.
-The difference between these two things (a modelling software tool and an individual 'model' of a catchment) is worth noting. ACRU modelling software, for example, does enforce certain ways of representing/calculating the hydrological processes in a catchment. In this way the ACRU modelling software does constitute a “model" of how catchments work in a general sense. However, there are various set-up options in the tool and there are many things that can vary across different individual "models" that have all been built using ACRU software, ''even those built to represent the same catchment area.'' Different "ACRU models" of ‘catchment A’ could have different numbers of subcatchments, river elements, and separately represented land cover types; different linkages between parts of the landscape; and different parameter values. The same can be said for most modelling tools.
+The difference between these two things (a modelling software tool and an individual model of a catchment) is worth noting. ACRU modelling software, for example, does enforce certain ways of representing/calculating the hydrological processes in a catchment. In this way the ACRU modelling software does constitute a “model" of how catchments work in a general sense. However, there are various set-up options in the tool and there are many things that can vary across different individual "models" that have all been built using ACRU software, ''even those built to represent the same catchment area.'' Different "ACRU models" of ‘catchment A’ could have different numbers of subcatchments, river elements, and separately represented land cover types; different linkages between parts of the landscape; and different parameter values. The same can be said for most modelling tools.
 Therefore, calling a particular model set-up for a catchment “an ACRU model" does say some things about the model structure, but it doesn't clarify many critical elements. A model built in SWAT and a model built in ACRU of the same catchment could actually have very similar structures to one another, or they could be vastly different. In some cases the differences between specific models built in different tools may be more due to the set-up choices of individual users than due to differences across the software tools! For these reasons it can help to differentiate between "a model" and "a modelling tool".
@@ Line 18: / Line 18: @@
 * ''"modelling software tool"'' ("modelling software", "modelling tool", or "tool" for short) for software programmes that can be used to design and run catchment models. Each software tool comes with its own set of structural and algorithm options and choices within this set would have to be made to build a “model" using that tool.
 <br />
 === Basic terminology table ===
 {| class="wikitable"