Property:Describe pre-processing software


This is a property of type Text.

Showing 20 pages using this property.
ArcGIS to produce the flow direction file and convert the files to ESRI ASCII format.  +
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)  +
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.  +
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.  +
Excel  +
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:  +
For spatial case one can developed its own pre-processing in order to put the input dataset in the format readable for GIPL.  +
GIS  +
GIS software  +
GIS software and Delft3D toolkit  +
GIS, Remote Sensing packages  +
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.  +
Initial centerline needs to be created or digitized. Hyrologic and sedimentary parameters need to be estimated from external information. See documentation.  +
Input is the along-channel width profile. You can obtain this for example with google earth and GIS software.  +
It is used to digitize the data and describe the problem, simulation programmes  +
Note that many input files are created using GIS and advanced skills are required.  +
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 After providing the required information, users can download the resultant input files and run OTIS in the usual manner.  +
Post-processing and (pre-processing) is through Matlab scripts.  +
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.  +