Model:SurfaceRoughness: Difference between revisions

From CSDMS
m (Text replacement - "|IRF interface=No not possible" to "|IRF interface=Not yet")
m (Text replacement - "|OpenMI compliant=No not possible" to "|OpenMI compliant=Not yet")
Line 83: Line 83:
{{Additional comments model}}
{{Additional comments model}}
{{CSDMS staff part
{{CSDMS staff part
|OpenMI compliant=No not possible
|OpenMI compliant=Not yet
|IRF interface=Not yet
|IRF interface=Not yet
|CMT component=Not yet
|CMT component=Not yet

Revision as of 17:00, 16 August 2016



SurfaceRoughness


Metadata

Also known as
Model type Tool
Model part of larger framework
Note on status model
Date note status model
Incorporated models or components:
Spatial dimensions 2D
Spatial extent
Model domain
One-line model description Quantifies surface roughness with high-resolution topographic data by analyzing the local variability of surface normal vectors.
Extended model description This tool can be used to map out areas of hillslopes where the emergence of bedrock drives an increase in surface roughness. The tool requires an input DEM in float format and will output the rasters, also in float format, for three eigenvectors that together describe the distribution of normal vectors within a user-defined neighbourhood for each pixel. To view the paper, please see: <url>
Keywords:

Rock Exposure, Surface Roughness, LiDAR,

Name David Milodowski
Type of contact Model developer
Institute / Organization University of Edinburgh, School of GeoSciences
Postal address 1 Geography Building
Postal address 2 Drummond Street
Town / City Edinburgh
Postal code EH8 9XP
State
Country United Kingdom
Email address d.t.milodowski@ed.ac.uk
Phone
Fax


Name Simon Mudd
Type of contact Model developer
Institute / Organization University of Edinburgh, School of GeoSciences
Postal address 1 Geography Building
Postal address 2 Drummond Street
Town / City Edinburgh
Postal code EH8 9XP
State
Country United Kingdom
Email address simon.m.mudd@ed.ac.uk
Phone
Fax


Supported platforms
Linux
Other platform
Programming language

C++

Other program language
Code optimized Single Processor
Multiple processors implemented
Nr of distributed processors
Nr of shared processors
Start year development 2012
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
Source code availability
(Or provide future intension)
Through CSDMS repository
Source web address
Source csdms web address https://github.com/csdms-contrib/SurfaceRoughness
Program license type GPL v2
Program license type other
Memory requirements Memory requirements dependent on size of DEM
Typical run time 1-30 minutes


Describe input parameters The input file is a DEM in .flt format. A driver text file is also required which contains the parameters used for the extraction.
Input format
Other input format float
Describe output parameters
Output format
Other output format
Pre-processing software needed? No
Describe pre-processing software
Post-processing software needed? No
Describe post-processing software
Visualization software needed? No
If above answer is yes
Other visualization software


Describe processes represented by the model This tool maps out local surface roughness based on the neighborhood distribution of surface normal vectors. As sediment transport processes in soil mantled landscapes tend to be diffusive, the emergence of bedrock drives an increase in surface roughness that is mapped out by this algorithm.
Describe key physical parameters and equations The surface normal vector for a given pixel are defined by fitting a 6-term polynomial surface to a set of DEM points within a user-specified radius of that pixel. A second user-defined neighborhood is used to then map out the local variability in the orientation of the surface normal vectors.
Describe length scale and resolution constraints A requirement is high resolution topographic data, typically ~1m resolution. For a detailed discussion of lengthscale and resolution constraints we urge the user to refer to the original manuscript
Describe time scale and resolution constraints No time resolution constraints as this software performs topographic analysis.
Describe any numerical limitations and issues


Describe available calibration data sets
Upload calibration data sets if available:
Describe available test data sets Two test DEMs are included in the repository, alongside their respective driver files. These are used in the original manuscript.
Upload test data sets if available:
Describe ideal data for testing Any 1m resolution bare earth digital elevation model will do.


Do you have current or future plans for collaborating with other researchers? Yes
Is there a manual available? No
Upload manual if available:
Model website if any
Model forum / discussion board
Comments


This part will be filled out by CSDMS staff

OpenMI compliant Not yet"Not yet" 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 Not yet"Not yet" is not in the list (Yes, No but planned, No but possible, No not possible) of allowed values for the "Code IRF or not" property.
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:
Model info
Nr. of publications: 1
Total citations: 40
h-index: 1
m-quotient: 0.11
Qrcode SurfaceRoughness.png
Link to this page


Introduction

History

References




Nr. of publications: 1
Total citations: 40
h-index: 1
m-quotient: 0.11



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 describedCitations


Overview and general


The part "]]" of the query was not understood.</br>Results might not be as expected.
Publication(s)Model describedCitations


Applications


The part "]]" of the query was not understood.</br>Results might not be as expected.
Publication(s)Model describedCitations


Related theory and data


The part "]]" of the query was not understood.</br>Results might not be as expected.
Publication(s)Model describedCitations

Issues

Help

Input Files

Output Files