See also: OATC Wiki Home

Date: September 7 - 10, 2009
Venue: Alterra, Gaia building, room C011; Wageningen, The Netherlands

Participants:

Rob Knapen, Alterra, Wageningen UR (Rob.Knapen@wur.nl)
Standa Vanecek, DHI (s.vanecek@dhi.cz)
Adrian Harper, Wallingford Software (adrian.harper@wallingfordsoftware.com)
Stef Hummel, Deltares (stef.hummel@deltares.nl)
~don, Deltares (gennadii.donchyts@deltares.nl)
~jgr@dhigroup.com, DHI (jgr@dhigroup.com)

Apologies:
~jnh@dhigroup.com, DHI (jnh@dhigroup.com)
Peter Schade, Bundesanstalt fuer Wasserbau (peter.schade@baw.de)
Daniele Andreis,Universita` di Trento,(daniele.andreis@gmail.com)
Jan Gregersen, LicTek

Documents:

http://www.openmi.org/
http://sourceforge.net/projects/openmi
wiki.openmi.org

Table of contents

1. Status of the implementation

GUI:

Under development and is usable for simple compositions, clearly work on this will continue until end of year

Compliancy xsd:

Sugestion = self contained task that review can be by email during december rather than at an OATC meeting

Standard

IIdentifiable

Accepting the need to keep IIdentifiable and IDescriable separate (as discussed at length in last meeting). I still feel uncomfortable with an interface with one method in. I find in the UI I am writing more code for which I feel no constructive benefit from except for making code more obscure to read. I would like to suggest that we replace the interface with a

Id { get; }

attribute on the interfaces that require it. I wont defend this if there is great objection to it, life's too short!

UserCount

A component should be able to keep track of how many users are interested in an exchange item's output.

IArgument.IsReadOnly

Is it really really needed (Stef though so, but doesn't consider it essential anymore).

Terminology

Are we sure that we want to use the name Decorator instead of the well known name DataOperation?

SDK

The original packages in the 1.4 SDK are not that explitely identifiable in 2.0. Besides of that, more then one model wrapping utility has been developed (by Adrian and by Stef/Jesper), so we should determine what to put in which package.
Other things that to take care of:

• split time buffering and time interpolation
• distinguish one or more decorator packages, implemenented as a third party factory

Java

Standard

During this week, the Java version of the standard has to be implemented and documented.

Utilities/GUI

We will currently put no effort in addinonal java developments, like the backbone, the GUI etc. Most probaby, there will be no time left in the OpenMI-Life project (ending end of Januari) to put any real effor to java.
However, next to having the standard, we will take to:

• have examples of IQuality/ICategory available in the C# version
• put the already available java utilities, like the Buffer and the ElementMapper, on sourceforge and point out that they are there.

Model migration

Samples

Simple River :

Have reviewed and modified src as Stef requested

GroundWater :

NOTE JESPER, have also started modifying the simple GW model for use in examples/tutorials etc., currently WIP will take you through that at next weeks meeting. You might notice that I have moved these examples into new folder structure to facilitate sharing of common code.This common code might find its way into the SDK in the future, or remain seperate as a seperate example. For us to decide lator.

2. Documentation

Main task for the meeting
Create maximum documents to be send to Stephen for review.
Assign rest of the documents to the individual persons

Documentation of the standard.

What it the status of Stephen's review on the C#-oode for the standard? Standa will send Stephen an e-mail.

What is OpenMI - Tutorials

*1 minute tutorial * // suggestion
Download Bin + install
Run GUI
Load composition
Run Composition
See Messages - progress
Look to the results

Status: To be realized as part of the on line help. Will be done by Adrian.

10 minute tutorial // suggestion
Download source code???
Download documentation (standard) ??
Download / compile + install
Open GUI
Create composition - Run composition
See Messages - progress
Look to the results
Add decorator - run ......
Open Reference manual - see basic schema
Clases
Status diagram
Composition XLS
OnenMI model compliensy
Load complex composition
Review of the Components / decorators, links ... properties
Open source code of the hard coded running of the composition

Status: To be realized as part of the on line help. Will be done by Adrian.

Scope document

need to be divided betwean more peoples / per chapters. Simplified contents of all chapters need to be created during meeting

Whats new in 2.0

Final review of existin document need to be done

GUI

Help document, with 2 turials
Started, using SimpleRiver and SimpleGW models, first draft on schedule for Nov end

OpenMI 2.0 Standard specifications

Standard Reference manual (class library) need to be checked if all comments are in the source code -> generate UML
SDK Developer guide/documentation
SDK Reference manual (class library) comments need to be placed in source code -> generate UML

How to

Various HowTo's will be provided (see the How To).
The table below shows the status of and the persons working on these HowTo's. Possible statuses:

• todo
• to adjust (according to new Standerd/SDK)
• first version
• basic skeleton exists (fill in)
• reviewed
• sent (to Stephen Morris)
• ready

! How to port the OpenMI from Windows to Linux | todo | ?? | ?? |

Note 1: this is a big task, lot of changes need to be done
Note 2: The OpenMI 2.0 compliant component has not been not been generated on Linux yet. The generation should follow the same rules as the generation of a component being OpenMI 1.4 compliant