See also: OATC Wiki Home

Date: November 9 - 12, 2009
Venue: Alterra, Gaia building, room C011; Wageningen, The Netherlands

...

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 Unknown User (don), Deltares (gennadii.donchyts@deltares.nl)
~jgr@dhigroup.com, DHI (jgr@dhigroup.com)

Apologies:
~jnh@dhigroup Unknown User (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

...

If a component performs an update, it may neglect all "non consumed" output items. An output item is consumed if its list of consumers contains at least one item, and/or if its list of decorators contains at least one item.unmigrated-wiki-markup

Related to this: do we need {{void Update(params IOutputItem\[\] requiredOutputItems)}}, or is void Update() enough? The alternative is that the consuming component(s) register/deregister input items to/from the output items that they want to be updated.
After some discussion we concluded that we need a relevant use case for this. Rob will create one in Java, Stef will port it to C#.
If we decide to keep it in, we should explain in detail how a time progressing component behaves when the optional argument is given indeed.

My vote is to keep it. Typical use case is to ask component for an update only of some specific items, think about it as a query. We can then test components independently from the rest. E.g. query values only for selected areas event when component can provide data for many areas.

...

So the result of the discussion is that:

• Wiki Markup{{IlinkableComponent.Initialize(IArgument\[\] arguments)}} will be changed to {{{*}IlinkableComponent.Initialize()*}}

Gena:

IOutputItem.Consumers and IOutputItem.Decorators

...

Gena: ... it does not sound more explicit than Decorator, the word Derived is more generic compare to Decorated. My suggestion is to keep it as it is unless there are good arguments and examples why it should be changed.

I'd keep the word Item in anyway, then it is clear what we work with one item here. Meaning of the word Output feels much wider compare to IOutputItem (output can be a set of all model output items).

...

• 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 therelike the Buffer and the ElementMapper, on sourceforge and point out that they are there.

Rob: Alterra is now considering to host Java OpenMI SDK and Editor development on its own server with svn, trac (ticket system) and possible Hudson (continuous integration and maybe automatic QA). Looks like next year at least there will be resources available to work on a 2.0 SDK and maybe Editor. We can open the server for public contributions / collaboration on the development work for other interested parties. Will proceed along these lines unless OATC votes against it (the official Java Standard interfaces will stay on SourceForge and under OATC control).

Model migration

Samples

Simple River :

...

Gena will prepare sugestion for the structureAll came with the ideasWhen will be agreed - Gena will implement it and write short description

5 Next meeting

Next meeting will be handeled as the extension of the January OpenLife final meeting 13-14.1 2010. Place will be specified later.