MétaCan
Menu
Back to cohort
Record W2094588121 · doi:10.1139/l00-049

A direct integration method for computation of gradually varied flow profiles

2000· article· en· W2094588121 on OpenAlex
A. S. Ramamurthy, Seyed Fazlolah Saghravani, Ram Balachandar

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.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueCanadian Journal of Civil Engineering · 2000
Typearticle
Languageen
FieldEngineering
TopicHydraulic flow and structures
Canadian institutionsnot available
Fundersnot available
KeywordsComputationFlow (mathematics)Open-channel flowExponentComputer scienceChannel (broadcasting)Drawdown (hydrology)MechanicsApplied mathematicsAlgorithmMathematical optimizationMathematicsGeologyGeotechnical engineeringGeometryGroundwaterPhysics

Abstract

fetched live from OpenAlex

A simple procedure to compute the length of gradually varied flow profiles is presented. It is based on the direct integration of the dynamic equation for gradually varied flow, which forms the bases for existing methods of computing flow profiles. In these methods, a long reach for which the profile length is needed gets divided into several subsections, to ensure that the hydraulic exponents do not vary very much in the subsections. Since the proposed analytical method does not use the hydraulic exponent in its development, the flow profiles can be computed in one step and one can still get accurate results. The results of the profile computations based on existing methods are compared with the corresponding results of the present method. The results find direct application in hydraulic engineering practice, where flow profile lengths are needed for design purposes. Key words: gradually varied flow, flow profile computation, open channel flow, backwater curve, drawdown curve.

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: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.932
Threshold uncertainty score0.564

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.007
GPT teacher head0.209
Teacher spread0.202 · 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