Comparison of event‐specific rainfall–runoff responses and their controls in contrasting geographic areas
Bibliographic record
Abstract
Abstract Numerous studies have examined the event‐specific hydrologic response of hillslopes and catchments to rainfall. Knowledge gaps, however, remain regarding the relative influence of different meteorological factors on hydrologic response, the predictability of hydrologic response from site characteristics, or even the best metrics to use to effectively capture the temporal variability of hydrologic response. This study aimed to address those knowledge gaps by focusing on 21 sites with contrasting climate, topography, geology, soil properties, and land cover. High‐frequency rainfall and discharge records were analysed, resulting in the delineation of over 1,600 rainfall–runoff events, which were described using a suite of hydrologic response metrics and meteorological factors. Univariate and multivariate statistical techniques were then applied to synthesize the information conveyed by the computed metrics and factors, notably measures of central tendency and variability, variation partitioning, partial correlations, and principal component analysis. Results showed that some response magnitude metrics generally reported in the literature (e.g., runoff ratio and area‐normalized peak discharge) did not vary significantly among sites. The temporal variability in site‐specific hydrologic response was often attributable to the joint influence of storage‐driven (e.g., total event rainfall and antecedent precipitation) and intensity‐driven (e.g., rainfall intensity and antecedent potential evapotranspiration) meteorological factors. Mean annual temperature and potential evapotranspiration at a given site appeared to be good predictors of hydrologic response timing (e.g., response lag and lag to peak). Response timing metrics, particularly those associated with response initiation, were also identified as the metrics most critical for capturing intrasite response variability. This study therefore contributes to the growing knowledge on event‐specific hydrologic response by highlighting the importance of response timing metrics and intensity‐driven meteorological factors, which are infrequently discussed in the literature. As few correlations were found between physiographic variables and response metrics, more data‐driven studies are recommended to further our understanding of landscape–hydrology interactions.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame distilled prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.
Codex and Gemma teacher scores by category
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.000 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.000 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one teacher head, not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".