Search by property

From CSDMS

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.

Search by property

A list of all pages that have property "Describe input parameters model" with value "Wind speed, storm duration, sediment characteristics, tidal currents". Since there have been only a few results, also nearby values are displayed.

Showing below up to 26 results starting with #1.

View (previous 50 | next 50) (20 | 50 | 100 | 250 | 500)


    

List of results

  • Model:2DFLOWVEL  + (Time (s) and space (m) descretisation stepTime (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.</br>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 aTwo text files are required as input for analysis of each vertical succession of strata in the following formats.</br></br>Vertical thickness and facies succession:</br><unit thickness (m)> <facies code (integer)></br><unit thickness (m)> <facies code (integer)></br>...</br><unit thickness (m)> <facies code (integer)></br>EOF</br></br>e.g. </br>0.61 9</br>0.05 5</br>0.52 1</br>...</br>1.21 3</br></br>Facies codes, colour coding and names:</br><Facies code 1 (integer)> <red (float)> <green (float)> <blue (float)> <facies name (string)></br><Facies code 2 (integer)> <red (float)> <green (float)> <blue (float)> <facies name (string)></br>...</br><Facies code n (integer)> <red (float)> <green (float)> <blue (float)> <facies name (string)></br></br>e.g. </br>1 0.55 0.32 0 clay</br>2 1 0.65 0 silt</br>3 0.93 0.91 0.8 fineSST</br>4 1 0.95 0.71 medSST</br>5 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 aTwo text files are required as input for analysis of each vertical succession of strata in the following formats.</br></br>Vertical thickness and facies succession: <unit thickness (m)> <facies code (integer)> <unit thickness (m)> <facies code (integer)> ... <unit thickness (m)> <facies code (integer)> EOF</br></br>e.g. 0.61 9 0.05 5 0.52 1 ... 1.21 3</br></br>Facies 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)></br></br>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 distribUSer-specified data on temperature distributions</br></br>We 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.</br></br>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: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 (shapeYou 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.)
  • Model:SedFoam-2.0  + (alpha,Ua, Ub, p, Theta, k, epsilon, omega)
  • Model:Meanderpy  + (channel width (m), channel depth (m), paddchannel width (m), channel depth (m), padding (number of nodepoints along centerline), sampling distance along centerline, number of iterations, dimensionless Chezy friction factor, threshold distance at which cutoffs occur, migration rate constant (m/s), vertical slope-dependent erosion rate constant (m/s), time step (s), density of water (kg/m3), which time steps will be saved, approximate number of bends you want to model, initial slope (setting this to non-zero results in instabilities in long runs)ero results in instabilities in long runs))
  • Model:River Temperature Model  + (climatology)
  • Model:CrevasseFlow  + (daily water discharge series;daily sedimendaily water discharge series;daily sediment flux series;</br>averaged channel cross-sectional depth, averaged channel cross-sectional width;</br>floodplain width;</br>manning coefficients of the channel and floodplain;</br>longitudinal channel slope;</br>Channel bed's super-elevation above the floodplain where sedimentation rate is close to 0;</br>M-coefficient for erosion rate for the bottom of crevasse splay;</br>M-coefficient for erosion rate for the two side slopes of crevasse splay; </br>critical velocity for erosion; </br>critical velocity for deposition;</br>width of dike at the root; </br>cross valley slope;</br>settling velocity of suspended load in the channel.velocity of suspended load in the channel.)
  • Model:WBM-WTM  + (depending on configuration, the model can depending on configuration, the model can be run with Air temperature and Precipitation only. In the most complex configuration, the model will also need vapor pressure, solar radiation, wind, daily minimum and maximum temperature. Built-in functions allow trading input variables (e.g. use cloud cover instead of solar radiation).e cloud cover instead of solar radiation).)
  • Model:WBMsed  + (depending on configuration, the model can depending on configuration, the model can be run with Air temperature and Precipitation only. In the most complex configuration, the model will also need vapor pressure, solar radiation, wind, daily minimum and maximum temperature. Built-in functions allow trading input variables (e.g. use cloud cover instead of solar radiation).e cloud cover instead of solar radiation).)
  • Model:TUGS  + (describe input parameters: Initial longitudescribe input parameters: Initial longitudinal profile and estimated surface/subsurface grain size; sediment input, including both rate and grain size distribution, and typically at a long-term-avearged basis; and water discharge, typically daily average discharge.charge, typically daily average discharge.)
  • Model:Mocsy  + (dissolved inorganic carbon (DIC), total alkalinity (Alk), temperature, and salinity as well as concentrations of total dissolved inorganic phosphorus and silicon concentrations.)
  • Model:FlowDirectorMFD  + (elev : array_like<br> Elevations at elev : array_like<br></br>Elevations at nodes.</br></br>neighbors_at_node : array_like (num nodes, max neighbors at node)<br></br>For each node, the link IDs of active links.</br> </br>links_at_node : array_like (num nodes, max neighbors at node)<br></br> </br>link_dir_at_node: array_like (num nodes, max neighbors at node)<br></br>IDs of the head node for each link.</br> </br>link_slope : array_like<br></br>slope of each link, defined POSITIVE DOWNHILL (i.e., a negative value means the link runs uphill from the fromnode to the tonode).</br> </br>baselevel_nodes : array_like, optional<br></br>IDs of open boundary (baselevel) nodes.</br> </br>partition_method: string, optional<br></br>Method for partitioning flow. Options include 'slope' (default) and 'square_root_of_slope'.for partitioning flow. Options include 'slope' (default) and 'square_root_of_slope'.)
  • Model:Tracer dispersion calculator  + (equilibrium bed profile, sediment size, probabilities of instantaneous bed elevations and of particle entrainment, area of the patch of tracers installed on the bed, entrainment rate of particles in bedload tranport, particle step lenght)
  • Model:TwoPhaseEulerSedFoam  + (flow forcing; sediment properties ( densitflow forcing; sediment properties ( density, grain size, etc.); fluid properties; coefficients for carrier fluid turbulence, and parameters for kinetic theory for granular flow; model selection for kinetic theory, such as granular pressure, conductivity, and viscosity model, etc. More details are described in the user maunal. details are described in the user maunal.)
  • Model:FractureGridGenerator  + (frac_spacing : int, optional<br> Average spacing of fractures (in grid cells) (default = 10) seed : int, optional<br> Seed used for random number generator (default = 0))
  • Model:TreeThrow  + (fraction of trees that move sediment when they die, # of plots to simulate, # of years to simulate, with or without growth of Chestnut.)
  • Model:ISSM  + (geometry of ice sheets, ice shelves, land-ice, ocean boundaries; material parameters; climate forcings (i.e surface mass balance); basal friction at the ice/bed interface; flightlines; errors; boundaries; grids; preview images)
  • Model:HackCalculator  + (grid : Landlab Model Grid instance, required<br><br> save_full_df: bool<br> Flag indicating whether to create the ``full_hack_dataframe``.<br> **kwds :<br> Values to pass to the ChannelProfiler.)
  • Model:ChannelProfiler  + (grid : Landlab Model Grid instance, requirgrid : Landlab Model Grid instance, required<br><br></br></br>channel_definition_field : field name as string<br></br>Name of field used to identify the outlet and headwater nodes of the channel network. Default is "drainage_area".</br></br>minimum_outlet_threshold : float, optional<br></br>Minimum value of the *channel_definition_field* to define a watershed outlet. Default is 0.</br></br>minimum_channel_threshold : float, optional<br></br>Value to use for the minimum drainage area associated with a plotted channel segment. Default values 0.</br></br>number_of_watersheds : int, optional<br></br>Total number of watersheds to plot. Default value is 1. If value is greater than 1 and outlet_nodes is not specified, then the number_of_watersheds largest watersheds is based on the drainage area at the model grid boundary. If given as None, then all grid cells on the domain boundary with a stopping field (typically drainage area) greater than the minimum_outlet_threshold in area are used.</br></br>main_channel_only : Boolean, optional<br></br>Flag to determine if only the main channel should be plotted, or if all stream segments with drainage area less than threshold should be plotted. Default value is True.</br></br>outlet_nodes : length number_of_watersheds iterable, optional<br></br>Length number_of_watersheds iterable containing the node IDs of nodes to start the channel profiles from. If not provided, the default is the number_of_watersheds node IDs on the model grid boundary with the largest terminal drainage area.</br></br>cmap : str<br></br>A valid matplotlib cmap string. Default is "viridis".minal drainage area. cmap : str<br> A valid matplotlib cmap string. Default is "viridis".)
  • Model:Lithology  + (grid : Landlab ModelGrid<br> thickngrid : Landlab ModelGrid<br></br></br>thicknesses : ndarray of shape `(n_layers, )` or `(n_layers, n_nodes)`<br></br>Values of layer thicknesses from surface to depth. </br>Layers do not have to have constant thickness. </br>Layer thickness can be zero, though the entirety of Lithology must have non-zero thickness.</br></br>ids : ndarray of shape `(n_layers, )` or `(n_layers, n_nodes)`<br></br>Values of rock type IDs corresponding to each layer specified in **thicknesses**. </br>A single layer may have multiple rock types if specified by the user</br></br>attrs : dict<br></br>Rock type property dictionary. </br>See class docstring for example of required format.</br></br>layer_type : str, optional<br></br>Type of Landlab layers object used to store the layers. </br>If MaterialLayers (default) is specified, then erosion removes material and does not create a layer of thickness zero. </br>If EventLayers is used, then erosion removes material and creates layers of thickness zero. </br>Thus, EventLayers may be appropriate if the user is interested in chronostratigraphy.</br></br>dz_advection : float, `(n_nodes, )` shape array, or at-node field array optional<br></br>Change in rock elevation due to advection by some external process.</br>This can be changed using the property setter. </br>Dimensions are in length, not length per time.</br></br>rock_id : value or `(n_nodes, )` shape array, optional<br></br>Rock type id for new material if deposited.</br>This can be changed using the property setter.ype id for new material if deposited. This can be changed using the property setter.)
  • Model:SpeciesEvolver  + (grid : ModelGrid<br> A Landlab ModelGrid. initial_time : float, int, optional<br> The initial time. The unit of time is not considered within the component, with the exception that time is logged in the record. The default value of this parameter is 0.)
  • Model:PrecipitationDistribution  + (grid : ModelGrid<br> A Landlab grid grid : ModelGrid<br></br>A Landlab grid (optional). If provided, storm intensities will be stored as a grid scalar field as the component simulates storms.</br></br>mean_storm_duration : float<br></br>Average duration of a precipitation event.</br></br>mean_interstorm_duration : float<br></br>Average duration between precipitation events.</br></br>mean_storm_depth : float<br></br>Average depth of precipitation events.</br></br>total_t : float, optional<br></br>If generating a time series, the total amount of time.</br></br>delta_t : float or None, optional<br></br>If you want to break up storms into determined subsections using yield_storm_interstorm_duration_intensity, a delta_t is needed.</br></br>random_seed : int or float, optional<br></br>Seed value for random-number generator.ndom_seed : int or float, optional<br> Seed value for random-number generator.)
  • Model:LakeMapperBarnes  + (grid : ModelGrid<br> A Landlab grid.grid : ModelGrid<br></br>A Landlab grid.</br> </br>surface : field name at node or array of length node<br></br>The surface to direct flow across.</br> </br>method : {'Steepest', 'D8'}<br></br>Whether or not to recognise diagonals as valid flow paths, if a raster. Otherwise, no effect.</br> </br>fill_flat : bool<br></br>If True, pits will be filled to perfectly horizontal. </br>If False, the new surface will be slightly inclined to give steepest descent flow paths to the outlet.</br> </br>fill_surface : bool<br></br>Sets the field or array to fill. </br>If fill_surface is surface, this operation occurs in place, and is faster.</br>Note that the component will overwrite fill_surface if it exists; to supply an existing water level to it, supply that water level field as surface, not fill_surface.</br> </br>redirect_flow_steepest_descent : bool<br></br>If True, the component outputs modified versions of the 'flow__receiver_node', 'flow__link_to_receiver_node', 'flow__sink_flag', and 'topographic__steepest_slope' fields. </br>These are the fields output by the FlowDirector components, so set to True if you wish to pass this LakeFiller to the FlowAccumulator, or if you wish to work directly with the new, correct flow directions and slopes without rerunning these components on your new surface.</br>Ensure the necessary fields already exist, and have already been calculated by a FlowDirector! </br>This also means you need to instantiate your FlowDirector **before** you instantiate the LakeMapperBarnes.</br>Note that the new topographic__steepest_slope will always be set to zero, even if fill_flat=False (i.e., there is actually a miniscule gradient on the new topography, which gets ignored).</br> </br>reaccumulate_flow : bool<br></br>If True, and redirect_flow_steepest_descent is True, the run method will (re-)accumulate the flow after redirecting the flow. </br>This means the 'drainage_area', 'surface_water__discharge', 'flow__upstream_node_order', and the other various flow accumulation fields (see output field names) will now reflect the new drainage patterns without having to manually reaccumulate the discharge. </br>If True but redirect_flow_steepest_descent is False, raises an ValueError.</br> </br>ignore_overfill : bool<br></br>If True, suppresses the Error that would normally be raised during creation of a gentle incline on a fill surface (i.e., if not fill_flat). </br>Typically this would happen on a synthetic DEM where more than one outlet is possible at the same elevation. </br>If True, the was_there_overfill property can still be used to see if this has occurred.</br> </br>track_lakes : bool<br></br>If True, the component permits a slight hit to performance in order to explicitly track which nodes have been filled, and to enable queries on that data in retrospect. </br>Set to False to simply fill the surface and be done with it.ueries on that data in retrospect. Set to False to simply fill the surface and be done with it.)