Experimental methods in chemical engineering: Data processing and data usage in decision‐making
Bibliographic record
Abstract
Abstract Industrial facilities collect large volumes of data, store them according to prescribed protocols, and then interpret them for process decision‐making. Several sources and types of error contaminate these data for various reasons, but especially because they come from unreliable or unpredictable instruments. Data (or signal) processing corrects measurement errors to improve fidelity. Here, we highlight decision‐making applications and signal processing methods. To fully appreciate the state‐of‐the‐art, we interviewed plant data experts and software developers in the pulp and paper industry to examine how they apply signal processing methods in the context of decision‐making, including the value of process data, how these data are used, and the major barriers that prevent plants from using data. Process experts clean data thoroughly with basic approaches compared to the advanced techniques available in the recent literature. The interviews demonstrate that decisions in industry are primarily based on steady‐state process operating data. Challenges and barriers that prevent the use of process data to their full potential relate to resource limitations (people, time, and money), an entrenched culture, and access to recent technology. In practice, experts consider, implicitly or explicitly, data that represent the process operating under steady‐state conditions. A plant model that represents steady‐state operations is easier to interpret, is presented in a form that is usable by plant operators, and in this way, better enables decision‐making.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.148 | 0.275 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.003 | 0.005 |
| Science and technology studies | 0.002 | 0.017 |
| Scholarly communication | 0.010 | 0.010 |
| Open science | 0.004 | 0.005 |
| Research integrity | 0.003 | 0.004 |
| Insufficient payload (model declined to judge) | 0.007 | 0.001 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".