Model:CHILD: Difference between revisions
m (Removed old questionniare information. Replaced with form.) |
No edit summary |
||
Line 3: | Line 3: | ||
|Last name=Tucker | |Last name=Tucker | ||
|Type of contact=Model developer | |Type of contact=Model developer | ||
|Institute / Organization=Cooperative Institute for Research in Environmental Sciences (CIRES) and Department of Geological Sciences at the University of Colorado | |Institute / Organization=Cooperative Institute for Research in Environmental Sciences (CIRES) and Department of Geological Sciences at the University of Colorado | ||
|Postal address 1=University of Colorado | |Postal address 1=University of Colorado | ||
|Postal address 2=Campus Box 399 | |Postal address 2=Campus Box 399 | ||
Line 18: | Line 18: | ||
|Categories=Terrestrial | |Categories=Terrestrial | ||
|Spatial dimensions=3D | |Spatial dimensions=3D | ||
|One-line model description=Landscape Evolution Model | |One-line model description=Landscape Evolution Model | ||
|Extended model description=CHILD computes the time evolution of a topographic surface z(x,y,t) by fluvial and hillslope erosion and sediment transport. | |Extended model description=CHILD computes the time evolution of a topographic surface z(x,y,t) by fluvial and hillslope erosion and sediment transport. | ||
}} | }} | ||
{{Model technical information | {{Model technical information | ||
|Supported platforms=Unix, Linux, Mac OS | |Supported platforms=Unix, Linux, Mac OS | ||
|Programming language=C | |Programming language=C++ | ||
|Start year development=1997 | |Start year development=1997 | ||
|Does model development still take place?=Yes | |Does model development still take place?=Yes | ||
Line 32: | Line 32: | ||
|CCA component=No but possible | |CCA component=No but possible | ||
|IRF interface=Yes | |IRF interface=Yes | ||
|Memory requirements=depends on grid size | |Memory requirements=depends on grid size | ||
|Typical run time=minutes to days | |Typical run time=minutes to days | ||
}} | }} | ||
{{Input - Output description | {{Input - Output description | ||
|Describe input parameters=Topography z(x,y) or parameters describing a topographic surface; rate coefficients; switches for activating options and choosing between alternative transport/erosion formulas. Uses a formatted text file for input of parameters. | |Describe input parameters=Topography z(x,y) or parameters describing a topographic surface; rate coefficients; switches for activating options and choosing between alternative transport/erosion formulas. Uses a formatted text file for input of parameters. | ||
|Input format=ASCII | |Input format=ASCII | ||
|Describe output parameters=Outputs include grids of surface elevation, drainage area, gradient, stratigraphy, drainage direction, Voronoi cell areas, sediment texture; data on mesh configuration; total landscape volume and change in volume at each storm (time step); list of storm durations, timing, and intensities. | |Describe output parameters=Outputs include grids of surface elevation, drainage area, gradient, stratigraphy, drainage direction, Voronoi cell areas, sediment texture; data on mesh configuration; total landscape volume and change in volume at each storm (time step); list of storm durations, timing, and intensities. | ||
|Output format=ASCII | |Output format=ASCII | ||
|Pre-processing software needed?=No | |Pre-processing software needed?=No | ||
|Post-processing software needed?=Yes | |Post-processing software needed?=Yes | ||
|Describe post-processing software=Yes, An extensive library of Matlab scripts provides visualization and post-processing capabilities. A few scripts also exist for IDL, and it is possible to process the output to generate lists of points for input to ArcGIS. | |Describe post-processing software=Yes, An extensive library of Matlab scripts provides visualization and post-processing capabilities. A few scripts also exist for IDL, and it is possible to process the output to generate lists of points for input to ArcGIS. | ||
|Visualization software needed?=Yes | |Visualization software needed?=Yes | ||
|If above answer is yes=ESRI, IDL, Matlab | |If above answer is yes=ESRI, IDL, Matlab | ||
}} | }} | ||
{{Process description model | {{Process description model | ||
|Describe processes represented by the model=Main processes include runoff generation, fluvial erosion and sediment transport, and sediment transport by soil creep. | |Describe processes represented by the model=Main processes include runoff generation, fluvial erosion and sediment transport, and sediment transport by soil creep. | ||
|Describe key physical parameters and equations=Too many to list here -- see Tucker et al. (2001a), the CHILD Users Guide, and other documents listed in the bibliography. | |Describe key physical parameters and equations=Too many to list here -- see Tucker et al. (2001a), the CHILD Users Guide, and other documents listed in the bibliography. | ||
|Describe length scale and resolution constraints=In principle, the model can address spatial scales ranging from gullies and small (~1km2) catchments to mountain ranges, as long as setup and parameters are chosen appropriately. Resolutions greater than about 10,000 nodes normally require significant computation time. | |Describe length scale and resolution constraints=In principle, the model can address spatial scales ranging from gullies and small (~1km2) catchments to mountain ranges, as long as setup and parameters are chosen appropriately. Resolutions greater than about 10,000 nodes normally require significant computation time. | ||
|Describe time scale and resolution constraints=The steady flow assumption used by most (not all) hydrology sub-models restricts time scale to periods significantly longer than a single storm. The model has been mostly used to address time scales relevant to significant topographic evolution, though in the case of rapidly changing landscapes (e.g., gully networks) this can be as short as decades. | |Describe time scale and resolution constraints=The steady flow assumption used by most (not all) hydrology sub-models restricts time scale to periods significantly longer than a single storm. The model has been mostly used to address time scales relevant to significant topographic evolution, though in the case of rapidly changing landscapes (e.g., gully networks) this can be as short as decades. | ||
|Describe any numerical limitations and issues=The fluvial sediment transport equations are quasi-diffusive and typically have orders of magnitude spatial variations in rate coefficient (reflecting differences in water discharge), which makes the system of equations stiff and difficult to solve efficiently. | |Describe any numerical limitations and issues=The fluvial sediment transport equations are quasi-diffusive and typically have orders of magnitude spatial variations in rate coefficient (reflecting differences in water discharge), which makes the system of equations stiff and difficult to solve efficiently. | ||
}} | }} | ||
{{Model testing | {{Model testing | ||
|Describe available calibration data sets=The model has been benchmarked against analytical solutions for simple cases, such as fluvial slope-area scaling and parabolic to parabolic-planar hillslope form under uniform erosion, materials, and climate. Testing and calibration of some of the individual components (e.g., linear and nonlinear soil creep, stream-power fluvial erosion law, etc.) have been reported in the literature (for a review, see Tucker and Hancock, 2009). Testing of the full coupled model using natural experiments (Tucker, 2009) is ongoing. | |Describe available calibration data sets=The model has been benchmarked against analytical solutions for simple cases, such as fluvial slope-area scaling and parabolic to parabolic-planar hillslope form under uniform erosion, materials, and climate. Testing and calibration of some of the individual components (e.g., linear and nonlinear soil creep, stream-power fluvial erosion law, etc.) have been reported in the literature (for a review, see Tucker and Hancock, 2009). Testing of the full coupled model using natural experiments (Tucker, 2009) is ongoing. | ||
|Describe available test data sets=(pending) | |Describe available test data sets=(pending) | ||
|Describe ideal data for testing=See Tucker, 2009 (in review) | |Describe ideal data for testing=See Tucker, 2009 (in review) | ||
}} | }} | ||
{{Users groups model | {{Users groups model | ||
Line 62: | Line 62: | ||
}} | }} | ||
{{Documentation model | {{Documentation model | ||
|Provide key papers on model if any=Tucker, G.E., Lancaster, S.T., Gasparini, N.M., and Bras, R.L. (2001) The Channel-Hillslope Integrated Landscape Development (CHILD) Model, in Landscape Erosion and Evolution Modeling, edited by R.S. Harmon and W.W. Doe III, Kluwer Academic/Plenum Publishers, pp. 349-388. | |Provide key papers on model if any=Tucker, G.E., Lancaster, S.T., Gasparini, N.M., and Bras, R.L. (2001) The Channel-Hillslope Integrated Landscape Development (CHILD) Model, in Landscape Erosion and Evolution Modeling, edited by R.S. Harmon and W.W. Doe III, Kluwer Academic/Plenum Publishers, pp. 349-388. | ||
|Manual model available=Yes | |Manual model available=Yes | ||
|Model website if any='''The CSDMS web site''' (this model section) | |Model website if any='''The CSDMS web site''' (this model section) | ||
}} | }} | ||
{{Additional comments model | {{Additional comments model | ||
|Comments=Updated manual is forthcoming ... | |Comments=Updated manual is forthcoming ... | ||
}} | }} | ||
{{Infobox Model | {{Infobox Model |
Revision as of 19:43, 26 October 2009
Contact
Name | Greg Tucker |
Type of contact | Model developer |
Institute / Organization | Cooperative Institute for Research in Environmental Sciences (CIRES) and Department of Geological Sciences at the University of Colorado |
Postal address 1 | University of Colorado |
Postal address 2 | Campus Box 399 |
Town / City | Boulder |
Postal code | 80309 |
State | Colorado |
Country | USA"USA" is not in the list (Afghanistan, Albania, Algeria, Andorra, Angola, Antigua and Barbuda, Argentina, Armenia, Australia, Austria, ...) of allowed values for the "Country" property. |
Email address | gtucker@colorado.edu |
Phone | +1 303 492 6985 |
Fax | +1 303 492 2606 |
CHILD
Metadata
Summary
Technical specs
In/Output
Process
Testing
Other
Channel-Hillslope Integrated Landscape Development (CHILD) ModelCHILD was originally developed in 1997 by Nicole Gasparini, Stephen Lancaster, and Greg Tucker, in a research group directed by Rafael Bras at the Department of Civil and Environmental Engineering at MIT. Development and use of CHILD continues, with contributions by (among others) Mikael Attal (Edinburgh), Patrick Bogaart (Wageningen), Quintijn Clevis (Oxford), Daniel Collins (Wisconsin), Arnaud Desitter (Oxford), Homero Flores (MIT), Erkan Istanbulluoglu (Nebraska), Scott Miller (Syracuse), Vanessa Teles (IFP), and the original developers. Example SimulationsFault block uplift and subsidence<localVideo width="200" height="150" image="Child_Fault_Basin_4m.png" caption="Fault block uplift and subsidence" type="video/msvideo"> Child_Fault_Basin_4m.avi </localVideo> Simulation of a pair of normal-fault blocks separated by a vertical fault. The lower left edge is fixed through time, and represents a shallow shelf just below sea level. The inner block of the landscape rises at a steady rate, while the outer block subsides. Initially, the relief and erosion rate are small, and the subsiding basin is underfilled. Notice the progradation of a fan-delta complex. As relief and sediment flux increase, the fan deltas reach the shallow shelf and the basin becomes filled (or "over-filled" as they say, meaning that there is more than enough sediment to keep filling the basin as it continues to subside). Evolution of river valley landscape, stratigraphy, and geoarchaeologyScenario 1: Steady Aggradation
Scenario 2: Pomme de Terre River incision/aggradation history
Scenario 3: incision/aggradation history based on oxygen isotope curve
ReferencesOverview and General
Applications
A Sampling of Related Theory and Data
IssuesJanuary 29, 2009 Philippe Steer reports: I am Philippe Steer, PhD student at Geosciences Montpellier in France. I have encountered an error when trying to compile child: "INT_MAX" was not declared in this scope /Code/tMesh/tMesh.cpp Solution to this problem: add "#include <limits.h>" at the begining of tMesh.cpp Configuration: OS: linux- Opensuse11 Computer: Dell Precision T 7400, Intel Xeon, 64 bits compiling with gcc 4.3 I hope it will help other newbies (as I am!) in C, Philippe HelpInput FilesOutput FilesDownloadSource |