Difference between revisions of "ReleasePlanKalypso220"

Revision as of 18:49, 2 February 2009

Kalypso - Release Plan for Version 2.2

Roadmap

Kalypso Platform

Items that improve Kalypso in general.

Proposed items

Leverage the full potential of the eclipse 3.4 command framework

Partly done; most important, some cosmetic changes to map-toolbars of 1d2d, risk and flood modules should be applied.

I18N

General i18n of the main modules

Translations at least for English and German

Committed items

Usage of Eclipse 3.4 command framework

Map context and appropriate commands have been defined; all standard map commands rely on this mechanism.

Deferred Items

Memory handling

Kalypso consumes lots of memory, which prohibits to work with very large models. Also some known memory leaks should be fixed as well (same applies to UI-handles).

REMARK: this has partly already been done for Kalypso 2.1. What is the real need now?

Accessing GML data

Access to GML should be reworked. For example zip'ed GML will greatly reduce storage consumption on users machine; accessing only parts of GML (using WFS techniques) would enhance performance and memory management.

REMARK: this has partly already been done for Kalypso 2.1. What is the real need now?

Consumability / Reliability

This work will make it easier for users to get Kalypso, install it on their systems, and configure it for their use. It will also enhance the error handling and reporting mechanisms to make it easier to service Kalypso in the field.

Proposed items

Update-Mechanism

Use Eclipse 3.4 Update mechanism in order to easily update Kalypso.

Bug/Feature-Reports

Integrate report mechanism directly into Kalypso UI.

Committed items

None at this time

Deferred Items

None at this time

1D/2D

Proposed items

general

style editing

Enable style editing in maps of 1D/2D perspective

speed up map drawing

How???

scenario handling

Is there any general conceptual thing to do? Otherwise functionality of deriving a scenario should exclude already derived scenarios from new derivation because there will be too many copies. Besides duplication of scenarios (again without sub scenarios, perhaps as choice from user) should be possible.

WMS(/WFS/WCS)

suggestions Give a suggestion list of available web server for data to process on.

processing

Memory handling

The current main bottleneck is the processing of 1D2D tin results in memory. Writing the results directly to disk should fix this main problem.

detailed definition of URFC

Enable the detailed setting of the under relaxation factor for each time step in a very comfortable way. This feature could extremly speed up the calculation speed.

import timeseries from RRM Enable

import of timeseries data that was processed/ calculated in KalypsoRRM? (i.e. just import timeseries, that are already zml)

Support other calculation cores

Other calculation cores (such as RMA2 and RMA10, Hydro-AS) should be supported, based on the same mesh-data as RMA10S (see KalypsoProdcutRoamdmap2_1CalcCores).

different junction approaches

Enable momentum controlled, energy controlled and water stage controlled 1D-junctions

manual calculation interruption

Enable manual interruption of calculation without total abruption, i.e. results processed so far should be interpreted

show chosen timeseries

Display chosen timeseries in control panel graphically

preprocessing

Net editing

The user experience with the net can be improved in many ways; for example refinements of the net are needed as well as integration of the GAJA3D toolkit. Management of net changes between calculations (consider restart!). The handling of terrain models should be refaktored in order to use the improved grid mechanisms.

2D net import

Allow the user to import a shape(z) file that represents the mesh geometry.

MAP widget - Infobutton

Infobutton for the node theme should display the node's elevation

Triangulation of discretisation

Enable processing of terrain TIN in preprocessing to visualise problematic parts of the mesh. At the moment the TIN is only created, if at least on calculation step is done successfully. Besides the problem occurs, that the terrain TIN can only be visualised in the result.map. It should become part of the fenet.map.

1D Preprocessing

The 1D preprocessing (aka determination of polynomials) should be possible without WSPM. For that, a profile management tool and also handling of initial restart data is needed in 1D2D.

1D-profile editor

Enable profile editing in 1D/2D, i.e. full profile editor functionality of WSPM

WSPM-1D/2D synchronization

Give a possibility to synchronize changes of models in WSPM with model data (terrain.gml) in 1D/2D, if e.g. user changes active flow region etc.

two-directions 1D-control structure

Support the generation of wwQ-relationships for both flow directions seperatly (changes in GUI and calculation core)

activation of control structures

Add a possibility to switch on/off individual control structures in a calculation unit or generally. Point is just to be able to switch off a control structure without deleting the data set.

support binary elevation models

Change data format for elevation models to binary data format like in FloodModeller? and RiskModeller?.

concave polygons

Validation check for polygons prohibits drawing of concave polygons, because first node for concavity is not allowed to be drawn. Better just prohibit FINISHING a self cutting polygon.

polygon Snapping

Enable snapping for polygon drawing (e.g. for roughness polygons)

polygon editing

Enable possibility of adding a node to the linear ring or moving a particular node of the linear ring

