MétaCan
Menu
Back to cohort
Record W2983504627 · doi:10.1515/revce-2018-0067

Uncertainty in chemical process systems engineering: a critical review

2019· review· en· W2983504627 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

VenueReviews in Chemical Engineering · 2019
Typereview
Languageen
FieldEngineering
TopicProcess Optimization and Integration
Canadian institutionsPolytechnique Montréal
Fundersnot available
KeywordsComputer scienceUncertainty analysisMerge (version control)Process (computing)Propagation of uncertaintyMultidisciplinary approachIndustrial engineeringData miningUncertainty quantificationRisk analysis (engineering)Management scienceMachine learningAlgorithmEngineeringSimulationInformation retrieval

Abstract

fetched live from OpenAlex

Abstract Uncertainty or error occurs as a result of a lack or misuse of knowledge about specific topics or situations. In this review, we recall the differences between error and uncertainty briefly, first, and then their probable sources. Then, their identifications and management in chemical process design, optimization, control, and fault detection and diagnosis are illustrated. Furthermore, because of the large amount of information that can be obtained in modern plants, accurate analysis and evaluation of those pieces of information have undeniable effects on the uncertainty in the system. Moreover, the origins of uncertainty and error in simulation and modeling are also presented. We show that in a multidisciplinary modeling approach, every single step can be a potential source of uncertainty, which can merge into each other and generate unreliable results. In addition, some uncertainty analysis and evaluation methods are briefly presented. Finally, guidelines for future research are proposed based on existing research gaps, which we believe will pave the way to innovative process designs based on more reliable, efficient, and feasible optimum planning.

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.001
metaresearch head score (Gemma)0.002
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Systematic review · Consensus signal: none
GenreCandidate signal: Review · Consensus signal: Review
Teacher disagreement score0.574
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.002
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0040.001
Bibliometrics0.0000.002
Science and technology studies0.0000.000
Scholarly communication0.0000.000
Open science0.0010.000
Research integrity0.0010.002
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.049
GPT teacher head0.327
Teacher spread0.278 · 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