You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 21 Next »

Date: April 14-16, 2008

Venue: Deltares, Rotterdamseweg 185, 2629 HD Delft, The Netherlands

Participants:
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 (Gena), Deltares (gennadii.donchyts@deltares.nl)
Peter Gijsbers, Deltares (Peter.Gijsbers@deltares.nl)
~onnoroos, Alterra (Onno.Roosenschoon@wur.nl)
Rob Knapen, Alterra (Rob.Knapen@wur.nl) (only on Monday)
Peter Schade, Bundesanstalt fuer Wasserbau, Germany (Peter.Schade@BAW.DE)

Apologies:

Jon Goodall, Univ South Carolina (goodall@engr.sc.edu)
~psi@dhigroup.com, DHI - Water & Environment (psi@dhigroup.com)

Objective:
OpenMI version 2.0

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

Agenda

1. Maintenance and support

2. OpenMI 2.0 Issues

2.1 Development model

Review the iterative development plan (Goto Plan)

Please also read "March 2006, OpenMI 2.0 by Brinkman, Hummel, and Gijsbers"

2.2 Use cases

GOTO use cases

2.3 OpenMI 2.0 architecture

Quality versus Quantity

We tried to remind ourselves about the outcome of previous discussions about quality, quantity, and chatagorized data.
The figue below shows the Interfaces we wanted to be inplemented.

Rob Knapen, will implement this in these interfaces as an extension to the OpenMI 1.4 Java SDK.

2.4 Development and release roadmap

3. OpenMI Java and OpenMI .net synchronization

Rob will follow up on the progress of JGrass, and report back to the OATC

Rob will upload the OpenMI 1.4 Java SDK, developed by Alterra to a directory under the MyOpenSource on SourceForge (create new subdirectory called Alterra).

4. OATC Procedures

Review and update the OATC procedures (GOTO OATC procedures)

5. OpenMI WIKI

6. www.OpenMI.org

7. Miscellaneous issues

7.1 OpenMI and Linux (Peter Schade)

    • short overview, why BAW is interested in linux
    • OpenMI (C#) standard has to be ported, which OpenMI version is suitable for Mono?
    • the C# wrappers have to be ported
    • the Fortran engines have to be ported, which compiler, ifort or Compaq Digital?
    • accessing the Fortran dll from C#

See OpenMIGoesLinux_200804.pdf presentation from BAW.

7.2 SourceForge version control

We need to decide how to handle the version control on source forge. Should version 2 be developed as the trunk and version 1.4.1 a branch? Whatever we decide should be described in a OATC procedure.

8. Tasks and unresolved issues

 All tasks and unresolved issues are managed via the sourceForge server: (GOTO OpenMI tasks on SourceForge)

9. Any other business

  • No labels