MétaCan
Menu
Back to cohort
Record W2152316836 · doi:10.2172/781830

ENDF-102 DATA FORMATS AND PROCEDURES FOR THE EVALUATION NUCLEAR DATA FILE ENDF-6.

2001· report· en· W2152316836 on OpenAlexaboutno aff
V. McLane

Bibliographic record

Venuenot available
Typereport
Languageen
FieldEngineering
TopicNuclear reactor physics and engineering
Canadian institutionsnot available
Fundersnot available
KeywordsNuclear dataNuclear physicsNeutronData fileFissionNuclear fission productNuclear engineeringPhysicsNuclear reactionFission productsComputer scienceDatabaseEngineering

Abstract

fetched live from OpenAlex

The Evaluated Nuclear Data File (ENDF) formats and libraries are decided by the Cross Section Evaluation Working Group (CSEWG), a cooperative effort of national laboratories, industry, and universities in the U.S. and Canada, and are maintained by the National Nuclear Data Center (NNDC). Earlier versions of the ENDF format provided representations for neutron cross sections and distributions, photon production from neutron reactions, a limited amount of charged-particle production from neutron reactions, photo-atomic interaction data, thermal neutron scattering data, and radionuclide production and decay data (including fission products). Version 6 (ENDF-6) allows higher incident energies, adds more complete descriptions of the distributions of emitted particles, and provides for incident charged particles and photonuclear data by partitioning the ENDF library into sub-libraries. Decay data, fission product yield data, thermal scattering data, and photo-atomic data have also been formally placed in sub-libraries. In addition, this rewrite represents an extensive update to the Version V manual.

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.007
metaresearch head score (Gemma)0.027
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: Not applicable
GenreCandidate signal: Dataset · Consensus signal: Dataset
Teacher disagreement score0.236
Threshold uncertainty score0.790

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0070.027
Meta-epidemiology (narrow)0.0020.002
Meta-epidemiology (broad)0.0010.001
Bibliometrics0.0070.005
Science and technology studies0.0020.001
Scholarly communication0.0050.005
Open science0.0050.003
Research integrity0.0020.002
Insufficient payload (model declined to judge)0.2360.236

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.140
GPT teacher head0.321
Teacher spread0.181 · 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.

The models applied no category: nothing in the taxonomy fit this work.
Study designNot applicable
Domainnot available
GenreDataset

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

Citations43
Published2001
Admission routes1
Has abstractyes

Explore more

Same topicNuclear reactor physics and engineeringFrench-language works237,207