Property:Describe pre-processing software

From CSDMS

This is a property of type Text.

Showing 52 pages using this property.
H
A channel network must be extracted for the landscape, this is performed using the DrEICH algorithm (https://csdms.colorado.edu/wiki/Model:DrEICH_algorithm).  +
D
A chi analysis of the landscape must first be performed to get the correct m/n value for the landscape. This can be done using the chi analysis toolkit available on CSDMS (https://csdms.colorado.edu/wiki/Model:Chi_analysis_tools).  +
O
All I/O is done with flat ASCII files; The 'MINTEQ Input file' is created using the Proteq utility; remaining input files may be created using a text editor  +
T
Another program must be used to create the input grids. This includes a D8 flow grid derived from a DEM for the region to be modeled. The earlier, IDL version of TopoFlow can be used to create some of these.  +
Another program must be used to create the input grids. This includes a D8 flow grid derived from a DEM for the region to be modeled. The earlier, IDL version of TopoFlow can be used to create some of these.  +
Another program must be used to create the input grids. This includes a D8 flow grid derived from a DEM for the region to be modeled. The earlier, IDL version of TopoFlow can be used to create some of these.  +
Another program must be used to create the input grids. This includes a D8 flow grid derived from a DEM for the region to be modeled. The earlier, IDL version of TopoFlow can be used to create some of these.  +
Another program must be used to create the input grids. This includes a D8 flow grid derived from a DEM for the region to be modeled. The earlier, IDL version of TopoFlow can be used to create some of these.  +
Another program must be used to create the input grids. This includes a D8 flow grid derived from a DEM for the region to be modeled. The earlier, IDL version of TopoFlow can be used to create some of these.  +
Another program must be used to create the input grids. This includes a D8 flow grid derived from a DEM for the region to be modeled. The earlier, IDL version of TopoFlow can be used to create some of these.  +
Another program must be used to create the input grids. This includes a D8 flow grid derived from a DEM for the region to be modeled. The earlier, IDL version of TopoFlow can be used to create some of these.  +
Another program must be used to create the input grids. This includes a D8 flow grid derived from a DEM for the region to be modeled. The earlier, IDL version of TopoFlow can be used to create some of these.  +
Another program must be used to create the input grids. This includes a D8 flow grid derived from a DEM for the region to be modeled. The earlier, IDL version of TopoFlow can be used to create some of these.  +
Another program must be used to create the input grids. This includes a D8 flow grid derived from a DEM for the region to be modeled. The earlier, IDL version of TopoFlow can be used to create some of these.  +
Another program must be used to create the input grids. This includes a D8 flow grid derived from a DEM for the region to be modeled. The earlier, IDL version of TopoFlow can be used to create some of these.  +
Another program must be used to create the input grids. This includes a D8 flow grid derived from a DEM for the region to be modeled. The earlier, IDL version of TopoFlow can be used to create some of these.  +
Another program must be used to create the input grids. This includes a D8 flow grid derived from a DEM for the region to be modeled. The earlier, IDL version of TopoFlow can be used to create some of these.  +
Another program must be used to prepare the required input grids. These include a D8 flow grid and a slope grid, extracted from a DEM of the area.  +
A
ArcGIS for calculating Area, Slope and D8 Flow direction  +
M
ArcGIS or similar  +
P
ArcGIS to produce the flow direction file and convert the files to ESRI ASCII format.  +
R
Associated with the RHESSys simulation are a number of interface programs which organize input data into the format required by the RHESSys simulation model. These include a standard GIS-based terrain partitioning program, r.watershed, and other basic GIS routines as part of the GRASS GIS system and two RHESSys specific programs: # GRASS2WORLD (derives landscape representation from GIS images) # CREATE_FLOWPATHS (establishes connectivity between spatial units)  +
G
Available as jupyter notebooks based on CSV and numpy compressed arrays format. The documentation contains some workflows and functions that helps, among others, to pre-process netCDF elevation and climate dataset, plate velocity files and to create an unstructured spherical mesh used as input for gospl.  +
C
Channel profile data must be prepared to meed the specifications of the *.chan file. The format of this file is described in the documentation provided with the source code.  +
S
Excel  +
L
External Dependencies and Programs. LTRANS requires NetCDF libraries and uses the following programs to calculate random numbers (Mersenne Twister) and fit tension splines (TSPACK). Because LTRANS reads-in ROMS-generated NetCDF (.nc) files, it requires that the appropriate NetCDF libraries be installed on your computer (see files and links below). Also, please note that although the Mersenne Twister and TSPACK programs are included in the LTRANS in the Random_module.f90 and Tension_module.f90, respectively, they do not share the same license file as LTRANS. See also: http://northweb.hpl.umces.edu/LTRANS.htm  +
G
For spatial case one can developed its own pre-processing in order to put the input dataset in the format readable for GIPL.  +
GIS  +
C
GIS software  +
D
GIS software and Delft3D toolkit  +
F
GIS, Remote Sensing packages  +
R
In cases where the standard required the use of a non-typical format (as in the use of the machine-independent binary HDF formats for large arrays), then the data transfer to and from LRSS is handled using a pre- and post-processing layer.  +
S
Initial centerline needs to be created or digitized. Hyrologic and sedimentary parameters need to be estimated from external information. See documentation.  +
E
Input is the along-channel width profile. You can obtain this for example with google earth and GIS software.  +
T
It is used to digitize the data and describe the problem, simulation programmes  +
M
D
Note that many input files are created using GIS and advanced skills are required.  +
O
OTIS relies on flat ASCII (text) files for input and output. At present, a graphical user interface for comprehensive management of OTIS input and output is not available. OTIS input files have traditionally been developed on the user's local computer system using a text-based editor. As an alternative, users may fill out the web-based forms available via the Generate Input section of http://water.usgs.gov/software/OTIS/. After providing the required information, users can download the resultant input files and run OTIS in the usual manner.  +
C
Post-processing and (pre-processing) is through Matlab scripts.  +
R
Pre-processing software is optional and should be used if the code is to be developed for specific vegetation communities. The software creates two-dimensional lookup tables for fluid mechanical parameters such as bed shear stress, depth-averaged drag force, and dispersion coefficients as a function of water depth and mean flow velocity. Lookup tables encapsulate the results of detailed simulations of velocity profiles under different combinations of water-surface slope and surface-water depth. See description in Larsen et al., Ecological Engineering, 2009.  +
M
Preparation if input files, particularly initial elevation matrix.  +
H
QGIS may be needed to preprocessing some files.  +
A
See: http://adcirc.org  +
W
The WRF Preprocessing System (WPS) is a set of three programs whose collective role is to prepare input to the real program for real-data simulations. Each of the programs performs one stage of the preparation: geogrid defines model domains and interpolates static geographical data to the grids; ungrib extracts meteorological fields from GRIB-formatted files; and metgrid horizontally interpolates the meteorological fields extracted by ungrib to the model grids defined by geogrid. (See also: http://www.mmm.ucar.edu/wrf/users/docs/user_guide_V3/users_guide_chap3.htm)  +
D
Though the component can use a simple slope-area threshold to delineate channels, it is much more preferable to use some channel-head extraction method like those of Passalacqua et al (2010, Journal of Geophysical Research), Pelletier (2013, Water Resources Research), or Clubb et al (2014, Water Resources Research).  +
S
To assist STWAVE users in generating input files and visualizing output files, a user interface has been built for STWAVE within the Surface-water Modeling System (Brigham Young University Engineering Computer Graphics Laboratory (ECGL) 1997). The SMS interface supports grid generation, interpolation of current fields, generation of input spectra, visualization of wave heights, periods, and directions, and visualization of output spectra. Non-Corps users can get information from ECGL (http://www.ecgl.byu.edu).  +
C
To improve stability of the computations, it is recommended to pre-process bathymetry map with depth_ssl (module included with the source code).  +
W
While some parameter files and templates are included with the model source code, most must be generated by the user. We provide a number of scripts and preprocessing utilities on the WRF-Hydro website (https://ral.ucar.edu/projects/wrf_hydro) in order to aid in this process. These include NCAR Command Language (NCL) scripts to regrid forcing data from commonly used data sources, R scripts to generate parameter and model initialization files, and a set of Python based ArcGIS pre-processing tools.  +
C
Yes - ish - uses arc GIS ascii formats - commonly available.  +
R
Yes, pre- and post-processing, and visualiztion tools provided in software package  +
B
idealized experiments can be run with simple text files as input, but for realistic cases input data needs to be created with e.g. python, matlab or fortran scripts.  +
F
taudem : Enable (True) or disable (False). Default is enabled. Parameter enables or disables TauDEM pre processing steps. Disabling will fail to generate any pre-processing files needed for FACET. The toggle is useful for re-running FACET without needing to also re-run all the pre processes steps. taudem cores : Parameter to set the number of cores TauDEM can use for generating pre processing files. If you experience performance issues reduce the number of cores. Default is set at 2. wt_grid : Enable (True) or disable (False). Default is enabled. Parameter to toggle the creation of a weight grid from NHD stream lines. Disabling will fail to generate *_wg.tif an important input for pre-processing steps. The toggle is useful for re-running FACET without needing to also re-run all the pre processes steps. resample resolution : The input is integer and the default is set to 3 meters. The units are always in meters. This parameter is the resolution to which the user wants the DEM resampled to. FACET uses ‘resample resolution’ to set the cross-section point distances parameter i.e. ‘xnptdist’. This ensures bank point spacing aligns with the DEM’s resolution.  +