MétaCan
Menu
Back to cohort
Record W2027834210 · doi:10.2495/mpf070341

The transition of an in-line vortex to slug flow: correlating pressure and reaction force measurements with high-speed video

2007· article· en· W2027834210 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

VenueWIT transactions on engineering sciences · 2007
Typearticle
Languageen
FieldEngineering
TopicFluid Dynamics and Mixing
Canadian institutionsUniversity of Calgary
Fundersnot available
KeywordsMechanicsSlug flowVortexMaterials scienceFlow (mathematics)Volumetric flow rateMass flow meterSpectral densityFlow mapThermodynamicsTwo-phase flowPhysics

Abstract

fetched live from OpenAlex

In this work, the performance of a Slug Flow Expander (SFE) was investigated. Multiphase flow consisting of air and water was injected into the SFE. Critical flow rates of air and water were identified that caused transition to the slug flow regime. It was observed that at water flow rates of 1.00 L/s and air flow rates above 3.00 L/s, the flow regime in the SFE transitioned to slug flow. A high-speed digital camera was used to visualize the flow inside the SFE. Wall pressure and reaction force measurements were synchronized with the high-speed camera. Autocorrelation, cross-correlation, and power spectral density functions were performed on reaction force, wall pressure, and air-core diameter. Power spectra of reaction force and wall pressure revealed strong energy peaks at low, middle, and high frequencies. Dominant low frequency energy (2.9 Hz and 4.4 Hz) was found to be attributed to the rotation rate of the liquid component in the SFE. The dominant middle frequency spikes (39.5 Hz, 31.3 Hz, 24.4 Hz for reaction force; 20 Hz, 15.6 Hz for wall pressure) are believed to be attributed to the formation, convection, and exiting of the liquid slugs from the SFE. It is speculated that the dominant high-frequency spikes are attributed to both mechanical vibrations and pressure fluctuations caused by the flow facility pump.

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.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.468
Threshold uncertainty score0.385

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.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.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.205
Teacher spread0.196 · 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