delete unused widgets

widgets "Ein Element entfernen", "ein Element erzeugen", "ein Element editieren" (Schere, Plus, Bleistift) are without function and have to be deleted

leave zooming widgets always in control bar

Some general widgets disappear, if map is not the active view. This leads to pressing the wrong widget, if the map-activation-click is direclty made on another widget that is placed on the left hand side of the hidden widgets. ('prohibit jumping of widgets')

pasting into time series

Enable pasting into the table of a boundary condition

improve Bandgenerator

Connection lines between 1st and 3rd boundary lines are straight. They should connect equal distant distributed nodes in between.

roughness classes update

Update usable roughness classes with literature source

results

Improve result processing

Result processing is limited because memory consumption is too high. This should be one of the key issues for the next release.

Result Post Processing

Allow selective and/or lazy result processing. Improve result visualization (i.e. 3D, dynamic, compare). Also new types of results(-views) should be considered (i.e. dynamic flow pathes, ...).

Overwrite existing results

Overwrite existing results for setting in timeseries results view. Problem is, that user has to set up nodes again after each new calculation. Additionally take Profile kilometer as default name.

Marsh-vectors

Enable marsh water depth display and Marsh-vector display in plan view. (Let's have a deeper discussion about, what could be done to understand Marshing-algorithm better, too). This task is very important, as it can extremly increase the stability of the model. Following should be visualizable optionally: Marsh depth/slot depth, Marsh vectors, Marsh water depth results, effective porosity results, type of active Marsh range ...

Active/Inoperative elements

Enable the visualisation of boundary lines of the active flow region. Besides display the active/ inoperative elements at a particular run

Line checks

Introduce result evaluation at cross section definitions in 2D meshs. Also integrate them for evaluation of longitudinal sections through 2D-mesh parts for calculation of Q and average v.

Longitudinal section setup

Enable longitudinal section setup, i.e. be able to set up connections of longitudinal sections of base units in coupled units.

Add timeseries to tables

Enable additional loading of time series to results graphics to be able (e.g. for calibration)

Belated evaluation of results

Enable the evaluation of particular result steps of unsteady calculations. Besides an import of results from external calculations would be nice.

Improve error messages and log messages

Improve error messages from the calculation core (Errors, warnings, hints, direkt access to nodes etc., iteration table, activation/deactivation of nodes/elements ... )

completly new features

IMPORTANT:

support rm1-model files Enable Prof. King to use our GUI

Loading of files

Enable loading of external results and external control files (r10)

enable side friction e.g. for walls

Make use of the shore line friction functionality of RMA·Kalypso, that already exists

Calculation Units

Implement an import / export functionality for calculation units (and all underlying data) in order to share / exchange calculation units beyond projects.

2D-control structures

Add possibility to introduce 2D control structures as weirs, sluice gates etc.

enlarge cstrc-possibilies

Add additional calculation possibilities for weirs

channel profiles (GEO-approach)

Enable 1D-sections with original RMA10S-definition method (geometric approach)

parameter settings

Set up general calculation core parameters like memory settings, inflow element number etc.

Calculation core compatibility

Add general information page, which calculation core versions are supported in a certain Kalypso version

Inflow elements

More refinement of inflow elements, i.e. differ between inflow elements with or without predefined inflow direction (momentum influence). Develope inflow groups (deep cogging with calculation core, see other road map)

widening/contraction losses

Develope feature for consideration of widening and contraction losses in 1D approach (deep cogging with calculation core, see other road map)

local losses

Develope feature to consider local losses (deep cogging with calculation core, see other road map)

simplified bridges/weirs

Develope feature to consider bridges/weirs in simple form as local loss with formula of Cidarer (deep cogging with calculation core, see other road map)

Committed items

None at this time

Deferred Items

None at this time

WSPM

Proposed items

Profile Interpolation

Enhance Profile Management/Display

Enforce work with map in general

Synchronisation Map - Chart

Distinguish profiles from different strands/water bodies

Result Post Processing

Enhance visualization of results, for example show waterlevels in profiles, show multiple results in one chart, ...

Support for 'Energieverlust'

Workflow for WSPM

Profile DGM Extraction

Committed items

None at this time

Deferred Items

None at this time

RRM (NA)

Committed items

None at this time

Proposed items

workflow support

Theoretical workflow already exists. Workflow support for RRM is really necessary

statistical analysis Add statistical analysis functions

Deferred Items

None at this time

Flood

Committed items

None at this time

Proposed items

None at this time

Deferred Items

None at this time

Risk

Committed items

None at this time

Proposed items

Additional outputs

generate more 'in between results' during risk calculation as damages etc.

Additional outputs

formats export grids as shapes.

single damage calculation

Enable calculation of damage for single flood events

Deferred Items

None at this time