MétaCan
Menu
Back to cohort

Clutch size relative to tree cavity size in Northern Flickers

2001· article· en· W1972085194 on OpenAlex
Karen L. Wiebe, Trisha L. Swift

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

VenueJournal of Avian Biology · 2001
Typearticle
Languageen
FieldEnvironmental Science
TopicAvian ecology and behavior
Canadian institutionsUniversity of Saskatchewan
FundersNatural Sciences and Engineering Research Council of Canada
KeywordsAvian clutch sizeBiologyNest (protein structural motif)PredationClutchEcologyHatchingZoologyAnimal scienceReproductionPhysics

Abstract

fetched live from OpenAlex

We analysed clutch size versus nest size in 153 broods of the Northern Flicker Colaptes auratus , a woodpecker using natural cavities in British Columbia, Canada. Larger volume cavities were less susceptible to predation and cavity size was positively associated with the age and body size of males and with the body condition of female parents. Although clutches varied between 4 and 11 eggs, and the floor area of cavities varied about 5‐fold, we found no relationship between clutch size and floor area or cavity volume. To see if there were fitness consequences to clutch size relative to nest size, we examined hatching success and nestling mortality in flicker broods. Hatching success was not related to cavity size, but crowding slightly reduced nestling survival even when clutch size was controlled statistically. However, there was no effect of cavity size on the total number of nestlings fledged. Newly excavated flicker cavities were smaller than reused cavities suggesting a cost to excavation. This cost, coupled with the minimal fitness consequences of overcrowding, may explain why flickers do not adjust clutch size to cavity size.

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 categoriesInsufficient 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 score0.999

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.0000.000
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0020.001

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.012
GPT teacher head0.260
Teacher spread0.248 · 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