MétaCan
Menu
Back to cohort
Record W2968348525 · doi:10.22230/jwsm.2019v3n2a25

Key Planning Questions to Consider in Small Stream Hydrometric Monitoring

2019· article· en· W2968348525 on OpenAlexaffvenue
Robin Pike, Neil Goeller, Jonathan D. Goetz, Sarah Crookshanks

Bibliographic record

VenueConfluence Journal of Watershed Science and Management · 2019
Typearticle
Languageen
FieldEnvironmental Science
TopicHydrology and Sediment Transport Processes
Canadian institutionsSimon Fraser University
Fundersnot available
KeywordsKey (lock)StreamflowMetadataComputer scienceResource (disambiguation)Sampling (signal processing)Computer securityTelecommunicationsGeographyWorld Wide Web

Abstract

fetched live from OpenAlex

This article provides key questions to consider when planning and operating a small stream hydrometric station. Office planning components include defining hydrometric monitoring objectives; the availability of hydrometric expertise; resource availability; safety plans and standard operating procedures; equipment availability (hydrometric station installation and streamflow measurement); sampling frequency and data availability; permissions and permitting requirements; data processing, access, and archiving; and metadata requirements. Key parts of field-based hydrometric planning include site safety; site accessibility; flow variability; channel control features; flow containment, diversions and additions; low flow considerations; high flow considerations; flow measurement challenges in small streams; benchmarks and survey criteria; and public safety and vandalism. Theoverall goal of the article is to help non-professionals collect better hydrometric data and to highlight the varied planning aspects of typical hydrometric installations and operations.

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 machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.019
metaresearch head score (Gemma)0.043
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.019
Threshold uncertainty score0.100

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0190.043
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0020.003
Science and technology studies0.0060.004
Scholarly communication0.0080.011
Open science0.0030.005
Research integrity0.0040.004
Insufficient payload (model declined to judge)0.0110.002

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.020
GPT teacher head0.262
Teacher spread0.242 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreMethods

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

Quick stats

Citations3
Published2019
Admission routes2
Has abstractyes

Explore more

Same venueConfluence Journal of Watershed Science and ManagementSame topicHydrology and Sediment Transport ProcessesFrench-language works237,207