GSFLOW-GRASS v1.0.0: GIS-enabled hydrologic modeling ofcoupled groundwater–surface-water systems
Bibliographic record
Abstract
Abstract. Water flow through catchments sustains ecosystems and human activity, shapes landscapes, and links climate to the outermost layers of the solid Earth. The profound importance of water moving between the atmosphere and aquifers has led to efforts to develop and maintain coupled models of surface water and groundwater. However, developing inputs to these models is usually time-consuming and requires extensive knowledge of software engineering, often prohibiting their use by many researchers and water managers, and thus reducing these models' potential to promote science-driven decision-making in an era of global change and increasing water-resource stress. In response to this need, we have developed GSFLOW-GRASS, a straightforward set of open-source tools that develops inputs for and runs GSFLOW, the U.S. Geological Survey's coupled groundwater-surface-water flow model. As inputs, GSFLOW-GRASS requires at a minimum a digital elevation model, a precipitation and temperature record, and estimates of channel parameters and hydraulic conductivity. GSFLOW-GRASS is written in Python as a set of (1) GRASS GIS extensions, (2) input-file-builder scripts, and (3) visualization scripts. We developed a set of custom GRASS GIS commands that generate "hydrologic response units" for surface water, discretized topologically as sub-basins of the tributary network; build the MODFLOW grid; and add necessary attributes to each of these geospatial units. These GIS outputs are interpreted by a second set of Python scripts, which link them to hydrologic variables, build inputs to GSFLOW, and run GSFLOW. Lastly, GSFLOW output files are used to produce figures and time-lapse movies of simulation results using a third set of post-processing Python scripts. We demonstrate the broad applicability of these tools to diverse settings through examples based on: the high Peruvian Andes, the Channel Islands of California, and the formerly-glaciated Upper Mississippi valley in Minnesota.
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 imitationNot 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.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.013 | 0.002 |
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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
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".