MétaCan
Menu
Back to cohort
Record W194771532 · doi:10.14796/jwmm.r220-19

Water Resources Modeling Tools - Open Source Code versus Proprietary Software

2004· article· en· W194771532 on OpenAlexaffvenue
Edward Burgess, William James, Lewis A. Rossman

Bibliographic record

VenueJournal of Water Management Modeling · 2004
Typearticle
Languageen
FieldEnvironmental Science
TopicHydrology and Watershed Management Studies
Canadian institutionsUniversity of Guelph
Fundersnot available
KeywordsOpen sourceComputer scienceSource codeSoftware engineeringSoftwareOpen waterCode (set theory)Water resourcesOpen source softwareWater sourceSystems engineeringEnvironmental scienceWater resource managementEngineeringOperating systemProgramming languageMarine engineeringSet (abstract data type)

Abstract

fetched live from OpenAlex

The water resources engineering community has available an array of computer models that can be applied to support analysis, planning and design of water resources systems.Some models are software that reside in the public domain as open source code; some models are commercial software for which the source code is the proprietazy property of its owner.In selecting a model for use in supporting their work, water resources engineers are therefore faced with a basic choice-to use a public domain model, or a model that is commercial software.There are many factors that must be considered when making this choice.Careful consideration of the relevant factors reveals that there are many benefits of open source software that favor the use of public domain models.In addition to the selection of software on an individual basis, there are also a number of factors that water resources engineers should consider from the broader perspective of the benefits to their profession in supporting the continued advancement of public domain models.The various factors that should be considered are identified and evaluated.

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 imitation

Not 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.

metaresearch head score (Codex)0.006
metaresearch head score (Gemma)0.028
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesOpen science
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: none
Teacher disagreement score0.997
Threshold uncertainty score0.032

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0060.028
Meta-epidemiology (narrow)0.0010.001
Meta-epidemiology (broad)0.0000.001
Bibliometrics0.0030.005
Science and technology studies0.0010.001
Scholarly communication0.0050.010
Open science0.0030.003
Research integrity0.0020.002
Insufficient payload (model declined to judge)0.0100.003

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.040
GPT teacher head0.247
Teacher spread0.207 · 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

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

Study designNot applicable
Domainnot available
GenreEmpirical

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".

Quick stats

Citations0
Published2004
Admission routes2
Has abstractyes

Explore more

Same venueJournal of Water Management ModelingSame topicHydrology and Watershed Management StudiesFrench-language works237,207