Search by property

This page provides a simple browsing interface for finding entities described by a property and a named value. Other available search interfaces include the page property search, and the ask query builder.

List of results

Model:GEOMBEST-Plus + (Description: ''Note: See also the GEOMBEST … Description:''Note: See also the GEOMBEST+ Users Guide'', section 6 A minimum of four excel files are required to run a GEOMBEST-Plus simulation: an “erosionresponse” file, an “accretionresponse” file, a “run#” file, and a “tract#” file. If the simulation involves a single coastal tract then the files must be titled “erosionresponse”, “accretionreponse”, “run1” file and “tract1.” Quasi-3D simulations require additional files with sequential numbers. For example a simulation involving 3 tracts within a littoral cell also requires a “run2” and “run3” file as well as a “tract2” and “tract3” file. These files must conform to the strict format outlined in the following sections. If you are running multiple simulations of the same tract, you can use the multiple input and output files to keep track of your simulations. Caution: Note that the run# and tract# files will have the same name (tract1, run1, etc., see below) for all simulations and so attention to organization is critical. We suggest noting the changes made in each simulation in a readme file and then moving this file, as well as the input and output folders for each simulation, to a unique folder having an identifying name. Our convention, for example, has been to name each run with using the date and run number on that date as the identifier, e.g., the first simulation run on February 20, 2010 would be titled 02_20_10_01and would be placed in a folder having this name.'''6.1: “erosionresponse” file''' '''6.2: “accretionresponse” file''' '''6.3: “run#” file''' '''6.4: “tract#” file'''t;br> '''6.3: “run#” file''' '''6.4: “tract#” file''')
Model:TauDEM + (Digital elevation model)
Model:OTTAR + (Discharge, channel properties)
Model:Kirwan marsh model + (Does not require any input data, but if desired, model can run from files describing sea level and/or the elevations of an existing marsh.)
Model:CellularFanDelta + (Domain dimensions and cell size (regular 2 … Domain dimensions and cell size (regular 2D grid). Initial condition.Locations and rates of sediment and water influxes. Subsidence pattern and rate. Sea level curve. (Presently all boundary conditions are constant, but could vary in space and time in future versions)vary in space and time in future versions))
Model:BRaKE + (Domain size/length/spacing, time to run, t … Domain size/length/spacing, time to run, timestep, hillslope response timescale, baselevel lowering rate, bed erodibility, block erodibility, bed critical shear stress, block critical shear stress, block delivery coefficient, initial block size, roughness length scale, channel width, mean discharge, discharge variability, and data recording time interval.ability, and data recording time interval.)
Model:HydroTrend + (Drainage basin properties (river networks, hypsometry, relief, reservoirs). biophysical parameters (temperature, precipitation, evapo-transpiration, and glacier characteristics).)
Model:SFINCS + (Elevation file and a mask file designating boundary cells, active cells, and inactive cells)
Model:GEOMBEST + (Excel files. See User's Guide and Moore et al., 2010)
Model:1DBreachingTurbidityCurrent + (Excel sheet. User can change initial geome … Excel sheet. User can change initial geometry data (slope at top of breach, initial height of breach face, initial bed slope in quasi-horizontal region, initial location of breach face, initial length of quasi-horizontal region); sediment grain size distribution; sediment properties (bed porosity, breach porosity, bed friction coefficient, wall friction coefficient, submerged specific gravity); and time evolution (time step, number of time steps, initial number of nodes in horizontal, print interval, calculation time).zontal, print interval, calculation time).)

Model:SVELA + (Flow velocity, friction slope, hydraulic radius, and bed roughness)

Model:WRF-Hydro + (For a complete explanation of input parame … For a complete explanation of input parameters please see the WRF-Hydro Technical Description https://ral.ucar.edu/projects/wrf_hydro/technical-description-user-guideWRF-Hydro requires a number of input files describing the model domain, parameters, initialconditions, hydrologic routing, and when run in a standalone configuration, meteorological forcing files.nfiguration, meteorological forcing files.)
Model:DLBRM + (For every cell in the watershed grid, dail … For every cell in the watershed grid, daily precipitation and air temperature, solar isolation, elevation, slope, flow direction, land use, depths (cm) of USZ (Upper Soil Zone) and LSZ (Lower Soil Zone), available water capacity (%) of USZ and LSZ, soil texture, permeability (cm/h) of USZ and LSZ, Manning's coefficient values, and daily flows (Changsheng He and Thomas E. Croley II, 2007).ngsheng He and Thomas E. Croley II, 2007).)
Model:TopoFlow-Diversions + (For sources and sinks, the following infor … For sources and sinks, the following information must be provided, each on its own line: ID (source pixel ID as long integer; calendar index) nd (number of durations and flow rates) durations (vector of durations in minutes) flow rates (vector of discharges in m^3/sec)For canals, the following information must be provided, again with each entry on a separate line in the text file: ID1 (start pixel ID as long integer; calendar index) ID2 (end pixel ID as long integer; calendar index) time (travel time between ID1 and ID2, in minutes) nd (number of durations and flow rates) durations (vector of durations in minutes) flow rates (vector of discharges in m^3/sec)Canals are currently assumed to be lossless, so that the flow rates at the two ends are identical, but lagged by the travel time. 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: 0 Method name: Standard Use sources: 0 Treynor_sources.txt (N/A) Use sinks: 0 Treynor_sinks.txt (N/A) Use canals: 0 Treynor_canals.txt (N/A) Treynor_canals.txt (N/A))
Model:WACCM-EE + (GCM initial conditions files (netcdf) files describe initial state of atmosphere up ~km 140)
Model:TopoToolbox + (GeoTiff, ESRI ASCII digital elevation model)
Model:LateralVerticalIncision + (Geometric parameters of river reach and erosion capacity.)
Model:DeltaClassification + (Geometric parameters on delta shapes deriv … Geometric parameters on delta shapes derived from satellite data. To run this code, the following shape files are required:• network shapefile, containing the river network extracted from satellite imagery• island shapefile, containing the land masses or islands of the delta• patch shapefile, containing the outline of channelspefile, containing the outline of channels)
Model:Pllcart3d + (Geometrical parameters: Nx, Ny, Nz, X1, X2, Y1, Y2, Z1, Z2; Flow parameters: Reynolds, Peclet, Viscosity Ratio; Flags: resume simulation, add wave perturbation.)
Model:LOADEST + (Given a time series of streamflow, additional data variables, and constituent concentration, LOADEST assists the user in developing a regression model for the estimation of constituent load (calibration).)
Model:VIC + (Global Parameter File user_def.h File Meteorological Forcing Files Soil Parameter File Vegetation Library File Vegetation Parameter File (Optional) Initial State File (Optional) Elevation Band File (Optional) Lake/Wetland Parameter File)