Difference between revisions of "Change Log Kalypso 15.1"
Gernotbelger (Talk | contribs) (→Kalypso1D2D) |
Gernotbelger (Talk | contribs) (→Kalypso1D2D) |
||
| Line 81: | Line 81: | ||
| | | | ||
|- | |- | ||
| − | | valign="top" | | + | | valign="top" | A new concept of model specific boundary conditions has been introduced in order to improve the support for multiple models within Kalypso. |
| − | | | + | A boundary conditions (which is basically only the location of the condition) can now hold the boundary condition data for several models at once in parallel. |
| + | Depending on the specific type of the condition, data can be shared between models (such as a discharge condition). Other data types or only supported by specific models (such as hydraulic gradient with HYDRO_AS-2D or hhQ-conditons with Kalypso-RMA). | ||
| + | This also allows to theoretically calculate the same mesh with different models. | ||
| + | | [[Image:ChangeLog 15.1 1D2D ModelSpecificBCs.png|thumb|Different types of boundary conditions at the same boundary location]] | ||
|- | |- | ||
| valign="top" | TODO preview of bc | | valign="top" | TODO preview of bc | ||
Revision as of 11:39, 4 February 2015
Changes since: Kalypso-13.12 (see Change Log Kalypso 13.12)
Contents |
Kalypso Platform
Items that improve Kalypso in general.
| It is now possible to copy/cut and paste layers in the outline of the map view via it's context menu.
This allows for example to quickly rearrange layers into sub-folders. The copy/cut/paste functions are restricted to layers that have been added by the user. |
 |
| The import of projects of older Kalypso versions has been made smarter in such a way that Kalypso now automatically checks if a dataset is outdated when opening a project.
In this case Kalpyso informs the user that the project must be updated and does so after confirmation. |
KalypsoHydrology
| The comparison of scenarios, which has formerly been part of the functionality for merging scenarios has been reworked and is now a separate feature.
It is now possible to compare arbitrary scenarios via the context menu of the scenario view. The results of the comparison are exported as Excel workbook. The operation compares all relevant model elements by their properties such as:
|
 |
| It is now possible to export maximal values of result timeseries (currently only node discharge and volume is supported) from the result management view. This export replaces the former 'statistics result'. The results are exported as Excel workbook and contain the results for all nodes of all selected result datasets, i.e. the export of multiple simulations at once is possible.
An additional sheet in the excel workbook shows the maximum of all exported simulations and the information at what simulation this maximum is reached. This greatly facilitates determing the relevant variant of simulation sbased on design rainfall. |
 |
Error handling and validation of all model data has been improved in many little ways such as
|
 |
KalypsoWSPM
| Empty, please replace me with a real entry. |
Kalypso1D2D
| The timeseries import has been replaced with a trimeseries management equivalent to the timeseries management in KalypsoHydrology. The timeseries management allows to group timeseries by stations and to enter some metadata associated with these stations. |
 |
| A new 'cross section management' has been introduced that replaces the former functionality for importing sections into 1D2D and displaying them in the map.
Funtionality of the cross section management includes:
All cross sections are automatically displayed as layers in the map. |
 |
| The workflow of 1D2D has been cleaned up and been optimized for a more efficient and more logical handling. Functionalities that have been separated across multiple workflow items (such as timeseries import and timeseries view) have been integratied into one workflow task (such as timeseries management).
One notable change is that most tools for mesh editing (such a triangulation, refinement) have been removed as workflow tasks and are now part of the workflow task '2D-discretisation' in form of map tool. This avoids switching between workflow tasks while editing the net. |
 |
| The layer structure of the 1D2D map has been restructured in a more logical way. Some redundant layers have been removed from the map. |  |
| The internal handling of the mesh structure has been optimized for much bigger meshes.In order to work with very big meshes, a machine with a 64bit core and at least 8GB of memory is recommended. |  |
In order to support more and other models within Kalypso1D2D (such as TELEMAC-2D or HYDRO_AS-2D), the data structures and concepts of Kalypso have been reworked in a very general way. Most notably, two key ideas have been implemented (see further points for more details):
Due to these changes, projects of older version of Kalypso are automatically converted to the new data formats when opened the first time in the current version. |
|
| A new concept of model specific boundary conditions has been introduced in order to improve the support for multiple models within Kalypso.
A boundary conditions (which is basically only the location of the condition) can now hold the boundary condition data for several models at once in parallel. Depending on the specific type of the condition, data can be shared between models (such as a discharge condition). Other data types or only supported by specific models (such as hydraulic gradient with HYDRO_AS-2D or hhQ-conditons with Kalypso-RMA). This also allows to theoretically calculate the same mesh with different models. |
 |
| TODO preview of bc | |
| TODO calc unit - control parameters | |
| TODO control nodes | |
TODO: support for more and other data types:
|
KalypsoRisk
| Empty, please replace me with a real entry. |
