MétaCan
Menu
Back to cohort
Record W2773889255 · doi:10.1080/10871209.2017.1402223

Mitigating infrastructure loss from beaver flooding: A cost–benefit analysis

2017· article· en· W2773889255 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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueHuman Dimensions of Wildlife · 2017
Typearticle
Languageen
FieldEnvironmental Science
TopicEcology and biodiversity studies
Canadian institutionsUniversity of Alberta
FundersAlberta Conservation Association
KeywordsBeaverCost–benefit analysisNet present valueWillingness to payFlooding (psychology)DiscountingEnvironmental scienceGeographyEnvironmental resource managementBusinessEconomicsEcologyFinanceProduction (economics)

Abstract

fetched live from OpenAlex

We installed 12 pond levelers to counter flooding by beavers and developed a cost–benefit analysis for these sites in Alberta, Canada. We also documented beaver management approaches throughout Alberta. Over 3 years, one site required regular maintenance until we designed a modified pond leveler; another required minor modifications. Others required almost no maintenance. Based on a “willingness-to-pay” (WTP) of $0 and discount rate of 3%, installing pond levelers resulted in a present value net benefit of $81,519 over 3 years and $179,440 over 7 years. Scenarios incorporating discount rates of 3% and 7%, horizons of either 3 or 7 years, and varying WTPs resulted in significant net benefits. Provincially, municipalities employed up to seven methods to control beavers: most commonly lethal control and dam removal. Total annual costs provided by 48 municipalities and 4 provincial parks districts were $3,139,223; however, cost-accounting was sometimes incomplete, which makes this a conservative estimate.

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.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesScience and technology studies, Insufficient payload (model declined to judge)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.010
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0020.001
Scholarly communication0.0000.000
Open science0.0000.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0010.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.018
GPT teacher head0.252
Teacher spread0.234 · 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