...
The Delta Shell Framework should result in decreased maintenance and support costs. Furthermore, it should enhance exibility in modelling opportunities resulting in an increase of project acquisition. It also enhances knowledge sharing between developers and modellers. Lead time to market for new products (plug-ins) should be decreased when using Delta Shell as a development platform.
For users:
All modellers should be able to use the Delta Shell combined with the modelling models tools of their preference (ex. D-Flow 1D/2D, D-Flow FM, SimonaDelft3D, Mike11, etc.). The Delta Shell should facilitate modellers in batch execution (from command line), schematization (with/without graphical user interface), parallel execution (on clusters), calibration of models and running of models in standardized modelling environments (ex. OpenMI).
For developers:
The Delta Shell Framework should provide a generic, transparent and simple way of developing new or coupling existing modelling tools (plug-ins). The emphasis should be on reuse and expansion of existing code and features.
Architecture outline
The architecture outline of Delta Shell is shown in the figure below. As can be seen from the figure, Delta Shell consists of a set of common class libraries, mainly representing different domains and software standards such as:
...
features
...
These general framework class libraries define on a very high level how a typical console or graphical user interface application is constructed. They also define how different parts of the environment can be extended by means of plugins. This includes both:
- non-gui plugins providing new data types or computational models to the system, and;
- graphical user interface components used to visualize different data.
...
Background readings on Delta Shell
Unfortunately there currently is no complete set of documentation available for the Delta Shell components and interfaces and, additionally, the documentation that is available quickly becomes obsolete as development of Delta Shell progresses further.
Nevertheless, some background papers are available that are recommended for new Delta Shell developers to read before proceeding with any tutorials or exercises:
...
| Wiki Markup |
|---|
*\[TOOLS:TODO\] Add link to PDF{*} |
...
| Wiki Markup |
|---|
*\[TOOLS:TODO\] Add link to PDF{*} |
...
- DeltaShell Technical Reference Manual Architecture
Deltares Public Wiki: (http://publicwiki/display/DSM/DeltaShell)
Links to used open-source libraries
Additional information that might be useful, concerns the open source geospatial libraries that are used by Delta Shell. These background readings can be found at their repositories on the internet:
- NetCDF (http://www.unidata.ucar.edu/software/netcdf/)
- GeoAPI.NET (http://geoapi.codeplex.com/)
- NetTopologySuite (https://code.google.com/p/nettopologysuite/)
- SharpMap (http://sharpmap.codeplex.com)
NetCDF, GeoAPI.Net and NetTopologySuite are used closely together and have each been extended by Deltares to develop the Functional Coverages spatial API.
SharpMap is the Map UI component used by Delta Shell which has been extended by Deltares in a separate branch that can be found at the SharpMap repository (http://sharpmap.codeplex.com/SourceControl/latest#Branches/0.9.5-DeltaShell).
Some final notes:
...
.