MétaCan
Menu
Back to cohort
Record W2743712474 · doi:10.5170/cern-2011-006.148

Setting Limits, Computing Intervals, and Detection

2011· article· en· W2743712474 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.

fundA Canadian funder is recorded on the work.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueCERN Document Server (European Organization for Nuclear Research) · 2011
Typearticle
Languageen
FieldDecision Sciences
TopicProbabilistic and Robust Engineering Design
Canadian institutionsnot available
FundersBanff International Research Station for Mathematical Innovation and DiscoveryCERNHigh Energy PhysicsNational Science Foundation
KeywordsSensitivity (control systems)Limit (mathematics)Computer scienceComputationFocus (optics)Detection theoryData miningStatisticsAlgorithmMathematicsDetectorEngineering

Abstract

fetched live from OpenAlex

This article discusses a number of statistical aspects of source detection, thecomputation of intervals and upper limits for a source intensity, and accessingthe sensitivity of a detection procedure. Emphasis is placed on model diag-nostics, validation, and improvement as means of avoiding odd behaviors in theseprocedures such as over abundant short or empty intervals. Improved modelspecification is viewed as a better response to systematic uncertainties, thelook elsewhere effect, and general model inadequacy than simply insisting on asignificance level of 5σ for source detection. We advocate reporting both theupper limit and the sensitivity to better represent the strength of evidence fordetection and the reported source intensity. Finally, we explore the use ofdecision theoretic analysis to derive detection procedures, intervals, andlimits in order to focus attention on the statistical properties of primaryinterest.

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.003
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesInsufficient payload (model declined to judge)
Consensus categoriesInsufficient payload (model declined to judge)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.311
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

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