Summary
| Also known as
|
|
| Model type
|
Single
|
| Model part of larger framework
|
|
| Note on status model
|
|
| Date note status model
|
|
Technical specs
| Supported platforms
|
Unix, Linux, Windows
|
| Other platform
|
|
| Programming language
|
Fortran90, Matlab
|
| Other program language
|
|
| Code optimized
|
Single Processor, Parallel
Computing"Parallel </br>Computing" is not in the list (Single Processor, Multiple Processors) of allowed values for the "Code optimized" property.
|
| Multiple processors implemented
|
|
| Nr of distributed processors
|
|
| Nr of shared processors
|
|
| Start year development
|
2000
|
| 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 executable"As executable" 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)
|
Through owner"Through owner" is not in the list (Through web repository, Through CSDMS repository) of allowed values for the "Source code availability" property.
|
| Source web address
|
|
| Source csdms web address
|
|
| Program license type
|
Other
|
| Program license type other
|
|
| Memory requirements
|
|
| Typical run time
|
it takes less than a minite to run the serial model for one with daily time interval
|
In/Output
| Describe input parameters
|
Upper Boundary (Air temperature)
Lower Boundary (Temperature gradient)
Initial conditions (Temperature distribution at initial time)
Thermo-physical properties
|
| Input format
|
ASCII
|
| Other input format
|
|
| Describe output parameters
|
Temperature distribution with depth
Active Layer Depth
Freezing/Thawing day
|
| Output format
|
ASCII
|
| Other output format
|
netcdf, GIS
|
| Pre-processing software needed?
|
Yes
|
| Describe pre-processing software
|
For spatial case one can developed its own pre-processing in order to put the input dataset in the format readable for GIPL.
|
| Post-processing software needed?
|
Yes
|
| Describe post-processing software
|
To generate netcdf or GIS outputs one can write its own converter for that.
|
| Visualization software needed?
|
Yes
|
| If above answer is yes
|
ESRI, Matlab
|
| Other visualization software
|
Matlab, Microsoft Excel (for serial); Matlab, ARCGIS, ncview (for spatial model)
|
Process
| Describe processes represented by the model
|
Main purpose of the model is to calculate subsurface temperature profile, active layer depth and freeze-up day.
|
| Describe key physical parameters and equations
|
Thermal capacities and conductivities prescribed for each subsurface layer, volumetric water content and unfrozen water coefficients.
|
| Describe length scale and resolution constraints
|
|
| Describe time scale and resolution constraints
|
|
| Describe any numerical limitations and issues
|
|
Testing
| Describe available calibration data sets
|
We have tested the model for different permafrost observation sites for Alaska(USA) and Siberia(Russia). Typically, the model results show good correlation with measured data (if observations are accurate).
|
| Upload calibration data sets if available:
|
|
| Describe available test data sets
|
|
| Upload test data sets if available:
|
|
| Describe ideal data for testing
|
|
Other
| Do you have current or future plans for collaborating with other researchers?
|
|
| Is there a manual available?
|
No
|
| Upload manual if available:
|
|
| Model website if any
|
|
| Model forum / discussion board
|
|
Introduction
GIPL(Geophysical Institute Permafrost Laboratory) is an implicit finite difference one-dimensional heat flow numerical model. The model was developed by V.Romanovsky and G. Tipenko at University of Alaska Fairbanks. The model uses coarse vertical resolution grid which preserves the latent-heat effects in the phase transition zone, even under conditions of rapid or abrupt changes in the temperature fields. The air temperature is a driving force for the GIPL upper boundary condition and constant geothermal heat flux at the lower boundary (typically from 500 to 1000 m). The other inputs are precipitation, prescribed water content and thermal properties of the multilayered soil column. As an output the model produces temperature distributions at different depths, active layer thickness and calculates time of freeze up.
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 |Email address=gtucker@colorado.edu |Phone=+1 303 492 6985 |Fax=+1 303 492 2606 }}
GIPL
Metadata
Summary
| Also known as
|
|
| Model type
|
Modular
|
| Model part of larger framework
|
|
| Note on status model
|
|
| Date note status model
|
|
Technical specs
| Supported platforms
|
Unix, Linux, Mac OS
|
| Other platform
|
|
| Programming language
|
C++
|
| Other program language
|
|
| Code optimized
|
|
| Multiple processors implemented
|
|
| Nr of distributed processors
|
|
| Nr of shared processors
|
|
| Start year development
|
1997
|
| 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 executable"As executable" 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)
|
Through CSDMS repository
|
| Source web address
|
|
| Source csdms web address
|
|
| Program license type
|
GPL v2
|
| Program license type other
|
|
| Memory requirements
|
depends on grid size
|
| Typical run time
|
minutes to days
|
In/Output
| 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
|
| Other input format
|
|
| 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
|
| Other output format
|
|
| Pre-processing software needed?
|
No
|
| Describe pre-processing software
|
|
| 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.
|
| Visualization software needed?
|
Yes
|
| If above answer is yes
|
ESRI, IDL, Matlab
|
| Other visualization software
|
|
Process
| 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 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 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.
|
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.
|
| Upload calibration data sets if available:
|
|
| Describe available test data sets
|
(pending)
|
| Upload test data sets if available:
|
|
| Describe ideal data for testing
|
See Tucker, 2009 (in review)
|
Other
| Do you have current or future plans for collaborating with other researchers?
|
Yes, both.
|
| Is there a manual available?
|
Yes
|
| Upload manual if available:
|
|
| Model website if any
|
The CSDMS web site (this model section)
|
| Model forum / discussion board
|
|
| Comments
|
Updated manual is forthcoming ...
|
Example Spatial Mapping of Active layer depth for Alaska
Scenario 1: A1B
History
Papers
Issues
Help
Input Files
Output Files
Download
Source |
|
