| scrollbar |
|---|
| Excerpt |
|---|
...
|
...
| ||
| Panel | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
This tutorial provides a general overview of the application files as well as brief introduction of the most common user operations, which are available in the program. |
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|
How DelftShell files are organized
The DelftShell application consists of the 2 main parts, Main Application and a set of Plugins.
- Download DelftShell.zip from http://public.deltares.nl/display/DS/Home
...
- (tab
...
- Download)
...
- and
...
- uncompress
...
- this
...
- file
...
- In
...
- order
...
- to
...
- start
...
- the
...
- application
...
- go
...
- to
...
- the
...
- DelftShell\bin\Release
...
- start
...
- DelftShell.Loader.exe
...
- .
The Microsoft .NET
...
Framework
...
3.5
...
(
...
...
)
...
should
...
be
...
installed
...
on
...
your
...
computer
...
before
...
you
...
can
...
run
...
DelftShell.
...
This
...
will
...
start
...
the
...
application
...
and
...
will
...
show
...
a
...
screen
...
like
...
the
...
one
...
below.
The main graphical user interface is organized as a set of tool windows and document windows. A difference between those two is that the tool windows are always shown on the screen and the document windows are only used to visualize or edit a specific data type.
Typical examples of the Tool Windows are:
- Project Explorer - the main navigation window showing all data contained in the current project in a tree-like form.
- Message Window - logging windows, messages sent from models or different parts of the system are placed here.
- Property Grid - shows properties for an active selection of the graphical user interface.
- Toolbox - user-specific data shared between different projects (not fully implemented yet).
- Maps - tree-like window showing the list of the GIS layers in the currently opened map.
- Time Series Navigator - allows to navigate through times of any time-dependent data.
- Network - allows to view / edit structure of the currently opened (hydro) network.
When application is started - it automatically creates a default empty project so an user can immediately start filling it in with data, models, etc. A project can be seen as a currently opened user work document. An active project can be stored in SQLite database file format. Eventually DelftShell may store a model input / output data in a set of NetCDF files located next to the project file. So in total there are two non-proprietary file formats used to store project data.
| Tip | ||
|---|---|---|
| ||
Use F2 in Project Explorer in order to edit the name of the project, folder, model or any other item contained. |
Generally DelftShell can store the following data types in a project:
- Folder
- Model / Composite Model - working activities which the user can start in order to perform computations
- Data - any data type registered in the system, default contain e.g. Time Series, Regular Grid Coverage or more specific data types such as Network.
- <specific application documents such as Map or Chart> - these are non-data objects but more views configured in order to view those objects.
How to add new Time Series or any other data type to the project.
- Use a menu command shown on the screen below.
- After a dialog appears, a list of data types currently supported by the application are shown.
Note that Network (hydro network) is also considered as one of the supported data types. Actually an architecture of the system allows easy implementation of the user-specific data types, but this is a more advanced topic and will be covered in a Developers Guide (obsolete).
How to add a new computational model, e.g. Delft Flow Model 1D, to a project
Adding models to the project works almost the same as with data. The user has to select a model type via Project (right-click) > Add > New Model.
This is how it looks after demo 1D flow model is added to the project:
All model input and output data can be navigated via the Project Explorer tree view.
| Tip | ||
|---|---|---|
| ||
When model is selected in the project explorer you can define run time parameters of the model via Property Grid: |
Actually many parameters, not only for model, can be viewed or edited via the Property Grid when they are selected in the different windows.
How data, added to the project, can be edited
The graphical user interface supports different data types and most of them currently have a default editor. Usually the editor opens automatically when data / model is added to the project. But when it is closed - the user may re-open it by double clicking.
In some specific cases there may be more than two editors / viewers registered for one data type - in this case the gui will show a selection dialog where user can select a default type of the editor. The view type selection dialog can be activated by right-clicking on selected item in the Project Explorer and then selecting Open With.
| Tip | ||
|---|---|---|
| ||
When one of the Tool Windows is closed, it can be reopened with the View menu, e.g. View > Project Explorer. This will re-add it back in the main gui. |
| Tip | ||
|---|---|---|
| ||
When gui exits - it automatically saves all its settings data, including all tool windows layout, into the user custom settings file which is usually located in a directory: *C:\Document and Settings\<user name>\Local Settings\Application Data\Deltares\DelftShell*. Check this directory to see which files are saved. It is also possible to remove the whole Deltares\DelftShell directory, if you want to reset all user-specific settings |
How to import data into a project or export data to an external file format?
When you need to get a specific data type imported into the project one of the options is to use one of the existing Data Import plugins. The default installation includes some of them, for example importers make it possible to import a network from the older versions of the SOBEK or import a set of a grid files as a single time-dependent grid. Go to File > Import Data to open the Import Data window.
Current API of the DelftShell allows very easy implementation of the custom importers / exporters requiring very minimum knowledge of the whole system architecture. In some cases it can be extended by the team on request.
| scrollbar |
|---|