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 "Too many to mention here". Since there have been only a few results, also nearby values are displayed.

Showing below up to 11 results starting with #1.

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

    

List of results

  • 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.</br></br>To set the grid to a desired region</br> x=25 means 25 degrees east of the international date line</br> y=37 means 37 degrees south of the north pole</br></br>(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. </br></br>Other input parameters include: </br> hydraulic_conductivity</br> soil_bulk_density</br> rock_density</br> initial_soil_moisture_content</br> soil_type</br> volume_fraction_coarse_fragments</br> coarse_sed_flag</br> surface_water_minimum_depth</br> soil_pore_size_distribution_index</br> soil_bubbling_pressure</br> 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.</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: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.</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 a … Two 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 distrib … USer-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.)
Retrieved from "https://csdms.colorado.edu/wiki/Special:SearchByProperty/:Describe-20input-20parameters-20model/Too-20many-20to-20mention-20here"