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 output parameters model" with value "Solute concentrations as a function of space and time". 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:SPARROW  + (SPARROW is designed to describe the spatiaSPARROW is designed to describe the spatial patterns in water quality and the factors that affect it. SPARROW models are developed using mass balance constraints to quantify the relation between stream constituent load (the mass of the constituent being transported by the stream) and the sources and losses of mass in watersheds. Thus the models are inherently designed to predict load (mass per time) for all stream reaches in the modeling region. However, the predictions of stream load can be modified to provide a variety of water-quality metrics that can support various types of assessments.</br></br>The SPARROW prediction metrics include constituent yields, concentrations, and source contributions to stream loads: </br>*Constituent yields</br>*Constituent concentrations</br>*Source contributions to stream loadsions *Source contributions to stream loads)
  • Model:SWAN  + (SWAN can provide output on uniform, recti-SWAN can provide output on uniform, recti-linear spatial grids that are independent from the input grids and from the computational grid. In the computation with a curvi-linear computational grid, curvi-linear output grids are available in SWAN. This also holds for triangular meshes. An output grid has to be specified by the user with an arbitrary resolution, but it is of course wise to choose a resolution that is fine enough to show relevant spatial details. It must be pointed out that the information on an output grid is obtained from the computational grid by bi-linear interpolation (output always at computational time level). This implies that some inaccuracies are introduced by this interpolation. It also implies that bottom or current information on an output plot has been obtained by interpolating twice: once from the input grid to the computational grid and once from the computational grid to the output grid. If the input-, computational- and output grids are identical, then no interpolation errors occur.</br></br></br>In the regions where the output grid does not cover the computational grid, SWAN assumes output values equal to the corresponding exception value. For example, the default exception value for the significant wave height is -9. The exception values of output quantities can be changed by means of the QUANTITY command.</br></br></br>In nonstationary computations, output can be requested at regular intervals starting at a given time always at computational times. given time always at computational times.)
  • Model:Sedflux  + (Sediment properties that include (but are Sediment properties that include (but are not limited to) bulk density, grain size, porosity, and permeability. These are averaged over are user-specified vertical resolution (typically mm to cm).</br></br>Sea-floor properties that include slope, water depth, and sand fraction.ude slope, water depth, and sand fraction.)
  • Model:SRH-1D  + (Sediment transport rates, cross section geometry, bed material, flow and sediment output)
  • Model:NearCoM  + (See documentation.)
  • Model:GeoTiff Data Component  + (See documentation: https://bmi-geotiff.readthedocs.io)
  • Model:Topography Data Component  + (See documentation: https://bmi-topography.readthedocs.io)
  • Model:WAVEWATCH III Data Component  + (See documentation: https://bmi-wavewatch3.readthedocs.io)
  • Model:GridMET Data Component  + (See documentation: https://pymt-gridmet.readthedocs.io)
  • Model:Hilltop and hillslope morphology extraction  + (See included readme)
  • Model:FUNWAVE  + (See manual, that is uploaded.)
  • Model:Glimmer-CISM  + (See paper)
  • Model:Nitrate Network Model  + (See results of related publication by J. A. Czuba.)
  • Model:River Network Bed-Material Sediment  + (See results of related publications by J. A. Czuba.)
  • Model:RiverMUSE  + (See the readme file.)
  • Model:OpenFOAM  + (See user manual)
  • Model:ADCIRC  + (See: (http://adcirc.org) *Screen Output (See: (http://adcirc.org) </br>*Screen Output (fort.6)</br>* General Diagnostic Output (fort.16)</br>* Iterative Solver ITPACKV 2D Diagnostic Output (fort.33)</br>* 3D Density, Temperature and/or Salinity at Specified Recording Stations (fort.41)</br>* 3D Velocity at Specified Recording Stations (fort.42)</br>* 3D Turbulence at Specified Recording Stations (fort.43)</br>* 3D Density, Temperature and/or Salinity at All Nodes in the Model Grid (fort.44)</br>* 3D Velocity at All Nodes in the Model Grid (fort.45)</br>* 3D Turbulence at All Nodes in the Model Grid (fort.46)</br>* Elevation Harmonic Constituents at Specified Elevation Recording Stations (fort.51)</br>* Depth-averaged Velocity Harmonic Constituents at Specified Velocity Recording Stations (fort.52)</br>* Elevation Harmonic Constituents at All Nodes in the Model Grid (fort.53)</br>* Depth-averaged Velocity Harmonic Constituents at All Nodes in the Model Grid (fort.54)</br>* Harmonic Constituent Diagnostic Output (fort.55)</br>* Elevation Time Series at Specified Elevation Recording Stations (fort.61)</br>* Depth-averaged Velocity Time Series at Specified Velocity Recording Stations (fort.62)</br>* Elevation Time Series at All Nodes in the Model Grid (fort.63)</br>* Depth-averaged Velocity Time Series at All Nodes in the Model Grid (fort.64)</br>* Hot Start Output (fort.67, fort.68)</br>* Atmospheric Pressure Time Series at Specified Meteorological Recording Stations (fort.71)</br>* Wind Velocity Time Series at Specified Meteorological Recording Stations (fort.72)</br>* Atmospheric Pressure Time Series at All Nodes in the Model Grid (fort.73)</br>* Wind Stress or Velocity Time Series at All Nodes in the Model Grid (fort.74)</br>* Depth-averaged Scalar Concentration Time Series at Specified Concentration Recording Stations (fort.81)</br>* Depth-averaged Scalar Concentration Time Series at All Nodes in the Model Grid (fort.83)</br>* Depth-averaged Density Fields at Specified Recording Stations (fort.91)</br>* Depth-averaged Density Fields at All Nodes in the Model Grid (fort.93)s at All Nodes in the Model Grid (fort.93))
  • Model:SWAT  + (See: https://swat.tamu.edu/)
  • Model:STWAVE  + (Selected Wave Spectra Selected Wave Parameters Wave Parameter Fields Breaker Index Fields Radiation Stress Gradient Fields)
  • Model:PIHMgis  + (Several state variables (soil moisture, groundwater table, stream head, interception, surface state and snow depth) and fluxes (3 components of evapotranspiration) 10 stream component fluxes for each reach, infiltration, recharge, lateral flux))
  • Model:Quad  + (Shoreline and alluvial-bedrock transition trajectories over time. Future versions of the model will include the profile evolution.)
  • Model:GENESIS  + (Shoreline position, breaking wave information, estimated longshore sand transport rates.)
  • Model:Bedrock Fault Scarp  + (Simple ascii files containing x and z coordinates of points at end of run. Optional output of figure in .eps format.)
  • Model:UEB  + (Snow melt)
  • Model:SNOWPACK  + (Snowpack creates various output files: * tSnowpack creates various output files:</br>* the current state of its soil and snow layers in ".sno" files;</br>* the current state of its hazard relevant data in ".haz" files;</br>* a time serie of snow profiles;</br>* a time serie of the meteorological data and fluxes as used in the model.ical data and fluxes as used in the model.)
  • Model:OTEQ  + (Solute concentrations as a function of space and time)
  • Model:WEPP  + (Storm, monthly, yearly, or average annual Storm, monthly, yearly, or average annual runoff, soil loss, and sediment yield from a hillslope profile. Spatial distribution of soil erosion and deposition on slope profiles. Graphical output available of 92 parameters from continuous model simulations (including precip, temperatures, runoff, soil loss, sediment yield, biomass production, residue cover, etc.). Soil output text file, water balance output text file, plant output text file, storm event output file, overland flow element summary line output file.and flow element summary line output file.)
  • Model:GIPL  + (Temperature distribution with depth Active Layer Depth Freezing/Thawing day)
  • Model:LONGPRO  + (Temporally evolving longitudinal profile and cross-sectional average flows of a 1D river)
  • Model:OverlandFlow  + (The Landlab OverlandFlow component outputsThe Landlab OverlandFlow component outputs data as Landlab fields - numpy arrays containing data with the associated CSDMS standard name, listed below:</br></br>'surface_water__depth' : NumPy array of length nnodes. Water depths at a given time step.</br>'surface_water__discharge' : NumPy array of length nlinks. Water discharge values at a given time step.</br>'water_surface__gradient' : NumPy array of length nlinks. Water surface gradient at a given time step.ter surface gradient at a given time step.)
  • Model:Permafrost Benchmark System  + (The PBS wraps ILAMB, which produces tabular and graphical statistics from a benchmark analysis. These outputs can be viewed in ILAMB, or downloaded to a user's local machine as a tarball.)
  • Model:WBMsed  + (The WBMplus model can output any variables used for the water balance and transport calculations. WBMsed unique output are: sediment-flux, over-bank water discharge, and all the BQART parameters.)
  • Model:SWEHR  + (The code outputs the following text files:The code outputs the following text files:</br>“topoout.txt” – elevation for each grid point at the end of the simulation</br>“depth.txt” – flow depth at each grid point at the end of the simulation</br>“uh.txt” – value of conserved variable UH at each grid point</br>“vh.txt” – value of conserved variable VH at each grid point</br>“ch.txt” – value of conserved variable CH at each grid point</br>“m.txt” – mass of sediment in the deposited layer at each grid point</br>“c.txt” – sediment concentration at each grid point</br>“vel.txt” – flow velocity at each grid point</br>“stage.txt” – time series data (time (s), flow depth, flow velocity, and sediment concentration) at the outlet pixel</br>“maxvel.txt” – maximum flow velocity recorded at each grid point throughout the simulation</br>“maxdepth.txt” -- maximum flow depth recorded at each grid point throughout the simulation</br>“saveflow.txt” – time series data (flow depth, flow velocity, sediment concentration) at user specified grid points</br>“topomovie.txt” – elevation data at different times throughout the simulation (specified in the code by “printinterval”)</br>“depthmovie.txt” – flow depth at different times throughout the simulation</br>“velocitymovie.txt” – flow velocity at different times throughout the simulation</br>“cmovie.txt” – sediment concentration at different times throughout the simulation</br>“Mmovie.txt” – mass of sediment in the deposited layer at different times throughout the simulation different times throughout the simulation)
  • Model:CMIP  + (The component provides monthly temperature data in degrees Celcius. Within the CSDMS framework, the component generates an NetCDF file of a stacked grid of monthly temperatures over the specified region.)
  • Model:DR3M  + (The computed outflow from any flow plane, The computed outflow from any flow plane, pipe, or channel segment for each storm period may be written to the output file or to the WDM file. A summary of the measured and simulated rainfall, runoff, and peak flows is written to the output file. A flat file containing the storm rainfall, measured flow (if available), and simulated flow at user selected sites can be generated. A flat file for each storm containing the total rainfall, the measured peak flow (if available), and the simulated peak flow for user-selected sites can be generated. for user-selected sites can be generated.)
  • Model:CruAKTemp  + (The data component provides monthly temperature as a NetCDF file for the region of Alaska)
  • Model:WRF-Hydro  + (The following output files are available tThe following output files are available to the user, depending on their run configuration:</br>1. Land surface model output</br>2. Land surface diagnostic output</br>3. Streamflow output at all channel reaches/cells</br>4. Streamflow output at forecast points or gage reaches/cells</br>5. Streamflow on the 2D high resolution routing grid (gridded channel routing only)</br>6. Terrain routing variables on the 2D high resolution routing grid</br>7. Lake output variables</br>8. Ground water output variables</br>9. A text file of streamflow output at either forecast points or gage locations</br>For a detailed table of each variable</br>contained within each output file, see the WRF-Hydro Output Variable Matrix V5 located on our website</br>https://ral.ucar.edu/projects/wrf_hydro/technical-description-user-guidewrf_hydro/technical-description-user-guide)
  • Model:1D Particle-Based Hillslope Evolution Model  + (The model can be customized to produce manThe model can be customized to produce many different kinds of output but, typically, the output consists of (i) h, a final hillslope profile; (ii) h_diffs, a vector which summarizes how the profile changed over the duration of the simulation; and (iii) a vector expressing the fluxes of particles through a site along the hillslope.</br></br>However, the same code can be used to produce a video of the hillslope evolution, a vector containing the absolute difference between the hillslope profile and a reference profile, and many other observables of interest.e, and many other observables of interest.)
  • Model:WBM-WTM  + (The model can output any variables used for the water balance and transport calculations. The most frequently requested ones are: potential and actual evapotranspiration, soil moisture, groundwater storage, river discharge, irrigational water uptake.)
  • Model:PyDeCe  + (The model generates several georeferenced The model generates several georeferenced tiff files upon completion. These geotiff files can be viewed using any GIS software. Each file is a 2D map of a modeled flow property such as thickness, velocity etc. Additionally, multiband geotiff files containing similar 2D maps at multiple user-defined time intervals during the simulation.</br></br>Depth – Map of the final 2D flow thickness (in meters).</br></br>Depthbin – Binary map where cells with thickness > user-defined threshold thickness have a value of 1 and the rest of the cells have a value of 0.</br></br>MaxDepth – Map of the maximum flow depth obtained at each cell during the entire simulation (in meters).</br></br>MaxVelocity – Map of the maximum velocity obtained at each cell during the entire simulation (in m/s).</br></br>MomentumX – Map of final 2D flow momentum along the X direction (in sq. m/s).</br></br>MomentumY – Map of final 2D flow momentum along the Y direction (in sq. m/s).</br></br>Velocity – Map of the final 2D flow velocity (in m/s).</br></br>VelocityX – Map of the final 2D flow velocity along the X direction (in m/s).</br></br>VelocityY – Map of the final 2D flow velocity along the Y direction (in m/s).</br></br></br>The multiband (movie) files output by the model are DepthMovie, MomentumXMovie, MomentumYMovie, VelocityMovie, VelocityXMovie, VelocityYMovie.elocityMovie, VelocityXMovie, VelocityYMovie.)
  • Model:Shoreline  + (The new coastline at the end of the simulation is plotted. Results are not currently saved to files.)
  • Model:Reservoir  + (The no-fail storage capacity and corresponding storage behaviour time series.)
  • Model:GullyErosionProfiler1D  + (The output are elevation values that represent the gully channel profile.)
  • Model:LTRANS  + (The output can ultimately be used to plot The output can ultimately be used to plot and view the particles and compare the</br>outcomes of different model runs. There are two types of comma-delimited output files: para</br>and endfile. The para files are created periodically at set intervals throughout the running of the</br>program and contain the particle locations at the current time. The endfile file is created only at</br>the end of the program and contains information regarding each particles’ start location, end</br>location, and ending status.location, end location, and ending status.)
  • Model:Hilltop flow routing  + (The output data is both plain text data files and .flt raster files containing the spatial location of the computed results.)
  • Model:CEM  + (The output of the model consists of snapshThe output of the model consists of snapshots of the coastline during its evolution. The model can be configured to write the resulting coastline at any point during the simulation. The output format of the coastline file is a custom binary formatted-file (the same format as the initial model input). Also, for convenience using with other software tools such as MATLAB, an ASCII-based file of the coastline shape can be written too. The model can also directly generate JPEG-formatted pictures of the coastline shape at any time during the simulation.e shape at any time during the simulation.)
  • Model:Chi analysis tools  + (The outputs are i) For chi_m_over_n_analysThe outputs are</br>i) For chi_m_over_n_analysis.exe, a *.movern file that contains information about the goodness of fit of channel profiles to a series of linear segments as a function of the m/n ratio: this file is used to determine the best fit m/n ratio of a channel network. </br>ii) For chi_get_profiles.exe, a series of *.tree files which contain information about the best fit channel segments in chi-elevation space. This data can be used to infer erosion rates, tectonics, or variations in erodibility., tectonics, or variations in erodibility.)
  • Model:HydroCNHS  + (The outputs of HydroCNHS are stored in a dThe outputs of HydroCNHS are stored in a data collector object, an attribute of HydroCNHS (e.g., model.dc). The main output is the daily streamflow at routing outlets. However, this data collector object will also contain other user-specified agent outputs as long as users use this data collector object in their ABM modules.ata collector object in their ABM modules.)
  • Model:CVPM  + (The state of the system is periodically output to a binary file that can be read by the post-processing and visualization routines (see the CVPM modeling system user's guide).)
  • Model:STORM  + (The windfield for a cyclone based on pressure distribution and radius to maximum winds (SI units).)
  • Model:DHSVM  + (There are a number of different types of oThere are a number of different types of output that the model can produce. In short, the following possibilities are available:</br></br>DHSVM hydrologic output</br>* Default output (these files are always produced)</br>* Model state files</br>* Network flow files</br>* Travel time based hydrograph file</br>* Optional output files</br></br>Sediment Module output</br>* Default output (these files are always produced)</br>* Network flow files</br>* Optional output filesNetwork flow files * Optional output files)