Bibliographic record
Abstract
Offspring of the nuclear reactor industry and gas-oil production, multiphase fluids handling technology appears to have matured into an entirely new field of inquiry, most notably following broad acceptance of the drift flux and flow pattern concepts and their widespread integration into engineering calculations. The drift flux model (DFM), first suggested by Nicklin in 1962 and, soon after, adapted and developed by Professor Zuber’s research group at General Electric, enables calculation of “locally averaged” phase velocity. Further progress made in selection of the flow patterns, calculated for each section of the pipe, provided the key to properly assessing the terminal velocity of the discrete phase and the local phase distributions. The flow pattern concept was first introduced by Canadian Charles Govier to describe oil-water laboratory experiments, then by Hewitt-Roberts and Baker in 1954. A decade later, the team of Dukler-Taitel-Barnea developed the qualitative flow pattern concept into a quantitative roadmap procedure leading to rational calculations of the local (cross-section averaged) gas-liquid flow geometry, or flow pattern. The homogeneous gas-liquid flow, presuming the equality of gas and liquid velocities, a simplification broadly accepted during the early days of two-phase flow engineering, came to be regarded, due to Hinze’s work (Shell, 1955), as an identifiable region in the local flow map, reflecting turbulent and high-shear breakup of the discrete phase. To illustrate the usefulness, validity, and importance of the DFM, and mechanistic modeling using the DFM, as well as the salient work of Prof. Zuber on boiling instability this paper discuses reduction of potential explosive droplet boiling risk during multiphase pumping of high–gas-oil ratio mixtures. To assess critical operating conditions of the multiphase pumps, the Ishi-Zuber criteria developed during 1970 for assessing potential boiling instabilities were adapted to multiphase pumping/compression equipment and the results compared to field instability data. The elucidation of this problem relies heavily on the DFM and on salient research performed during 70s by Prof. Zuber’s team.
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.004 | 0.010 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.002 | 0.003 |
| Science and technology studies | 0.001 | 0.003 |
| Scholarly communication | 0.004 | 0.008 |
| Open science | 0.002 | 0.002 |
| Research integrity | 0.003 | 0.003 |
| Insufficient payload (model declined to judge) | 0.004 | 0.002 |
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".