MétaCan
Menu
Back to cohort
Record W2086512405 · doi:10.1899/11-031.1

How did fixed-width buffers become standard practice for protecting freshwaters and their riparian areas from forest harvest practices?

2012· article· en· W2086512405 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.

Bibliographic record

VenueFreshwater Science · 2012
Typearticle
Languageen
FieldEnvironmental Science
TopicHydrology and Sediment Transport Processes
Canadian institutionsUniversity of British Columbia
Fundersnot available
KeywordsRiparian zoneEnvironmental scienceTemperate rainforestWatershedSTREAMSRiparian bufferVegetation (pathology)Water qualityBiotaRiparian forestHydrology (agriculture)GeographyEcologyHabitatAgroforestryEcosystemGeology

Abstract

fetched live from OpenAlex

Abstract. Riparian buffers provide improved protection for water quality and biota, and narrow, fixed-width buffers of native vegetation along streams have been used to mitigate the effects of forest harvest at least since the 1960s. The practice of leaving unmanaged strips of vegetation along water courses in agricultural lands had been used before the 1960s in southern Europe and in eastern North America, but the scientific basis for leaving riparian buffers on forested lands came from observations in the coastal temperate rainforests of western North America. Those observations often were applied to other forested landscapes without further considerations. Fixed-width buffers are administratively simple to implement and assess, and have come to be the norm for streamside protection from forestry. Most guidelines for streamside protection allow some local modification for site and watershed-scale considerations, but frequently, the option to deviate from fixed-width buffers is not exercised because of uncertainty about outcomes. Few experiments have been done to test the efficacy of buffers of a particular width or of site- or landscape-specific modifications.

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.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.847
Threshold uncertainty score0.916

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0010.001
Scholarly communication0.0000.007
Open science0.0010.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.019
GPT teacher head0.249
Teacher spread0.230 · 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