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:Oceananigans.jl  + (--)
• Model:Coastal Landscape Transect Model (CoLT)  + (1 year time steps, good results up to 200-300 years)
• Model:Detrital Thermochron  + (1. Sediment transport time through a catchment 2. Exhumation time from a depth of a thermochronometric closure isotherm to the surface)
• Model:Avulsion  + (100s of years)
• Model:IceFlow  + (2D grid, variable dx and dy possible)
• Model:Spbgc  + (A parameter called the CFL number controls … A parameter called the CFL number controls the time step in relation to the spatial scales. For boussinesq simulations, a CFL number of 0.2 is usually sufficient for code stability. However, for the non-boussinesq simulations, I usually have to lower the CFL number to around 0.05. It's really just a bit of trial and error though.ally just a bit of trial and error though.)
• Model:Inflow  + (A single river flood event.)
• Model:Sakura  + (A single river flood event.)
• Model:TAo  + (About 1kyr for surface processes; 200kyr for tectonic/ isostatic processes.)
• Model:TreeThrow  + (Annual time step, usually simulate ~1000 years.)
• Model:CSt ASMITA  + (Averaging time is on the order of annual averages so that individual storm events are not represented. Problems usually are scaled for years, to decades all the way up to millenia.)
• Model:Princeton Ocean Model (POM)  + (CFL condition)
• Model:Symphonie  + (CFL criterium)
• Model:RASCAL  + (Code has been most commonly run at 1 year … Code has been most commonly run at 1 year time steps for up to 6000 years. Time steps are constrained by rates of evolution of topography due to episodic sediment transport events and peat accretion and how quickly those processes affect the flow field. In the situation for which the model was developed, sediment accumulates at a mean rate of 1 mm/yr.ent accumulates at a mean rate of 1 mm/yr.)
• Model:GEOMBEST-Plus  + (Constraints: * Time step - 1 - 50 years * Duration - Hundreds to thousands of years)
• Model:GFlex  + (Currently does not time-evolve. I would like to couple this to a 3D viscoelastic mantle at some point, but this hasn't happened yet.)
• Model:Marsh column model  + (Daily timestep.)
• Model:River Temperature Model  + (Daily timesteps)
• Model:HBV  + (Daily timesteps)
• Model:Plume  + (Daily; Steady-state)
• Model:CruAKTemp  + (Data coverage 1901-2009 monthly temperature in degree Celcius.)
• Model:CMIP  + (Data covers 1901 to 2100. It is processed from the original data to comprise a monthly timescale.)
• Model:Sedflux  + (Days or greater. Component processes can have much higher resolutions for numerical stability.)
• Model:FVshock  + (Days/months. When running for more then few month the simulation time is very large.)
• Model:Demeter  + (Decades to centuries)

• Model:RivMAP  + (Dependent on resolution and extent of input imagery)

• Model:GSSHA  + (Dependent upon computational power and memory.)
• Model:Landlab  + (Depends on application/process)
• Model:ParFlow  + (Depends upon application.)
• Model:GOLEM  + (Designed for time scales over which topography changes appreciably, which might be years for badlands, up to thousands or millions of years for other landscapes.)
• Model:AquaTellUs  + (Developed as a stratigraphic model, approach is event-based. Intended time scale ranges from several decades to Holocene (10-10.000yrs).)
• Model:TopoFlow  + (Each process can have its own timestep. Typical timesteps are: *Channel flow (seconds) *Infiltration (seconds to minutes) *Snowmelt (hours to days) *Subsurface flow (hours to days), etc. Model can be run for a full year or longer, if necessary.)
• Model:CASCADE  + (Evolution of Myrs, due to the model parameterization used (no human-scale proceses))
• Model:Bing  + (For stability, time step is typically fractions of a second)
• Model:TUGS  + (For typical application in a natural river as a prediction tool, the recommended resolution is annual, although it can be as high as hours for simulation of a specific known event.)
• Model:GPM  + (From seconds to about 100,000 years.)
• Model:GENESIS  + (GENESIS is a long-term shoreline evolution model and is best applied to estimate shoreline change over time periods of 1 year to 10's of years.)
• Model:MarshMorpho2D  + (Generally runs with very large time steps (1 year) Cannot resolve intra-tidal processes (i.e., ebb-flood variability))
• Model:NearCoM  + (Hours to months.)
• Model:ROMS  + (Hours, days, seasons. It also can be used for climate research (decades).)
• Model:ChesROMS  + (Hours, days, seasons. It also can be used for climate research (decades).)
• Model:CBOFS2  + (Hours, days, seasons. It also can be used for climate research (decades).)
• Model:UMCESroms  + (Hours, days, seasons. It also can be used for climate research (decades).)
• Model:CAM-CARMA  + (I am running the model with dynamical time steps of 1800 seconds, but it only computes the radiative transfer every 200 timesteps.)
• Model:Cyclopath  + (Internal time step years to decades Model chron resolution 1000 years Total run time 1-10 My)
• Model:AnugaSed  + (Internal timestep is determined by ANUGA for numerical stability (in seconds). Output timestep is set by the user. Simulations are realistically limited to a few model hours.)
• Model:Morphodynamic gravel bed  + (It is applied for 90 years. The time step is ~0.7 days.)
• Model:GullyErosionProfiler1D  + (It is typically run for times no less than 25 years and no greater than 700 years.)
• Model:WBMsed  + (It simulate at daily time-steps. Maximum available datasets time-span is between 1901-present.)
• Model:River Network Bed-Material Sediment  + (Limited by computational resources.)
• Model:Nitrate Network Model  + (Limited by computational resources.)