Model:TopoFlow-Saturated Zone-Darcy Layers

From CSDMS
Revision as of 20:17, 16 September 2020 by WikiSysop (talk | contribs) (Text replacement - "{{End headertab}}" to "{{End headertab}} {{{{PAGENAME}}_autokeywords}}")
{{#default_form:Module_questionnaire}}

TopoFlow-Saturated Zone-Darcy Layers


Metadata

Also known as
Model type Single
Model part of larger framework
Note on status model
Date note status model
Incorporated models or components:
Spatial dimensions {{#arraymap:2D|,|x|x"x" is not in the list (1D, 1.5D, 2D, 3D) of allowed values for the "Spatial dimensions" property.}}
Spatial extent {{#arraymap:Landscape-Scale, Watershed-Scale|,|x|x"x" is not in the list (Global, Continental, Regional-Scale, Landscape-Scale, Watershed-Scale, Reach-Scale, Patch-Scale, Grain-Scale, Point-Based) of allowed values for the "Spatialscale" property.}}
Model domain {{#arraymap:Hydrology|,|x|x"x" is not in the list (Terrestrial, Hydrology, Coastal, Marine, Geodynamic, Climate, Ecosystems, Carbonates and Biogenics, Cryosphere, Artificial Intelligence and Machine Learning, ...) of allowed values for the "ModelDomain" property.}}
One-line model description Saturated Zone process component (Darcy's law, multiple soil layers) for a D8-based, spatial hydrologic model
Extended model description This process component is part of a spatially-distributed hydrologic model called TopoFlow, but it can now be used as a stand-alone model.
Keywords:

basins,

Name Scott Peckham
Type of contact Model developer
Institute / Organization CSDMS, INSTAAR, University of Colorado
Postal address 1 1560 30th street
Postal address 2
Town / City Boulder
Postal code 80305
State Colorado
Country United States
Email address Scott.Peckham@colorado.edu
Phone 303-492-6752
Fax


Supported platforms
{{#arraymap:Unix, Linux, Mac OS, Windows|,|x|x"x" is not in the list (Unix, Linux, Mac OS, Windows) of allowed values for the "Supported platforms" property.}}
Other platform
Programming language

{{#arraymap:Python|,|x|x"x" is not in the list (Fortran77, Fortran90, C, C++, Python, Java, IDL, Matlab) of allowed values for the "Programming language" property.}}

Other program language None (but uses NumPy package)
Code optimized {{#arraymap:Single Processor|,|x|x"x" is not in the list (Single Processor, Multiple Processors) of allowed values for the "Code optimized" property.}}
Multiple processors implemented {{#arraymap:|,|x|x"x" is not in the list (Distributed memory, Shared memory) of allowed values for the "Multiple processors implemented" property.}}
Nr of distributed processors
Nr of shared processors
Start year development 2001
Does model development still take place? {{#arraymap:Yes|,|x|x"x" is not in the list (Yes, No) of allowed values for the "Development still active" property.}}
If above answer is no, provide end year model development
Code development status Active
When did you indicate the 'code development status'? 2020
Model availability {{#arraymap:As code, As teaching tool|,|x|x"x" is not in the list (As code, As teaching tool) of allowed values for the "Model availability" property.}}
Source code availability
(Or provide future intension)
{{#arraymap:Through web repository|,|x|x"x" is not in the list (Through web repository, Through CSDMS repository) of allowed values for the "Source code availability" property.}}
Source web address https://github.com/peckhams/topoflow
Source csdms web address
Program license type Apache public license
Program license type other
Memory requirements Standard
Typical run time Minutes to hours


Describe input parameters The input variables used for modeling horizontal subsurface flow in the saturated zone via Darcy's Law are defined as follows:
K_s 	= saturated hydraulic conductivity (m / s)
S_y 	= specific yield or drainable porosity (unitless)

(less than or equal to the porosity, φ, see Notes)

thickness 	= soil layer thickness (meters)
Input format {{#arraymap:ASCII, Binary|,|x|x"x" is not in the list (ASCII, Binary) of allowed values for the "Input format model" property.}}
Other input format
Describe output parameters
Output format {{#arraymap:ASCII, Binary|,|x|x"x" is not in the list (ASCII, Binary) of allowed values for the "Output format model" property.}}
Other output format
Pre-processing software needed? {{#arraymap:Yes|,|x|x"x" is not recognized as a Boolean (true/false) value.}}
Describe pre-processing software Another program must be used to create the input grids. This includes a D8 flow grid derived from a DEM for the region to be modeled. The earlier, IDL version of TopoFlow can be used to create some of these.
Post-processing software needed? {{#arraymap:Yes|,|x|x"x" is not recognized as a Boolean (true/false) value.}}
Describe post-processing software None, except visualization software. Grid sequences saved in netCDF files can be viewed as animations and saved as movies using VisIt.
Visualization software needed? {{#arraymap:Yes|,|x|x"x" is not recognized as a Boolean (true/false) value.}}
If above answer is yes {{#arraymap:|,|x|x"x" is not in the list (ESRI, IDL, Matlab) of allowed values for the "Visualization software" property.}}
Other visualization software VisIt


Describe processes represented by the model
Describe key physical parameters and equations
Describe length scale and resolution constraints Recommended grid cell size is around 100 meters, but can be parameterized to run with a wide range of grid cell sizes. DEM grid dimensions are typically less than 1000 columns by 1000 rows.
Describe time scale and resolution constraints The basic stability condition is: dt < (dx / u_min), where dt is the timestep, dx is the grid cell size and u_min is the smallest velocity in the grid. This ensures that flow cannot cross a grid cell in less than one time step. Typical timesteps are on the order of seconds to minutes. Model can be run for a full year or longer, if necessary.
Describe any numerical limitations and issues This model/component needs more rigorous testing.


Describe available calibration data sets This model/component is typically not calibrated to fit data, but is run with a best guess or measured value for each input parameter.
Upload calibration data sets if available: {{#arraymap:|,|x|Media:x}}
Describe available test data sets Available test data sets:
  • Treynor watershed, in the Nishnabotna River basin, Iowa, USA.
  • (Two large rainfall events.)
  • Small basin in Kentucky.
  • Inclined plane for testing.
  • Arctic watershed data from Larry Hinzman (UAF).
  • See /data/progs/topoflow/3.0/data on CSDMS cluster.
Upload test data sets if available: {{#arraymap:|,|x|Media:x}}
Describe ideal data for testing Several test datasets are stored on the CSDMS cluster at: /data/progs/topoflow/3.0/data.


Do you have current or future plans for collaborating with other researchers? Collaborators include: Larry Hinzman (UAF), Bob Bolton, Anna Liljedahl (UAF), Stefan Pohl and others
Is there a manual available? Yes
Upload manual if available: {{#arraymap:|,|x|Media:x}}
Model website if any This site.
Model forum / discussion board
Comments About this component:
  • This component was developed as part of the TopoFlow hydrologic model, which was originally written in IDL and had a point-and-click GUI. For more information on TopoFlow, please goto: https://csdms.colorado.edu/wiki/Model:TopoFlow.
  • When used from within the CSDMS Modeling Tool (CMT), this component has "config" button which launches a graphical user interface (GUI) for changing input parameters. The GUI is a tabbed dialog with a Help button at the bottom that displays HTML help in a browser window.
  • This component also has a configuration (CFG) file, with a name of the form: <case_prefix>_channels_diff_wave.cfg. This file can be edited with a text editor.
  • The Numerical Python module (numpy) is used for fast, array-based processing.
  • This model has an OpenMI-style interface, similar to OpenMI 2.0. Part of this interface is inherited from "CSDMS_base.py".


This part will be filled out by CSDMS staff

OpenMI compliant {{#arraymap:No but planned|,|x|x"x" is not in the list (Yes, No but planned, No but possible, No not possible) of allowed values for the "Code openmi compliant or not" property.}}
BMI compliant {{#arraymap:Yes|,|x|x"x" is not in the list (Yes, No but planned, No but possible, No not possible) of allowed values for the "BMICompliant" property.}}
WMT component {{#arraymap:Yes|,|x|x"x" is not in the list (Yes, In progress, No but possible, No not possible) of allowed values for the "Code CMT compliant or not" property.}}
PyMT component {{#arraymap:|,|x|x"x" is not in the list (Yes, In progress, No but possible, No not possible) of allowed values for the "Code PyMT compliant or not" property.}}
Is this a data component
Can be coupled with:

CanCoupleWith, CanCoupleWith, CanCoupleWith, CanCoupleWith, CanCoupleWith, CanCoupleWith, CanCoupleWith, CanCoupleWith, CanCoupleWith, CanCoupleWith,

Model info
Nr. of publications: 1
Total citations: 12
h-index: 1
m-quotient: 0.06

Link to this page



Introduction

History

References


{{#formlink:form=Reference-auto1|link text=Automatically enter Reference by DOI|link type=button|query string=RefsInt2[1][PublicationMultipleModelsCargo]=TopoFlow-Saturated Zone-Darcy Layers }} {{#formlink:form=Reference-manual1|link text=Manually enter Reference|link type=button|query string=RefsInt2[1][PublicationMultipleModelsCargo]=TopoFlow-Saturated Zone-Darcy Layers }}



Nr. of publications: 1
Total citations: 12
h-index: 1
m-quotient: 0.06



Issues

Help

Model help:TopoFlow-Saturated Zone-Darcy Layers

Input Files

Output Files