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:TopoFlow-Saturated Zone-Darcy Layers + (The input variables used for modeling hori … The input variables used for modeling horizontal subsurface flow in the saturated zone via Darcy's Law are defined as follows: K_s = saturated hydraulic conductivity (m / s) S_y = specific yield or drainable porosity (unitless) (less than or equal to the porosity, φ, see Notes) thickness = soil layer thickness (meters)thickness = soil layer thickness (meters))
Model:TopoFlow-Infiltration-Richards 1D + (The input variables used for modeling infi … The input variables used for modeling infiltration and unsaturated vertical flow with the 1D Richard's equation are defined as follows: K_s = saturated hydraulic conductivity (m / s) K_i = initial hydraulic conductivity (m / s) (typically much less than K_s) θ_s = soil water content at ψ = 0 (unitless) (often set to the soil porosity, φ) θ_i = initial soil water content (unitless) θ_r = residual soil water content (unitless) (must be < θ_i) ψ_B = bubbling pressure head (meters) (also called air-entry pressure, ψ_ae) ψ_A = pressure head offset parameter (meters) λ = pore-size distribution parameter (unitless) (alt. notation = 1/b ) η = 2 + (3 * λ) (unitless) (see Notes) c = transitional Brooks-Corey curvature parameter (unitless) (see Notes) dznodes = vertical distance between nodes (meters) nnodes = number of subsurface vertical nodes The behavior of this component is controlled with a configuration (CFG) file, which may point to other files that contain input data.point to other files that contain input data.)
Model:TopoFlow-Snowmelt-Degree-Day + (The input variables used for the Degree-Da … The input variables used for the Degree-Day method of estimating runoff due to snowmelt are defined as follows: c_0 = coefficient T_0 = threshold temperature (deg C) T_air = air temperature (deg C) ρ_snow = density of the snow (kg / m^3) ρ_water = density of liquid water, 1000 (kg / m^3) h0_snow = initial snow depth (m) h0_swe = initial depth, snow water equivalent (m)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: Degree-Day Time step: Scalar 3600.00000000 (sec) Cp_snow: Scalar 2090.00000000 (J/kg/K) rho_snow: Scalar 300.00000000 (kg/m^3) c0: Scalar 2.70000005 (mm/day/deg C) T0: Scalar -0.20000000 (deg C) h0_snow: Scalar 0.50000000 (m) h0_swe: Scalar 0.15000000 (m) Save grid timestep: Scalar 60.00000000 (sec) Save mr grids: 0 Case5_2D-SMrate.rts (m/s) Save hs grids: 0 Case5_2D-hsnow.rts (m) Save sw grids: 0 Case5_2D-hswe.rts (m) Save cc grids: 0 Case5_2D-Ecc.rts (J/m^2) Save pixels timestep: Scalar 60.00000000 (sec) Save mr pixels: 0 Case5_0D-SMrate.txt (m/s) Save hs pixels: 0 Case5_0D-hsnow.txt (m) Save sw pixels: 0 Case5_0D-hswe.txt (m) Save cc pixels: 0 Case5_0D-Ecc.txt (J/m^2) Case5_0D-Ecc.txt (J/m^2))
Model:TopoFlow-Channels-Dynamic Wave + (The input variables used for the Dynamic W … The input variables used for the Dynamic Wave method of routing flow in channels are defined as follows. These inputs must be provided as grids:*flow_codes = D8 flow codes (Jenson convention), (NE,E,SE,S,SW,W,NW,N) → (1,2,4,8,16,32,64,128)*bed_slope = slope of the channel bed or hillslope (m / m)*Manning_n = Manning roughness parameter (s / m1/3)*bed_width = bed width for trapezoidal cross-section (m)*bank_angle = bank angle for trapezoid (deg) (from vertical)*sinuosity = channel sinuosity (unitless) (along-channel / straight length)*init_depth = initial water depth (m) (See Notes below) These inputs can be provided as scalars or grids:*sinuosity = channel sinuosity (m/m) (along-channel / straight length)*init_depth = initial water depth (m) (See HTML help) Grids must be saved in binary files with no header. All variables should be stored as 4-byte, floating-point numbers (IEEE standard) except flow codes, which are unsigned, 1-byte integers.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: 3 Method name: Dynamic_Wave Manning flag: 1 Law of Wall flag: 0 Time step: Scalar 6.00000000 (sec) D8 flow code: Grid Treynor_flow.rtg (none) D8 slope: Grid Treynor_slope.rtg (m/m) Manning N: Grid Treynor_chan-n.rtg (s/m^(1/3)) Bed width: Grid Treynor_chan-w.rtg (m) Bank angle: Grid Treynor_chan-a.rtg (deg) Init. depth: Scalar 0.00000000 (m) Sinuosity: Scalar 1.00000000 (m/m) Save grid timestep: Scalar 60.00000000 (sec) Save Q grids: 1 Case5_2D-Q.rts (m^3/s) Save u grids: 0 Case5_2D-u.rts (m/s) Save d grids: 0 Case5_2D-d.rts (m) Save f grids: 0 Case5_2D-f.rts (none) Save pixels timestep: Scalar 60.00000000 (sec) Save Q pixels: 1 Case5_0D-Q.txt (m^3/s) Save u pixels: 0 Case5_0D-u.txt (m/s) Save d pixels: 0 Case5_0D-d.txt (m) Save f pixels: 0 Case5_0D-f.txt (none) Case5_0D-f.txt (none))
Model:TopoFlow-Channels-Kinematic Wave + (The input variables used for the Dynamic W … The input variables used for the Dynamic Wave method of routing flow in channels are defined as follows. These inputs must be provided as grids:*flow_codes = D8 flow codes (Jenson convention), (NE,E,SE,S,SW,W,NW,N) → (1,2,4,8,16,32,64,128)*bed_slope = slope of the channel bed or hillslope (m / m)*Manning_n = Manning roughness parameter (s / m^1/3)*bed_width = bed width for trapezoidal cross-section (m)*bank_angle = bank angle for trapezoid (deg) (from vertical)*sinuosity = channel sinuosity (unitless) (along-channel / straight length)*init_depth = initial water depth (m) (See Notes below) These inputs can be provided as scalars or grids:*sinuosity = channel sinuosity (m/m) (along-channel / straight length)*init_depth = initial water depth (m) (See HTML help) Grids must be saved in binary files with no header. All variables should be stored as 4-byte, floating-point numbers (IEEE standard) except flow codes, which are unsigned, 1-byte integers.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: Kinematic_Wave Manning flag: 1 Law of Wall flag: 0 Time step: Scalar 6.00000000 (sec) D8 flow code: Grid Treynor_flow.rtg (none) D8 slope: Grid Treynor_slope.rtg (m/m) Manning N: Grid Treynor_chan-n.rtg (s/m^(1/3)) Bed width: Grid Treynor_chan-w.rtg (m) Bank angle: Grid Treynor_chan-a.rtg (deg) Init. depth: Scalar 0.00000000 (m) Sinuosity: Scalar 1.00000000 (m/m) Save grid timestep: Scalar 60.00000000 (sec) Save Q grids: 1 Case5_2D-Q.rts (m^3/s) Save u grids: 0 Case5_2D-u.rts (m/s) Save d grids: 0 Case5_2D-d.rts (m) Save f grids: 0 Case5_2D-f.rts (none) Save pixels timestep: Scalar 60.00000000 (sec) Save Q pixels: 1 Case5_0D-Q.txt (m^3/s) Save u pixels: 0 Case5_0D-u.txt (m/s) Save d pixels: 0 Case5_0D-d.txt (m) Save f pixels: 0 Case5_0D-f.txt (none) Case5_0D-f.txt (none))
Model:UEB + (The model is driven by inputs of air temperature, precipitation, wind speed, humidity and radiation at time steps sufficient to resolve the diurnal cycle (six hours or less))
Model:1D Particle-Based Hillslope Evolution Model + (The model takes as input (i) p, dynamics asymmetry parameter; (ii) L, the hillslope length; (iii) H, the hillslope height; (iv) N, the number of steps of the simulation; and (v) a choice of initial hillslope profile.)
Model:BarrierBMFT + (The use of this coupled model framework re … The use of this coupled model framework requires Barrier3D v2.0 (https://doi.org/10.5281/zenodo.7604068) and PyBMFT-C v1.0 (https://doi.org/10.5281/zenodo.7853803).1) barrier3d-parameters.yaml: yaml-formatted text file containing initial values for all static and dynamic variables2) barrier3d-elevation.npy: Initial interior elevation grid3) barrier3d-storms.npy: Stochastically generated sequence of storms4) barrier3d-dunes.npy: Initial height of dune cells5) barrier3d-growthparam.npy: Alongshore varying growth rates for the dune domain6) Equilibrium Bay Depth.mat: Array of bay depths for a given combination of rate of sea level rise and external sediment supply7) MarshStrat.mat: Initial marsh stratigraphyMarshStrat.mat: Initial marsh stratigraphy)
Model:FUNWAVE + (There are four input data files to be read … There are four input data files to be read by subroutine init. The first file consists of control parameters and is named funwave2d.data for 2-D programs and funwave1d.data for 1-D programs. With the use of intrinsic function NAMELIST in the program, variable name and its corresponding data can be put together. The logical device number for this file is chosen as 1 and the form of the files is ASCII.The other three input files are water depth data, initial wave field data, and time series of source function amplitude, respectively. Their names are represented by f1n, f2n and f3n which are specified in funwave2d.data or funwave1d.data. Binary format is used for these three files to increase I/O speed for 2-D prograams while ASCII format is used for 1-D programs. Since the record length of data for binary format in SGI computer is different from other machines, a control parameter imch is used in funwave2d.data or funwave1d.data to adjust for different computers.1d.data to adjust for different computers.)
Model:ROMS + (There are hundreds of input parameters for the physical, ecosystem, and sediment models. In addition, there are input scripts for floats, stations, model coupling, and data assimilation.)
Model:ChesROMS + (There are hundreds of input parameters for the physical, ecosystem, and sediment models. In addition, there are input scripts for floats, stations, model coupling, and data assimilation.)
Model:CBOFS2 + (There are hundreds of input parameters for the physical, ecosystem, and sediment models. In addition, there are input scripts for floats, stations, model coupling, and data assimilation.)
Model:UMCESroms + (There are hundreds of input parameters for the physical, ecosystem, and sediment models. In addition, there are input scripts for floats, stations, model coupling, and data assimilation.)
Model:TopoFlow-Channels-Diffusive Wave + (These inputs must be provided as grids: *f … These inputs must be provided as grids:*flow_codes = D8 flow codes (Jenson 1984 convention), (NE,E,SE,S,SW,W,NW,N) → (1,2,4,8,16,32,64,128)*bed_slope = slope of the channel bed or hillslope (m / m)*Manning_n = Manning roughness parameter (s / m^(1/3))*bed_width = bed width for trapezoidal cross-section (m)*bank_angle = bank angle for trapezoid (deg) (from vertical)These inputs can be provided as scalars or grids:*sinuosity = channel sinuosity (m/m) (along-channel / straight length)*init_depth = initial water depth (m) (See HTML help)Grids must be saved in binary files with no header. All variables should be stored as 4-byte, floating-point numbers (IEEE standard) except flow codes, which are unsigned, 1-byte integers.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: 2 Method name: Diffusive_Wave Manning flag: 1 Law of Wall flag: 0 Time step: Scalar 6.00000000 (sec) D8 flow code: Grid Treynor_flow.rtg (none) D8 slope: Grid Treynor_slope.rtg (m/m) Manning N: Grid Treynor_chan-n.rtg (s/m^(1/3)) Bed width: Grid Treynor_chan-w.rtg (m) Bank angle: Grid Treynor_chan-a.rtg (deg) Init. depth: Scalar 0.00000000 (m) Sinuosity: Scalar 1.00000000 (m/m) Save grid timestep: Scalar 60.00000000 (sec) Save Q grids: 1 Case5_2D-Q.rts (m^3/s) Save u grids: 0 Case5_2D-u.rts (m/s) Save d grids: 0 Case5_2D-d.rts (m) Save f grids: 0 Case5_2D-f.rts (none) Save pixels timestep: Scalar 60.00000000 (sec) Save Q pixels: 1 Case5_0D-Q.txt (m^3/s) Save u pixels: 0 Case5_0D-u.txt (m/s) Save d pixels: 0 Case5_0D-d.txt (m) Save f pixels: 0 Case5_0D-f.txt (none) Case5_0D-f.txt (none))
Model:OverlandFlow + (This component operates on a Landlab Raste … This component operates on a Landlab RasterModelGrid instance, and requires that the user has downloaded and installed Landlab. Parameters listed below are required. Ones noted as (optional) will revert to the prescribed default values as described in the documentation. Input parameters include:grid : A Landlab RasterModelGrid, representing the topographyh_init : (optional) Thickness of initial thin layer of water on the surfacealpha : (optional) Time step coeffcient, described in Bates et al., 2010 and de Almeida et al., 2012.mannings_n : (optional) Manning's roughness coefficient.g : (optional) Acceleration due to gravity (m/s^2).theta : (optional) Weighting factor from de Almeida et al., 2012.rainfall_intensity : (optional) Rainfall intensity.ntensity : (optional) Rainfall intensity.)
Model:CMIP + (This data component serves as input climat … This data component serves as input climate data for components in the permafrost toolbox. It requires specification of time period, time step (monthly), and of grid dimensions.To set the grid to a desired region x=25 means 25 degrees east of the international date line y=37 means 37 degrees south of the north pole(30 by 23) means a grid that is "30 degrees E/W by 23 degrees N/S"that is "30 degrees E/W by 23 degrees N/S")
Model:CruAKTemp + (This is a data component that serves as input to a set of components in the permafrost modeling toolkit)
Model:SoilInfiltrationGreenAmpt + (This model expects that the user has downl … This model expects that the user has downloaded and installed the Landlab modeling framework. It operates on a Landlab RasterModelGrid instance. Other input parameters include: hydraulic_conductivity soil_bulk_density rock_density initial_soil_moisture_content soil_type volume_fraction_coarse_fragments coarse_sed_flag surface_water_minimum_depth soil_pore_size_distribution_index soil_bubbling_pressure wetting_front_capillary_pressure_head wetting_front_capillary_pressure_head)
Model:Area-Slope Equation Calculator + (Three input maps at ESRI ASCII format: # Flow Direction (ArcGIS format); # Contributing Area (Flow Accumulation-ArcGIS format); # Slope (ArcGIS format);)
Model:FVCOM + (Tides, Winds, Heat flux, Preccipitation/Evaporation, River discharges, Groundwater, O.B. fluxes)
Model:2DFLOWVEL + (Time (s) and space (m) descretisation step … Time (s) and space (m) descretisation steps, Wind friction coefficient (dimensionless), Chezy Bed friction coefficient (units?), Wind velocity components in x and y (m/s), Coriolis parameter (1/s), Max number of grid points along x direction, Max number of grid points along y direction, Max number of time steps desired, Number of coastal and open boundary nodes, Dependent variables are saved every dat timesteps, Amplitude of the incident long waves (m), Period of the incident long waves (s), Starting node number of the computation field in the jth row, Ending node number of the computation field in the jth row.r of the computation field in the jth row.)
Model:DELTA + (Timestep (sec.), Spacestep (m), Flow velocity at river mouth (m/s), Width and depth of river mouth (m), Bedload dumping rate (m/s), Concentration (gm/m3 of coarse and med silt, Concentration (gm/m3) of fine silt and clay))
Model:WAVEREF + (Timestep (sec.), dm, deltax & deltay, Wave period and max number of apexes)
Model:BatTri + (To generate a grid, the user should input … To generate a grid, the user should input the boundary node information, boundary segment information and hole (or island) information in form of a .poly file, as described in the Triangle manual (http://www.cs.cmu.edu/~quake/triangle.poly.html). These input nodes and segments in the .poly file are forced into the triangulation of the domain. Alternatively (and this is a strong point of BATTRI), all this information can be created from only a bathymetric dataset with the use of the editing options of BATTRI (see Option 0 in Running BATTRI section). This process may require manual deleting of unnecessary segments and nodes, closing of islands by segment adding, addition of an open ocean boundary segment, etc.As a starting point, ordered digital coastline node data can be extracted from the National Geophysical Data Center's webpage (https://www.ngdc.noaa.gov/mgg/shorelines/) at various scales ranging from 1:70,000 to 1:5,000,000. If the coastline is very highly resolved, causing an excessive number of elements along the shoreline, the routine "xy_simplify.m" can be used to reduce the number of nodes to the desired resolution. Remember to format this data into a .poly file, consisting of nodes and segments, before inputting into BATTRI. To refine an already created grid, the user can input the above referenced information either in the form of a previously created .poly file or in the form of NML standard .nod, .ele and .bat files (see next section, Running BATTRI). files (see next section, Running BATTRI).)
Model:TopoFlow + (Too many to list here. Please see the HTML help system and the wiki pages for all of the process components.)

Model:QUAL2K + (Too many to mention here)

Model:MODFLOW + (Too many to mention here, see: http://water.usgs.gov/nrp/gwsoftware/modflow2000/modflow2000.html)
Model:HAMSOM + (Topography 3D temperature and salinity field 2D sea surface height Tidal components River discharge 2D Meteo forcing)
Model:CHILD + (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.)
Model:IceFlow + (Topography, mass balance)
Model:Princeton Ocean Model (POM) + (Topography, temperature, salinity, wind, heat/salt fluxes. Determine by user and application.)
Model:PsHIC + (Two input files, all in ESRI ASCII format: # DEM # Flow direction grid (D8) To change the input files, edit lines 19 for DEM and line 20 for Flow-direction in the source code.)
Model:OrderID + (Two text files are required as input for a … Two text files are required as input for analysis of each vertical succession of strata in the following formats.Vertical thickness and facies succession:<unit thickness (m)> <facies code (integer)><unit thickness (m)> <facies code (integer)>...<unit thickness (m)> <facies code (integer)>EOFe.g. 0.61 90.05 50.52 1...1.21 3Facies codes, colour coding and names:<Facies code 1 (integer)> <red (float)> <green (float)> <blue (float)> <facies name (string)><Facies code 2 (integer)> <red (float)> <green (float)> <blue (float)> <facies name (string)>...<Facies code n (integer)> <red (float)> <green (float)> <blue (float)> <facies name (string)>e.g. 1 0.55 0.32 0 clay2 1 0.65 0 silt3 0.93 0.91 0.8 fineSST4 1 0.95 0.71 medSST5 0.81 0.71 0.23 crsSST; <blue (float)> <facies name (string)> e.g. 1 0.55 0.32 0 clay 2 1 0.65 0 silt 3 0.93 0.91 0.8 fineSST 4 1 0.95 0.71 medSST 5 0.81 0.71 0.23 crsSST)
Model:OptimalCycleID + (Two text files are required as input for a … Two text files are required as input for analysis of each vertical succession of strata in the following formats.Vertical thickness and facies succession: <unit thickness (m)> <facies code (integer)> <unit thickness (m)> <facies code (integer)> ... <unit thickness (m)> <facies code (integer)> EOFe.g. 0.61 9 0.05 5 0.52 1 ... 1.21 3Facies codes, colour coding and names: <Facies code 1 (integer)> <red (float)> <green (float)> <blue (float)> <facies name (string)> <Facies code 2 (integer)> <red (float)> <green (float)> <blue (float)> <facies name (string)> ... <Facies code n (integer)> <red (float)> <green (float)> <blue (float)> <facies name (string)>e.g. 1 0.55 0.32 0 clay 2 1 0.65 0 silt 3 0.93 0.91 0.8 fineSST 4 1 0.95 0.71 medSST 5 0.81 0.71 0.23 crsSSToat)> <blue (float)> <facies name (string)> e.g. 1 0.55 0.32 0 clay 2 1 0.65 0 silt 3 0.93 0.91 0.8 fineSST 4 1 0.95 0.71 medSST 5 0.81 0.71 0.23 crsSST)
Model:OTTER + (Typical inputs of a 1D river profile model (resolution, river length, model time, rock-uplift, erodibility, grain size characteristics))
Model:Frost Model + (USer-specified data on temperature distrib … USer-specified data on temperature distributionsWe present the Frost model with a subsampled version of the CRU-NCEP reanalysis data for the region of Alaska. The geographical extent of this dataset has been reduced to greatly reduce the number of ocean, Aleatian Islands or Canadian pixels. The spatial resolution has been reduced by a factor of 13 in each direction, resulting in an effective pixel resolution of about 10km.The data are monthly average temperatures for each month from January 1901 through December 2009.h from January 1901 through December 2009.)
Model:GIPL + (Upper Boundary (Air temperature) Lower Boundary (Temperature gradient) Initial conditions (Temperature distribution at initial time) Thermo-physical properties)
Model:Permafrost Benchmark System + (Users can upload ILAMB-compatible model outputs and benchmark datasets to the PBS. More information can be found in the PBS documentation, available at https://permamodel.github.io/pbs.)
Model:SUSP + (Various flow properties; sizes, densities and proportions of all grain fractions making up the active layer of the bed)
Model:Cyclopath + (Various text files defining initial conditions and parameter values)
Model:GRLP + (Water discharge inputs, sediment discharge inputs, base-level change, along-channel sources/sinks of sediment, grid of downstream distances)
Model:Detrital Thermochron + (Watershed hypsometry and detrital ages)
Model:OlaFlow + (Wave height, wave period, wave theory, water depth See: waveDict in Reference folder)
Model:LITHFLEX2 + (Width of loading element (m), value for flexural rigidity (Nm), Number of loading events, Number of loading elements for event J (position, height (m) of loading element, density (kg/m3)))
Model:LITHFLEX1 + (Width of loading element (meters), value for flexural rigidity (Nm), number of nodes describing baseline position, number of loading events, number of loading elements for event, number of hidden load elements.)
Model:Point-Tidal-flat + (Wind speed, storm duration, sediment characteristics, tidal currents)
Model:BOM + (Wind, rivers, submerged inlets, lateral open boundaries, surface heat flux, a limited number of numerical schemes can be chosen, ...)
Model:SINUOUS + (X,Y coordinates of centerline, hydrologic and sedimentary parameters, as detailed in the model documentation)
Model:Bing + (Yield/shear strength, viscosity, bulk density, shape of failed material; bathymetry)
Model:Cross Shore Sediment Flux + (You can vary the initial slope, wave periods, wave heights, and sediment fall velocity (a proxy for sediment size).)
Model:GISKnickFinder + (You need a DEM, a watershed outline (shape … You need a DEM, a watershed outline (shapefile), and a point shapefile identifying the top of the streams you are interested in. You also need to input a curvature threshold value and a drainage area threshold value. The curvature threshold is the key to identifying knickpoints (if it is too low you will not see very many knicks, and if it is too high you will identify too many). The drainage area threshold is used to exclude knickpoints that are not in the main channel you are interested in.in the main channel you are interested in.)