MétaCan
Menu
Back to cohort

Vision 2050: Reaction Engineering Roadmap

2023· article· en· W4387859577 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

VenueACS Engineering Au · 2023
Typearticle
Languageen
FieldEngineering
TopicInnovative Microfluidic and Catalytic Techniques Innovation
Canadian institutionsPolytechnique Montréal
Fundersnot available
KeywordsContext (archaeology)Chemical reaction engineeringSpeciality chemicalsScale (ratio)Field (mathematics)Engineering managementManagement scienceComputer scienceBiochemical engineeringSystems engineeringRisk analysis (engineering)EngineeringChemistryBusinessCatalysis

Abstract

fetched live from OpenAlex

ABSTRACT: This perspective provides the collective opinions of a dozen chemical reaction engineers from academia and industry. In this sequel to the “Vision 2020: Reaction Engineering Roadmap,” published in 2001, we provide our opinions about the field of reaction engineering by addressing the current situation, identifying barriers to progress, and recommending research directions in the context of four industry sectors (basic chemicals, specialty chemicals, pharmaceuticals, and polymers) and five technology areas (reactor system selection, design and scale-up, chemical mechanism development and property estimation, catalysis, nonstandard reactor types, and electrochemical systems). Our collective input in this report includes numerous recommendations regarding research needs in the field of reaction engineering in the coming decades, including guidance for prioritizing efforts in workforce development, measurement science, and computational methods. We see important roles for reaction engineers in the plastics circularity challenge, decarbonization of processes, electrification of chemical reactors, conversion of batch processes to continuous processes, and development of intensified, dynamic reaction processes.

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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
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.402
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.002
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.009
GPT teacher head0.225
Teacher spread0.216 · 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