MétaCan
Menu
Back to cohort
Record W3164791059 · doi:10.1109/mim.2021.9436102

Machine Learning in Measurement Part 2: Uncertainty Quantification

2021· article· en· W3164791059 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

VenueIEEE Instrumentation & Measurement Magazine · 2021
Typearticle
Languageen
FieldComputer Science
TopicAdversarial Robustness in Machine Learning
Canadian institutionsUniversity of Ottawa
Fundersnot available
KeywordsUsabilityComputer scienceMeasurement uncertaintyUncertainty quantificationSoftware deploymentArtificial intelligenceRisk analysis (engineering)Machine learningHuman–computer interactionSoftware engineeringMathematicsStatistics

Abstract

fetched live from OpenAlex

In spite of the advent of Machine Learning (ML) and its successful deployment in measurement systems, little information can be found in the literature about uncertainty quantification in these systems [1]. Uncertainty is crucial for the adoption of ML in commercial products and services. Designers are now being encouraged to be upfront about the uncertainty in their ML systems, because products that specify their uncertainty can have a significant competitive advantage and can unlock new value, reduce risk, and improve usability [2]. In this article, we will describe uncertainty quantification in ML. Because there isn't enough room in one article to explain all ML methods, we concentrate on Deep Learning (DL), which is one of the most popular and effective ML methods in I&M [3]. Please note that this article follows and uses concepts from Part 1 [4], so readers are highly encouraged to first read that part. In addition, we assume the reader has a basic understanding of both DL and uncertainty. Readers for whom this assumption is false are encouraged to first read the brief introduction to DL and its applications in I&M presented in [3] as well as the uncertainty tutorial in [5].

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.003
metaresearch head score (Gemma)0.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.957
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.001
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0010.000
Research integrity0.0000.001
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.063
GPT teacher head0.277
Teacher spread0.214 · 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