MétaCan
Menu
Back to cohort
Record W3132249344 · doi:10.1515/pac-2020-0403

Good reporting practice for thermophysical and thermochemical property measurements (IUPAC Technical Report)

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

VenuePure and Applied Chemistry · 2021
Typearticle
Languageen
FieldChemistry
TopicChemical Thermodynamics and Molecular Structure
Canadian institutionsRoyal Military College of CanadaSchlumberger (Canada)Virtual Materials Group (Canada)
FundersInternational Union of Pure and Applied Chemistry
KeywordsChemical nomenclatureProperty (philosophy)Consistency (knowledge bases)ChemistryQuality (philosophy)Property valueValue (mathematics)Management scienceComputer scienceOrganic chemistryEpistemologyEngineeringBusiness

Abstract

fetched live from OpenAlex

Abstract Scientific projects frequently involve measurements of thermophysical, thermochemical, and other related properties of chemical compounds and materials. These measured property data have significant potential value for the scientific community, but incomplete and inaccurate reporting often hampers their utilization. The present IUPAC Technical Report summarizes the needs of chemical engineers and researchers as consumers of these data and shows how publishing practices can improve information transfer. In the Report, general principles of Good Reporting Practice are developed together with examples illustrating typical cases of reporting issues. Adoption of these principles will improve the quality, reproducibility, and usefulness of experimental data, bring a better level of consistency to results, and increase the efficiency and impact of research. Closely related to Good Reporting Practice , basic elements of Good Research Practice are also introduced with a goal to reduce the number of ambiguities and unresolved problems within the thermophysical property data domain.

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.001
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Bench or experimental · Consensus signal: Bench or experimental
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.148
Threshold uncertainty score0.929

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.001
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.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.017
GPT teacher head0.274
Teacher spread0.256 · 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