MétaCan
Menu
Back to cohort
Record W2030467114 · doi:10.1115/icone16-48128

Validation of FLUENT for Prediction of Flow Distribution and Pressure Gradients in a Multi-Branch Header Under Low Flow Conditions

2008· article· en· W2030467114 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

VenueVolume 2: Fuel Cycle and High Level Waste Management; Computational Fluid Dynamics, Neutronics Methods and Coupled Codes; Student Paper Competition · 2008
Typearticle
Languageen
FieldEngineering
TopicNuclear Engineering Thermal-Hydraulics
Canadian institutionsMcMaster University
Fundersnot available
KeywordsHeaderMechanicsFluentComputational fluid dynamicsFlow (mathematics)Flow coefficientVolumetric flow rateSimulationInletTwo-phase flowFluid dynamicsComputer scienceMechanical engineeringEngineeringPhysics

Abstract

fetched live from OpenAlex

Flow headers are commonly used in nuclear reactors, boilers and heat exchangers to distribute fluid to branches or to combine flow from the branches along the header. In CANDU reactors the main heat transport system divides the flow from the pumps into approximately 120 individual feeder pipes which then direct the flow into separate fuel channels. Historically, nuclear safety analysis has been performed using one-dimensional averaged system codes, and as such the headers are cross-sectionally averaged. In this paper, flow distribution and pressure gradients along a multi-branch header have been predicted using the three dimensional computational fluid dynamics software FLUENT and were compared to results obtained from experimental data obtained from literature for single phase conditions. In order to assess FLUENTs capabilities this study was performed by comparing the predictions against separate effects experiments conducted on a smaller sized header available in literature. For these experiments, water inlet flow rate was varied and flow rates in the header branches were measured. The aim of this work is to validate FLUENT software for predicting flow distribution and pressure gradients in single phase flow in such a multi-branch geometry. The effects of flow model, grid density, convergence criteria, flow inlet velocity and header size on the computational results were studied. Vortex formation and flow separation were also studied and compared to the experimentally observed flow behaviour.

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 categoriesMeta-epidemiology (narrow)
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.502
Threshold uncertainty score1.000

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.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.014
GPT teacher head0.257
Teacher spread0.242 · 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