MétaCan
Menu
Back to cohort
Record W2134485987 · doi:10.1002/fld.2231

Velocity–pressure coupling in finite difference formulations for the Navier–Stokes equations

2010· article· en· W2134485987 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

VenueInternational Journal for Numerical Methods in Fluids · 2010
Typearticle
Languageen
FieldEngineering
TopicComputational Fluid Dynamics and Aerodynamics
Canadian institutionsUniversity of Windsor
Fundersnot available
KeywordsFinite volume methodFinite differenceLaminar flowPressure-correction methodMathematicsFinite element methodFinite difference methodRegular gridNavier–Stokes equationsFlow (mathematics)CompressibilityApplied mathematicsMechanicsMathematical analysisGridGeometryPhysics

Abstract

fetched live from OpenAlex

Abstract A new numerical procedure for solving the two‐dimensional, steady, incompressible, viscous flow equations on a staggered Cartesian grid is presented in this paper. The proposed methodology is finite difference based, but essentially takes advantage of the best features of two well‐established numerical formulations, the finite difference and finite volume methods. Some weaknesses of the finite difference approach are removed by exploiting the strengths of the finite volume method. In particular, the issue of velocity–pressure coupling is dealt with in the proposed finite difference formulation by developing a pressure correction equation using the SIMPLE approach commonly used in finite volume formulations. However, since this is purely a finite difference formulation, numerical approximation of fluxes is not required. Results presented in this paper are based on first‐ and second‐order upwind schemes for the convective terms. This new formulation is validated against experimental and other numerical data for well‐known benchmark problems, namely developing laminar flow in a straight duct, flow over a backward‐facing step, and lid‐driven cavity flow. Copyright © 2010 John Wiley & Sons, Ltd.

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.002
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: Methods · Consensus signal: none
Teacher disagreement score0.536
Threshold uncertainty score0.518

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.002
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.0010.000
Research integrity0.0000.001
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.031
GPT teacher head0.379
Teacher spread0.348 · 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