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 "Memory requirements" with value "Flexible". 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:SVELA  + (<512Mb)
  • Model:DHSVM  + (> 512Mb RAM)
  • Model:SLAMM 6.7  + (>4GB recommended)
  • Model:Caesar  + (>512MB)
  • Model:AlluvStrat  + (?)
  • Model:Symphonie  + (A few Gb)
  • Model:DLBRM  + (All memory is dynamically sized on the basis of the number of cells in the watershed, so memory requirements are scaled with the size of the watershed.)
  • Model:CAESAR Lisflood  + (Contingent on simulation size (area))
  • Model:Topography Data Component  + (Data are downloaded directly to a file, so memory use is minimal. Optionally, the data can be loaded into a Python session, in which case, memory use scales with the size of the data.)
  • Model:MARM5D  + (Depend on landscape size and resolution.)
  • Model:HexWatershed  + (Depend on study domain and spatial resolution)
  • Model:GEOtop  + (Dependent on DEM size)
  • Model:Non Local Means Filtering  + (Dependent on DEM size)
  • Model:Hilltop and hillslope morphology extraction  + (Dependent on DEM size)
  • Model:Drainage Density  + (Dependent on size/resolution of model grid)
  • Model:TUGS  + (Depending on node,number of sizes and number of layers information has to be stored)
  • Model:ROMS  + (Depends on application but it is relativelDepends on application but it is relatively small in distributed-memory since only the tile partition is allocated for global and local arrays. All the state model variables are dynamically allocated and passed as arguments to the computational routines via de-referenced pointer structures.ines via de-referenced pointer structures.)
  • Model:CBOFS2  + (Depends on application but it is relativelDepends on application but it is relatively small in distributed-memory since only the tile partition is allocated for global and local arrays. All the state model variables are dynamically allocated and passed as arguments to the computational routines via de-referenced pointer structures.ines via de-referenced pointer structures.)
  • Model:UMCESroms  + (Depends on application but it is relativelDepends on application but it is relatively small in distributed-memory since only the tile partition is allocated for global and local arrays. All the state model variables are dynamically allocated and passed as arguments to the computational routines via de-referenced pointer structures.ines via de-referenced pointer structures.)
  • Model:GSSHA  + (Depends on catchment)
  • Model:TauDEM  + (Depends on data)
  • Model:OrderID  + (Depends on dataset being analysed, but should be small, perhaps a few megabytes)
  • Model:WOFOST  + (Depends on implementation: 20 Mb (Fortran) to 150 Mb (python))
  • Model:Chi analysis tools  + (Depends on the size of your DEM)
  • Model:SINUOUS  + (Depends upon size of simulated domain)