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

Compare with Current View Page History

« Previous Version 12 Next »

See also: OATC Wiki Home

(warning) Minues are under construction, expected to be completed January 22(warning)

Date: January 13-15, 2008
Venue: University of Trento and Riccardo Rigon, Italy (Location and hotel information for OATC meeting no 21)
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)
Andrea Antonello, Universita` di Trento, (andrea.antonello@gmail.com)
Peter Schade, Bundesanstalt fuer Wasserbau, Germany (Peter.Schade@BAW.DE)

Apologies:

~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)

Documents:

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

Agenda

1. Minutes from previous OATC meeting

2. Maintenance and support

2.1 Reported bugs

(GOTO bug list on SourceForge)

2.2 Help issues

(GOTO help issues on SourceForge).

2.3 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.3 Development and release road map

3. OpenMI Java and OpenMI .net synchronization

Unable to render {include} The included page could not be found.

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

6.1 OpenMI goes Linux

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

  • the OpenMI environment
  • and an OpenMI compliant model.

6.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

6.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

6.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

6.1.4. Porting GEIWrapper to Linux

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

6.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.

6.1.6. Test of a composition

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

6.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.

Peter Schade

7. Tasks and unresolved issues

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

8. Any other business

  • No labels

Disclaimer