MétaCan
Menu
Back to cohort
Record W1982220374 · doi:10.1080/02626667.2012.727212

Modelling streamflow trends for a watershed with limited data: case of the Litani basin, Lebanon

2012· article· en· W1982220374 on OpenAlex
Hamzeh Hussein Ramadan, R. Edward Beighley, Amruthur S. Ramamurthy

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueHydrological Sciences Journal · 2012
Typearticle
Languageen
FieldEnvironmental Science
TopicHydrology and Watershed Management Studies
Canadian institutionsConcordia University
FundersMinistry of Environment
KeywordsStreamflowEnvironmental scienceStructural basinSurface runoffWatershedDrainage basinHydrology (agriculture)ClimatologyPrecipitationMeteorologyGeologyGeography

Abstract

fetched live from OpenAlex

Streamflow variability in the Upper and Lower Litani basin, Lebanon was modelled as there is a lack of long-term measured runoff data.To simulate runoff and streamflow, daily rainfall was derived using a stochastic rainfall generation model and monthly rainfall data.Two distinct synthetic rainfall models were developed based on a two-part probabilistic distribution approach.The rainfall occurrence was described by a Markov chain process, while the rainfall distribution on wet days was represented by two different distributions (i.e.gamma and mixed exponential distributions).Both distributions yielded similar results.The rainfall data were then processed using water balance and routing models to generate daily and monthly streamflow.Compared with measured data, the model results were generally reasonable (mean errors ranging from 0.1 to 0.8 m 3 /s at select locations).Finally, the simulated monthly streamflow data were used to investigate discharge trends in the Litani basin during the 20th century using the Mann-Kendall and Sen slope nonparametric trend detection methods.A significant drying trend of the basin was detected, reaching a streamflow reduction of 0.8 and 0.7 m 3 /s per decade in January for the Upper and Lower basin, respectively.

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.

Full frame distilled prediction

Teacher imitation

Not 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.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.342
Threshold uncertainty score0.786

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0010.001
Scholarly communication0.0000.001
Open science0.0010.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.

Opus teacher head0.068
GPT teacher head0.274
Teacher spread0.206 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it