Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
scrollbar
Table of Contents

See also: OATC Wiki Home

...

Date: January 13-15,

...

2009
Venue: University of Trento and Riccardo Rigon, Italy (Location and hotel information for OATC meeting no 21)

...

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)
Andrea Antonello, Universita` di Trento, (andrea.antonello@gmail.com)
Peter Schade, Bundesanstalt fuer Wasserbau, Germany (Peter.Schade@BAW.DE)
Silvia Franceschi, Universita` di Trento, (silvia.franceshi@hydrologis.eu)

Apologies:

~onnoroosUnknown User (onnoroos), Alterra (Onno.Roosenschoon@wur.nl)
Peter Gijsbers, Deltares (Peter.Gijsbers@deltares.nl)
Rob Knapen, Alterra (Rob.Knapen@wur.nl)
Jon Goodall, Univ South Carolina (goodall@engr.sc.edu)
Lars Ekebjærg, DHI, (lce@dhigroup.com)

...

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

...

Table of contents

Table of Contents

Minutes

1. Minutes from previous OATC meeting

There were no comments to the minutes from last meeting

Include Page
2. Maintenance and support
2.

...

(GOTO bug list on SourceForge)

2.2 Help issues

(GOTO help issues on SourceForge).

2.3 Discussion issues

...

Maintenance and support

3. OpenMI 2.0 Issues

Include Page
3.1 Use cases

...

3.1 Use cases
Include Page
3.2 OpenMI 2.0 architecture
3.2 OpenMI 2.0 architecture
Include Page
3.3 Development and release road map
3.

...

3 Development and release road map
Include Page
OPENMI: 34. OpenMI Java and OpenMI .net synchronizationOPENMI: 3
4. OpenMI Java and OpenMI .net synchronization

The OpenMI 1.4 standard is released both for .net and Java. However, with respect to the supporting tools, documentation and application there are differences:

  • Documentation
    All available documents (e.g. the document A to E series) and the wiki getting started pages are written with the C# implementation in mind. Consequently, all UML's and code examples are targeting the C# implementation. The principles remain the same for the Java and the .Net implementation so the provided documentation can be used both for Java and C# developers, but with some inconveniences for the Java developers.
  • GUI configuration editor
    A OpenMI configuration editor is only available for OpenMI .Net compliant components.
  • SDK
    SDK are available both in Java and C#. However, it is not fully clear if everything is the same in the two implementations.
  • Distribution
    The OATC which is an official subcommittee under the OpenMI Association is releasing the C# source code and applications, whereas the Java SDK is provided by Alterra. The C# SDK can be downloaded directly from www.sf.net as a zip file, whereas the Java SDK only can be accessed through SVN on source forge. Rob has written a wiki page, which describes how to get the Java SDK and how to get started with developing OpenMI in Java.

Over the recent years there have been many discussions about to which extend a Java implementation of GUI and SDK should be provided by the OA (or OATC). The meeting concluded that ideally we should support Java and C# equally, which means that the OATC should provide the Java SDK and a Java based configuration editor also. However, since we do not currently have the resources to both develop the OpenMI version 2 and to extend our tasks with respect to Java development, we realize that for version 1.4.* the OATC can only work with the C# versions. We appreciate the work done by Alterra in providing Java implementations.

For version 2 we will try to find resources to support both Java and .Net equally with respect to the Standard, configuration editor, SDK and documentation

4. OATC Procedures

5. www.OpenMI.org and wiki.OpenMI.org

6. Miscellaneous issues

5. OATC Procedures

There were not changes to the OATC Procedures. However, there is still a task to review and update these.

6. www.OpenMI.org and wiki.OpenMI.org

6.1 The new wiki

It has been decided by the OAEC to move the contents of the www.openmi.org to a wiki hosted by Deltares. Jaco has already organized the fist steps, which involved setting up the new wiki space and installing various plug-ins. The task in now on Jan to move the content of the current wiki mirror to the new wiki space and subsequently work on the layout.

6.1 The OATC wiki

At the OATC meeting 19 we decided to review and update the how-to-pages on the wiki. The wiki pages were distributed between Adrian, Stef, and Jan. Jan has done his task, but pages assigned to Adrian and Stef still needs to be updated. A new deadline was set for this task: March 10th 2009. (see also source forge OpenMI tasks .

7. Miscellaneous issues

7

...

.1 OpenMI goes Linux

The following lines describe the development status of the linux portation of

  • the OpenMI environment
  • and an OpenMI compliant model.

67.1.1. Porting the OpenMI environment

  • the OpenMI standard v. 1.4.0,  ... done
  • the SDK v 1.4.1,  ... done
  • the commandline v  1.4.1,   ... done
  • configuration editor v 1.4.1 (Mono 2.0 needed), ... under construction

67.1.2. Porting the Fortran Code from Compaq to ifort on Windows

Generation of an ifort gei.win.dll and a main program and running the 31 test cases.    ... done

67.1.3.Porting the ifort Code from Windows to Linux

Linux ifort compilation of the BAW engine gei.xe.dll on a 64bit system.  ... done

67.1.4. Porting GEIWrapper to Linux

Portation of GEIWrapper (the C#-Wrapper around the engine gei.xe.dll) ... done

67.1.5. Porting WLDelftWrapper to Linux

Original strategy: It could be reasonable to port the OpenMI compliant WLDelftWrapper to Linux (Deltares). Alternatively, Deltares could offer a Linux engine and the information how to access it from a Windows WLDelftWrapper.
New: Meanwhile fast multicore pc cpus made a linux WLDelftWrapper less important for the BAW, see 6.1.7.

67.1.6. Test of a composition

  • composition with commandline in batch mode   ... done
  • generation of a composition in configuration editor    ... under construction

67.1.7. Test System

The BAW test system is a linux workstation with one Intel Xeon Dual Core Processor and SLED 10. We use the 64 bit instead of the planned 32 bit mode, since our workstations as well as our hpc cluster work in 64bit mode.

7.1.8 Merging the OpenMI Linux version into the 1.4.1 branch on source forge

Peter Schade

...

Adrian will create a list of thing to do with respect to merging the Linux version of the GUI into the 1.4 branch after the 1.4.1 is released. This list will be mailed to Peter, and Peter will subsequently take care that the Linux version is available on source forge.

Peter will put the Linux How-to-pages on the wiki.

7.2 The OpenMI SDK and configuration editor version 1.4.1 release

Adrian will provide an updated GUI install and the zipped version of the SDK. Any remarks should be provided by January 30th .

Release notes: Everyone send contribution to the release note (look to your own commits to SVN. Send to Adrian also before January 30th.

Adrian will make sure that there is a news item on www.openmi.org which announce the 1.4.1 release.

7.3 Demonstration of Delft Shell and JGrass

Gena and Andrea gave demonstrations of Delft Shell and JGrass, respectively.

8. Tasks and unresolved issues

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

...

9. Any other business

9.1 Meeting dates for the next OATC meeting

The next OATC meeting is extended with one day. This will allow us to more time to actual implementation during the meeting. So new date for the meeting is Monday March 9th to Thursday March 12th 2009 (see also OATC Calendar).