See also: OATC Wiki Home

Date: September 8-10, 2008

...

Jan Gregersen, DHI / LicTek (gregersen@lictek.dk) (chairman of the meeting)
Adrian Harper, Wallingford Software (adrian.harper@wallingfordsoftware.com)
Stef Hummel, Deltares (stef.hummel@deltares.nl)
~don Unknown User (don) (Gena), Deltares (gennadii.donchyts@deltares.nl)
Peter Schade, Bundesanstalt fuer Wasserbau, Germany (Peter.Schade@BAW.DE)
Andrea Antonello, Universita` di Trento, (andrea.antonello@gmail.com)
Rob Knapen, Alterra (Rob.Knapen@wur.nl)

...

Apologies:

~psi@dhigroupUnknown User (psi@dhigroup.com), DHI - Water & Environment (psi@dhigroup.com)
~onnoroos Unknown User (onnoroos), Alterra (Onno.Roosenschoon@wur.nl)
Peter Gijsbers, Deltares (Peter.Gijsbers@deltares.nl)
Jon Goodall, Univ South Carolina (goodall@engr.sc.edu)

...

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

Agenda & draft minutes (in blue)

1. Minutes from previous OATC meeting

...

2. Maintenance and support

2.1 Reported bugs

(GOTO bug list on SourceForge)

Help issues

(GOTO help issues on SourceForge)

Discussion issues

(GOTO discussion issues on SourceForge)

3. OpenMI 2.0 Issues

3.1 Use cases

GOTO use cases

3.2 OpenMI 2.0 architecture

3.2.1 Current status

We need to remind ourselves about the current status for the OpenMI version 2 development - what is implemented and why. See also: OpenMI.Standard ver 1.4 to ver 2 change log

3.2.2 Configuration interfaces

At the last OATC meetings the focus has been on interfaces that relates to the configuration part of the standard

see also: Jan's ideas for version 2 configuration interfaces

3.2.3 IQuality and IQuantity

One of the change requests we have received for OpenMI Standard version 2 is the ability to handle categorized data. Examples could be "high", "medium", "low" or "grass", "corn", "potatoes".

See use case: Qualitative data support

See UML for proposed OpenMI interfaces

3.2.4 Spatial issues

We will focus on the spatial issues at the next OATC meeting in Delft. However, since Andrea is attending this meeting, it could be wise to start the thinking process now, utilizing his knowledge about GIS and specifically OpenMI GIS.

3.3 Development and release road map

Some time ago a prioritized list of issues that should be included in the next release was elaborated (OpenMI version 2 Development plan ). Seems that we already have covered most of the issues plus the quantity/quality issues, which are not listed in the plan. However, we still need a plan with some more strict deadlines.

Since we are dealing with a standard release we must follow the procedure for OpenMI standard releases. So far we do not have such procedure formally accepted by the OAEC. On this agenda (point 4.1) is a proposal for a procedure. So, let's discuss this first and then see how we can fit some dates into this.

Minutes: There are currently two open bug reports; one about unit conversion that does not handle missing values correctly and one about comparison of time horizons. Adrian and Jan will fix those bugs.

2.2 Help issues

(GOTO help issues on SourceForge)

Minutes: There is a fine activity on the help forum. We try to answer help request quickly (within a day), but unfortunately this sometimes takes longer. Hence, everyone is encouraged to subscribe the the help forum in order to receive a mail notification when new help issues are submitted. Jan will keep an eye on the forum and forward the help issues to OATC members if such issues are not already answered within a reasonable time.

2.3 Discussion issues

(GOTO discussion issues on SourceForge)

Minutes: Same comments as for Help issues (2.2 above)

3. OpenMI 2.0 Issues

3.1 Use cases

GOTO use cases

Minutes: We are not currently not actively using the use cases for the version 2 architecture development and we do not think there is a need for writing additional use cases at this moment. However, when the draft version 2 architecture is ready, we will review the use cases in order to ensure that features described by these are taken into account in the new OpenMI standard.

3.2 OpenMI 2.0 architecture

3.2.1 Current status

We need to remind ourselves about the current status for the OpenMI version 2 development - what is implemented and why. See also: OpenMI.Standard ver 1.4 to ver 2 change log

Minutes: Stef explained the recent developments and the current status for the OpenMI version 2 standard to the meeting participants.

3.2.2 Configuration interfaces

At the last OATC meetings the focus has been on interfaces that relates to the configuration part of the standard

see also: Jan's ideas for version 2 configuration interfaces

3.2.3 IQuality and IQuantity

One of the change requests we have received for OpenMI Standard version 2 is the ability to handle categorized data. Examples could be "high", "medium", "low" or "grass", "corn", "potatoes".

See use case: Qualitative data support

See UML for proposed OpenMI interfaces

3.2.4 Spatial issues

We will focus on the spatial issues at the next OATC meeting in Delft. However, since Andrea is attending this meeting, it could be wise to start the thinking process now, utilizing his knowledge about GIS and specifically OpenMI GIS.

Minutes:
Based on the discussions in the meeting Jan has updated the standard in the trunk on source forge. See UML below:

Image Added

3.3 Development and release road map

Some time ago a prioritized list of issues that should be included in the next release was elaborated (OpenMI version 2 Development plan ). Seems that we already have covered most of the issues plus the quantity/quality issues, which are not listed in the plan. However, we still need a plan with some more strict deadlines.

Since we are dealing with a standard release we must follow the procedure for OpenMI standard releases. So far we do not have such procedure formally accepted by the OAEC. On this agenda (point 4.1) is a proposal for a procedure. So, let's discuss this first and then see how we can fit some dates into this.

Minutes:
With respect to version 1.4.1 release, we will go into beta by the next OATC meeting in Delft, and a release on December 20 th 2008. Everyone in encouraged to start using the GUI version 1.4.1 now.


Version 2 development plan:

September 11th 2008 - November 2nd 2008
Finish the configuration architecture (the decorator pattern)and update SDK and GUI.

November 3 - November 5 2008.
OATC meeting in The Netherlands: special focus on return types and geometry (ElementSet)

November 6th 2008 - January 12th 2009
Implementation of new geometry interfaces and return types. Update SDK and GUI

January 13th - January 15th 2009
OATC meeting in UK. Final decision for the version 2 standard interfaces. This also implies deciding which requested feature that will not be include in version 2.

January 16th - March 9th 2009
Complete implementation and unit testing of the version 2 standard, SDK and GUI

March 10 - March 12 2009
OATC meetings, Denmark. OpenMI 2 standard, SDK and GUI beta release

March 13 - April 20, 2009
Migrate and test selected commercial models and components for version 2

April 21 - April 23
OATC Meeting i The Netherlands. Evaluate real models test and further refinements for version 2

April 24 - June 09 2009:
Continues real models testing, write documentation.

June 10 - June 12 2009
OATC meeting in Denmark. Final evaluation, submission of the version 2 to the OpenMI Association Executive Committee for acceptance

June 13 - October 13 2009
The standard is reviewed by external reviewers

October 14 - December 19, 2009
Adjustments based on comments from the reviewers. Finalization of the OpenMI 2 release.

December 20th 2009
OpenMI 2 standard, SDK and GUI releaseMinutes:
with respect to version 1.4.1 release, we will go into beta by the next OATC meeting in Delft, and a release on December 20 th 2008. Everyone in encouraged to start using the GUI version 1.4.1 now.
Version 2:
OATC Meeting November: Configuration finished. Draft for Spatail and return types.
OATC Meegting January 09: Cut off meeting, kick out things cannot achieve.
OATC Meeting March: SDK, Standard, and GUI in beta version.
OATC Meeting June 09: Tested real models finished, submission of the standard to the OAEC:
Review period (4 months)
Update period (3 months)
Release in December 2009.

3. OpenMI Java and OpenMI .net synchronization

...

Rob: Maybe it is (sometimes) a solution to serialise the object as XML or JSON and then exchange them from Java to C# and back. There might be open source solutions, e.g. http://woxserializer.sourceforge.net/^{Image Removed}. Of course performance is a potential issue.

4. OATC Procedures

4.1 Proposal for procedures for OpenMI Standard releases

From Jan: I have at task from one of the previous OpenMI Association Executive Committee meeting to elaborate a proposal for OpenMI Standard release procedure. These procedures will define the rules for how to go from OpenMI Standard release version x to OpenMI standard version x+1. I think that the OpenMI standard it selves is the most important asset of the OpenMI Association, which also means that rules for how this standard may be change becomes very important. I thought a lot about it (apparently, more difficult that I first anticipated), and I *Minutes:* have now written my first idea down in draft form. I would appreciate if we, at the OATC meetings, could discuss these ideas.
Please review the Proposed procedure for OpenMI Standard releases.

...

Minutes:
It was agreed that a Wiki would be the best solution. On a longer term we may want to use a real content management system, which makes nice formatting possible, but for now the contents of the pages are considered more important that the appearance. Adrian will investigate if WSL can provide a server to host the WIKI and Stef will investigete investigate if Deltares can host. We aggree agree that our current wiki for OATC (Confluence) is the best choice. Jan will make sure that this issue is on the agenda for the next AOEC meeting.

Confluence can be also customized to make layout look more professional like using plugin like Adaptivist Theme Builder . If we have time - we can also use current web site design materials for it.

...

(from Rob Knapen( There are some people expressing interest to contribute to the OpenMI
Java development, any ideas how this can be set up? Is it something the
OpenMI TC would like to handle, as part of the OpenMI open source
community?

Minutes:
Curret status: the The Java SDK is under MyOpen Source on source forge , is difficult for people to find.
Rob and Andrea will make a wiki HowTo page describing the Java SDK and explaining how to use it and where to download it.

...

From Jan: For some reason I like to have a full copy of OpenMI SourceForge repository on my local disk. However, currently this is about 4GB data (takes forever to download). One of the problems is the HEC model data that for some reason is checked into the repository. Could we somehow remove these data files and possibly also review if some of the branches are outdated and can be removed.

Minutes:
Gena will create new my openMI open source version control repository force and and .......
Minutes:on source forge and move the HEC files to this repository

6.5 OpenMI workshop at the BAW

...

Adrian has on behalf of Wallingford Software submitted xml files for InfoWorks according the the OpenMI 1.4 standard. Formally, the OATC should review these files and make recommendations to the OAEC for accepting or rejecting the components as officially OpenMI compliant. The files are attached to this agenda: InfoWorks xml files

Minutes:
OATC decided to recommend that the submitted xml's are accepted

7. Tasks and unresolved issues

All tasks are handled by sourceForge. GOTO: OpenMI Tasks on source forge

...

to this agenda: InfoWorksXMLZipFile

Minutes:
OATC decided to recommend that the submitted xml's are accepted

7. Tasks and unresolved issues

All tasks are handled by sourceForge. GOTO: OpenMI Tasks on source forge

*8. Any other business

Plan from now until next meeting

Minutes:
* Insert the following into the trunk
** Spatial things (see page..). (to be finished) (finished before Wednesday next week)
** Manual merge the Gregersen3 branch into the trunk. (Jan and Stef via Skype, next week). It involves the standard and backbone.
** Add the IDictionary type for Arguments (used for IDecoratedOutputexchageItem)
** Implement SDK and GUI.