MétaCan
Menu
Back to cohort
Record W2945648301 · doi:10.1002/aic.16672

A consolidated flow regime map of upward gas fluidization

2019· article· en· W2945648301 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

VenueAIChE Journal · 2019
Typearticle
Languageen
FieldEngineering
TopicGranular flow and fluidized beds
Canadian institutionsWestern University
Fundersnot available
KeywordsFluidizationTurbulenceFlow (mathematics)Fluidized bedMechanicsMaterials scienceThermodynamicsPhysics

Abstract

fetched live from OpenAlex

Abstract A new flow regime map, resulting from more fundamental studies on the hydrodynamics and new flow regimes, is proposed in response to more practical reclassifications of the existing regimes with the development of upward gas‐solids fluidization systems. The previously reported flow regime maps and flow structures of some widely used fluidized beds are carefully examined. To better reflect the industrial applications, the fast fluidization regime is reclassified as high‐density and low‐density circulating fluidization regimes. A consolidated flow regime map is then proposed where the flow regimes of upward fluidization expand to include new types of fluidized beds such as circulating turbulent fluidized bed and high‐density circulating fluidized bed. The proposed flow regime map consists of six flow regimes: bubbling, turbulent, circulating turbulent, high‐density circulating and low‐density circulating fluidization, and pneumatic transport. The transitions between the regimes are discussed with new correlations proposed for fluid catalytic cracking type particles. Analysis on the dominating phase in the different types of fluidized beds reveals the dynamic changeover from solids phase continuous in conventional low‐velocity batch/“fixed” fluidization operations to gas phase continuous in high‐velocity continuous/“moving” fluidization operations and provides more insights to the transitions between the flow regimes for industrial design and practice.

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 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.248
Threshold uncertainty score0.697

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
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.0010.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.005
GPT teacher head0.184
Teacher spread0.179 · 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