MétaCan
Menu
Back to cohort
Record W2314233999 · doi:10.2478/v10025-012-0038-4

Comparison of machine learning methods for runoff forecasting in mountainous watersheds with limited data / Porównanie metod uczenia maszynowego do prognozowania spływu w zlewniach górskich na podstawie ograniczonych danych

2012· article· en· W2314233999 on OpenAlex

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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueJournal of Water and Land Development · 2012
Typearticle
Languageen
FieldEnvironmental Science
TopicHydrological Forecasting Using AI
Canadian institutionsMcGill University
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsSurface runoffWatershedSupport vector machineHydrology (agriculture)PrecipitationAntecedent moistureEnvironmental scienceRunoff curve numberMachine learningMeteorologyComputer scienceGeographyEngineeringEcology

Abstract

fetched live from OpenAlex

Abstract Runoff forecasting in mountainous regions with processed based models is often difficult and inaccurate due to the complexity of the rainfall-runoff relationships and difficulties involved in obtaining the required data. Machine learning models offer an alternative for runoff forecasting in these regions. This paper explores and compares two machine learning methods, support vector regression (SVR) and wavelet networks (WN) for daily runoff forecasting in the mountainous Sianji watershed located in the Himalayan region of India. The models were based on runoff, antecedent precipitation index, rainfall, and day of the year data collected over the three year period from July 1, 2001 and June 30, 2004. It was found that both the methods provided accurate results, with the best WN model slightly outperforming the best SVR model in accuracy. Both the WN and SVR methods should be tested in other mountainous watershed with limited data to further assess their suitability in forecasting.

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.004
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: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.410
Threshold uncertainty score0.614

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0040.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
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.078
GPT teacher head0.335
Teacher spread0.257 · 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