| scrollbar |
|---|
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
...
IlinkableComponent.Initialize(IArgument[] arguments)will be changed toIlinkableComponent.Initialize()
Gena:
IOutputItem.Consumers and IOutputItem.Decorators
...
base class | derived class | factoryname | remarks |
|---|---|---|---|
IOutput | IDerivedOutput | IDerivedOutputFactory | methods in the factory need to be renamed as well |
IOutput | IAdaptedOutput | IAdaptedOutputFactory | Rename methods and properties, e.g. use "adaptee" |
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).
...
During this week, the Java version of the standard has to be implemented and documented.
Rob: After this has been implemented we need to agree on a way to keep both (C# and Java version of the Standard) updated in sync, including source code comments.
Utilities/GUI
We will currently put no effort in addinonal java developments, like the backbone, the GUI etc. Most probaby, there will be no time left in the OpenMI-Life project (ending end of Januari) to put any real effor to java.
However, next to having the standard, we will take to:
...
First iteration of the Java version has been completed and made available on SourceForge in the /trunk/src/java/OpenMI.Standard folder. There is a ./bin folder with the compiled jar library of the Standard interfaces, a ./javadoc folder with the source code documentation in HTML format, and the ./src folder with the Java source code. In this folder you also should find the changes.txt file that briefly lists the things I have modified compared to the C# version of the Standard that I based the Java implementation on. I used the C# source code from SourceForge, versions of November 9. Modifications mostly reflect latest things discussed in this TC meeting, programming language differences, and rewritten source code comments.
Now that this work been completed we need to agree on a way to keep both (C# and Java version of the Standard) updated in sync.
Utilities/GUI
We will currently put no effort in addinonal java developments, like the backbone, the GUI etc. Most probaby, there will be no time left in the OpenMI-Life project (ending end of Januari) to put any real effor to java.
However, next to having the standard, we will take to:
- 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 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 :
...
subject | status | page-author | page-reviewer |
|---|---|---|---|
How to generate a XML file describing compliancy with OpenMI 2.0 | todo first version | Peter | Stef |
How to migrate from version 1.4 IEngine | first version | Jesper | Adrian |
How to work with OMI files | first version | Peter | Adrian |
How to link OpenMI components via hardcoded interface calls | first version (see note 1) | all | Standa |
How to turn an Ascii file reader into a Linkable Component | first version | Jesper | Stef |
How to connect to GIS | first version | Standa | Stef |
How to turn a database into a LinkableComponent | first version | Jesper | Stef |
How to link models with different grids (spatial mapping) | to adjust | Stef | Jesper |
How to download the most recent source code | reviewed | Peter | Standa |
How to get started with OpenMI and Java | skeleton exists first version | Peter | Rob |
How to migrate existing Fortran based models codes | todo (see note 2) | Stef | Adrian |
How to generate a LinkableComponent with a Fortran engine on Linux | todo (see note 3) | Peter | Gena |
How to port the OpenMI from Windows to Linux | todo | Peter | Gena |
...
Whole structure of the source code, examples, unitest... were reorganised (not used files deleted...) to provide clear based for the Version 2.0.
Gena will and more details there + prepare the document describing new projects structure
4 Support for Version 2.0 reviewing
...
- Wiki
- Downloads
- Reviewer registration
- Voting system ??? _
Gena will prepare sugestion for the structure
...
All came with the ideas
...
When 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.