MétaCan
Menu
Back to cohort
Record W4221144283 · doi:10.1007/s41781-022-00086-2

Constraints on Future Analysis Metadata Systems in High Energy Physics

2022· article· en· W4221144283 on OpenAlexaff
T. J. Khoo, A. Reinsvold Hall, N. Skidmore, S. Alderweireldt, J. K. Anders, C. Burr, W. Buttinger, P. David, L. Gouskos, L. Gray, S. Hageböck, A. Krasznahorkay, P. Laycock, A. Lister, З. Маршалл, A. B. Meyer, T. Novák, S. Rappoccio, M. Ritter, E. Rodrigues, J. Rumsevicius, L. Sexton-Kennedy, Neale R. Smith, G. A. Stewart, S. Wertz

Bibliographic record

VenueComputing and Software for Big Science · 2022
Typearticle
Languageen
FieldComputer Science
TopicAdvanced Data Storage Technologies
Canadian institutionsUniversity of British Columbia
FundersDivision of PhysicsScience and Technology Facilities CouncilEuropean CommissionCERNHigh Energy PhysicsU.S. Department of EnergyH2020 European Research CouncilOffice of ScienceNational Science Foundation
KeywordsMetadataComputer scienceScope (computer science)ReinterpretationMeta Data ServicesData elementData scienceWorld Wide WebMetadata modelingInformation retrieval

Abstract

fetched live from OpenAlex

Abstract In high energy physics (HEP), analysis metadata comes in many forms—from theoretical cross-sections, to calibration corrections, to details about file processing. Correctly applying metadata is a crucial and often time-consuming step in an analysis, but designing analysis metadata systems has historically received little direct attention. Among other considerations, an ideal metadata tool should be easy to use by new analysers, should scale to large data volumes and diverse processing paradigms, and should enable future analysis reinterpretation. This document, which is the product of community discussions organised by the HEP Software Foundation, categorises types of metadata by scope and format and gives examples of current metadata solutions. Important design considerations for metadata systems, including sociological factors, analysis preservation efforts, and technical factors, are discussed. A list of best practices and technical requirements for future analysis metadata systems is presented. These best practices could guide the development of a future cross-experimental effort for analysis metadata tools.

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.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.176
metaresearch head score (Gemma)0.218
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch
Consensus categoriesnone
DomainCandidate signal: Methods · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.824
Threshold uncertainty score0.929

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.1760.218
Meta-epidemiology (narrow)0.0010.003
Meta-epidemiology (broad)0.0010.002
Bibliometrics0.0070.009
Science and technology studies0.0090.012
Scholarly communication0.0410.073
Open science0.0090.016
Research integrity0.0070.008
Insufficient payload (model declined to judge)0.0120.006

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.023
GPT teacher head0.261
Teacher spread0.238 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

Study designTheoretical or conceptual
DomainMethods
GenreMethods

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations1
Published2022
Admission routes1
Has abstractyes

Explore more

Same venueComputing and Software for Big ScienceSame topicAdvanced Data Storage TechnologiesFrench-language works237,207