Model:TopoFlow-Meteorology: Difference between revisions

Revision as of 20:34, 21 July 2015

TopoFlow-Meteorology

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	2D
Spatial extent	Landscape-Scale, Watershed-Scale
Model domain
One-line model description	Meteorology process component 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	Unix, Linux, Mac OS, Windows
Other platform
Programming language	Python
Other program language	None (but uses NumPy package)
Code optimized	Single Processor
Multiple processors implemented
Nr of distributed processors
Nr of shared processors
Start year development	2001
Does model development still take place?	Yes
If above answer is no, provide end year model development
Code development status
When did you indicate the 'code development status'?
Model availability	As code, As teaching tool
Source code availability (Or provide future intension)	Through web repository
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 for modeling the net flux of shortwave radiation are defined as follows: Tair = air temperature (deg C) RH = relative humidity (unitless) (in (0,1)) albedo = surface albedo (unitless) (in (0,1)) dust att. = dust attenuation factor (unitless) (in (0,1)) factor = cloud or canopy cover factor (unitless) (in (0,1)) slope = topographic slope (unitless, m/m) (in (0,Infinity)) aspect = aspect angle (radians) (in (0,1)) The behavior of this component is controlled with a configuration (CFG) file, which may point to other files that contain input data. Here is a sample configuration (CFG) file for this component: Method code: 1 Method name: Standard Time step: Scalar 3600.0 (sec) rho_H2O: Scalar 1000.00000000 (kg/m^3) Cp_air: Scalar 1005.70001221 (J/kg/K) rho_air: Scalar 1.26139998 (kg/m^3) P: Time_series Case5_rain_rates.txt (mm/hr) T_air: Scalar 20.00000000 (deg C) T_surf: Scalar -5.00000000 (deg C) RH: Scalar 0.50000000 (none) p0: Scalar 1000.00000000 (mbar) uz: Scalar 3.00000000 (m/s) z: Scalar 10.00000000 (m) z0_air: Scalar 0.02000000 (m) Qn_SW: Scalar 100.00000000 (W/m^2) Qn_LW: Scalar 10.00000000 (W/m^2) Save grid timestep: Scalar 60.00000000 (sec) Save ea grids: 0 Case5_2D-ea.rts (mbar) Save es grids: 0 Case5_2D-es.rts (mbar) Save pixels timestep: Scalar 60.00000000 (sec) Save ea pixels: 0 Case5_0D-ea.txt (mbar) Save es pixels: 0 Case5_0D-es.txt (mbar)
Input format	ASCII, Binary
Other input format
Describe output parameters
Output format	ASCII, Binary
Other output format
Pre-processing software needed?	Yes
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?	Yes
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?	Yes
If above answer is yes
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:
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:
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:
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: http://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	No but planned
BMI compliant	Yes
WMT component	Not yet"Not yet" 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
Is this a data component

Can be coupled with:	CanCoupleWith, CanCoupleWith, CanCoupleWith, CanCoupleWith, CanCoupleWith, CanCoupleWith, CanCoupleWith, CanCoupleWith, CanCoupleWith, CanCoupleWith, CanCoupleWith, CanCoupleWith, CanCoupleWith,

Model info

Authors

Scott Peckham

Source code

Go to external source code site

Model citations

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

QR-code

Link to this page

Introduction

History

References

Source code

Suggested way to reference a version of the model source code following data reference guidelines:

The part "]]" of the query was not understood.</br>Results might not be as expected.

Publication(s)	Model described	Citations

Overview and general

The part "]]" of the query was not understood.</br>Results might not be as expected.

Publication(s)	Model described	Citations

Applications

The part "]]" of the query was not understood.</br>Results might not be as expected.

Publication(s)	Model described	Citations

Related theory and data

The part "]]" of the query was not understood.</br>Results might not be as expected.

Publication(s)	Model described	Citations

Issues

Help

Model help:TopoFlow-Meteorology

Input Files

Output Files