See also: OATC Wiki Home

Date: July 6, 2010
Time: 16:00 - 17:00 CEST
Venue: Skype Conference Call
Topic: Extendable version of OpenMI 2 (continued)

Table of contents

Participants

Standa Vanecek, DHI (s.vanecek@dhi.cz)
Adrian Harper, Wallingford Software (adrian.harper@wallingfordsoftware.com)
Stef Hummel, Deltares (stef.hummel@deltares.nl)
Jesper Grooss, DHI (jgr@dhigroup.com)
Peter Schade, Bundesanstalt fuer Wasserbau (peter.schade(at)baw.de)

Apologies:
Rob Knapen, Alterra, Wageningen UR (Rob.Knapen@wur.nl)
Unknown User (don), Deltares (gennadii.donchyts@deltares.nl)

1. Progress towards OpenMI 2 Beta release

1.1. Source code update status - C#

1.2. Source code update status - Java

1.3. Documentation updates

Document

Update?

update author

author deadline

reviewer

deadline

What's new in OpenMI 2.0

yes

Stef, Peter

5. July

Stef

9. July

OpenMI 'in a nutshell'

yes

Adrian, Rob

5. July

who

9.July

The OpenMI Standard2 interface specification

yes

Stef, Peter

7. July

Peter

9. July

Migrating models

yes

Jesper

-

who

-

*.doc with accepted review issues

yes

Standa

-

-

-

1.4. Observations during working with the new standard

(Jesper) IDescribable has both setter and getter for Caption and Description, though these are I guess not really settable for others than the mother component. I have had to put in a number of "NotSupportedException" for the setter. Remove the setter?

(Rob) (thumbs down) I think the setters are there on purpose, since both caption and description for example should be modifiable by the user through a user interface. Unlike the ID, for which there is no setter in the interface.
(Team: Rob's argument is correct)

(Jesper) In 1.4 there was an event mechanism that could be used to propagate warnings from the engine to the OpenMI system (configuration editor etc). Now there is a StatusChanged event, which is much more specific. Being not a super-user of the OpenMI components, is it usefull to have such warnings from the engine in e.g. the configuration editor GUI or elsewhere? In that case maybe there should be a general purpose event on the IBaseLinkableComponent.

(Rob) What type of warnings would you like to propagate? Do we really want to include something like that in the standard, or leave it to the SDK (e.g. someone else might implement a (different) logging mechanism).

(Jesper) Where does the old EarliestNeededTime go? To the ITimeSpaceComponent.TimeExtent, or to each of the input items time extent?
(Stef) Has to be covered by the input items. See "Managing internal buffers using the consumer's time set" in Section 3.3.5 of the specification document.