...
Adrian Harper, Wallingford Software (adrian.harper@wallingfordsoftware.com)
Stef Hummel, Deltares (stef.hummel@deltares.nl)
Jesper Grooss, DHI (jgr@dhigroup.com)
Standa Vanecek, DHI (s.vanecek@dhi.cz)
Peter Schade, Bundesanstalt fuer Wasserbau (peter.schade(at)baw.de)
Apologies:
Rob Knapen, Alterra, Wageningen UR (Rob.Knapen@wur.nl)
Standa Vanecek, DHI (s.vanecek@dhi.cz)
~don Unknown User (don), Deltares (gennadii.donchyts@deltares.nl)
Peter Schade, Bundesanstalt fuer Wasserbau (peter.schade(at)baw.de)
Apologies:
)
1 Informations from the OAEC meeting (Standa)
1.1 Official paper
Some document, describing steps we did for the version a statement, than OATC is happy with the status of Version 2 is required. Content we will be obtained soon.
Up to this moment version is temporaly accepted.
1.2 Release
Not fully clear yet when the formal release for public is planned. At least during the Washington meeting (7-9.12 2010).
We will obtain info how the release process will be done
Proper decimination + publicity will be handled by OAEC and OADC.
1.3 Actions to SVN Repository and web sites before release
SVN Repository
The following actions have to be taken:
Everone: remove depricated branches
- Stef/Jesper: check SDK (See ch. 5)
- Stef: Create tags fixing C# and java release version of the Standard
Web sites
Standa: arrange wiki, i.e.:
- remove Dashboard > OpenMI 2.0 doc
- rename Review page to OpenMI 2.0 page
- etc. (adjust related texts)
Peter: make proposal for openmi.org site (news, button, etc., referring to the wiki).
2
...
. Roadmap to OpenMI 2.0 as suggested by Standa
...
2.1. Documentation
Updating of the Documentation
document | comment | task for | status | |
---|---|---|---|---|
What's new in OpenMI 2.0 |
| SH | Todo Done: remove loop-approach text | |
OpenMI 'in a nutshell |
| ADH | Still Valid | |
Scope document |
| all | Still Valid | |
Incorporate text on Standard Extensions in OpenMI Standard2 interface specification |
| SH | PS | Done (SH): Peter will review it todo: Incorporate text on Standard Extensions |
OpenMI Standard2 Reference manual | when source code will be stabilized | SV | - | |
Migrating models |
| SV/JGr | will check if still valid Will clean up the document and check it (JGr>SV>JGr>Steve) |
maybe change the names for OpenMI Standard2 interface specification and OpenMI Standard2 Reference manual
...
2.2. How to
page | comment | task for | status |
---|---|---|---|
How to download the most recent source code | no changes??? | JG | |
How to get started with OpenMI 2.x and Java | no changes??? | no changes, | - |
How to link models with different grids (spatial mapping) | small changes | Peter (starting nov. 12th) | - |
How to turn an ASCII file reader into a Linkable Component 2.0 | source code for latest version exist. Changes reflecting Time extensions | JG | |
How to upgrade from version 1.4 IEngine | Did it work now? Will be included to the official release? | (JG)/SH | OK, SH will just to be sure check when migrating Sobek Upgrading from 1.4 using the upwards compatible wrapper Did it work now? Will be included to the official release? |
– or put it to the pages later?
...
| -
...
| To be released after more experience |
time-dependent / time-independent mixing | how to mix time-dependent and time-ignorant model components | - | - |
(Jesper): Assuming the most recent HowTo pages are those on http://public.deltares.nl/display/OMI20DOC/Home - correct?
(Peter): The official review pages http://public.deltares.nl/display/OPENMI/OpenMI+Association+Technical+Committee -> OpenMI 2.0 Review -> "Content of the review" are more uptodate, at least the spatial mapping page.
1.3. SDK
Work is being done on the SDK, following the work of migrating existing engines.
2. Various issues
2.1. Final agreement on the extensions
No feedback from OAEC and OADC. The Standard just has be released as soon as possible.
Proper definition of how to use them and what it means for OpenMI-compliancy has been written (see action above).
2.3. Mixing time-dependent and time-independent components
...
Will be done later (not needed before releasing 2.0) |
3. Remaining issues from
...
previous meetings
Issue | Description | status | decision |
---|---|---|---|
OpenMI XSD files | The component and compliancy XSD files still are based on 1.4. Must be extended. | Done by: Rob/Stef | to be approved by Team |
Move interfaces to TimeSpace extension | ISpatialDefinition, IElementSet, ITime, ITimeSet could be moved from the base to the TimeSpace extension Done by: Jesper(C#)/Rob(Java) | Ok | |
Update copyright notice | Add year 2010 to the OpenMI copyright header in all source files | Java updates done: Rob. | Update SDK headers |
Distribution package | Distribute base and timespace extension in a single package or as two? | | Keep as 1 package |
Merge IValueDefinition and IDictionaryItem | IValueDefinition is an abstract entity, IDictionaryItem is just one of the available specializations, next to the quantity and the quality. Of course the IDictionary item incorporates part of the element set and time set definition, but this overlap is acceptable | Closed | keep IDictionaryItem as extension of IValueDefinition |
Rename IManageStateExtension | IManageStateExtension should be renamed back to IManageState, to emphasize that it is an optional interface to the base standard | SH(C#)/RK(Java: Done) | - |
Adapted output factorty providers | Check Specification document and code comments on the limitation of only asking the adaptee's component for adapted output factorties | action: SH | - |
<new issue> | <description> | <status: open> | |
- Release of the 2.0 Beta: Also notify people who participate in the review process about the new version and changes made according to their input.
5. SDK
Work is being done on the SDK, following the work of migrating existing engines.
Status:
- Issue with ElementMapper and memory has been fixed (transferring 1.4
...
- Perform steps to really release (will be described by SV).
- solution to 2.0)
- A number of bugs has been fixed (time buffer, some adaptors)
- The groundwater model and simple river model has been updated for more advanced (bidirectional) coupling
- Example and test of coupling the groundwater model and the simple river model, in as well a uni- as a bi-directional setup (ground water level -> river, and river leakage -> ground water model).
- Example of how one input can handle multiple outputs are implemented/tested. Check out: https://sourceforge.net/apps/trac/openmi/wiki/MultiInputSupport
Everyone: have a look at the MultiInputSupport in the next two weeks.
A project plan is probably required in the near future (when the standard is released), in order to have the SDK move in a proper direction.
Jesper and Stef will look at the SDK, clarify things were possible, and report what in their opinion still has to be done (next two weeks)
6
...
. Project management tool
Suggestion: Use the Trac wiki at sourceforge to keep track of tasks, feature requests, bugs, enhancements etc. and also discussions that covers many meetings.
Check out:
https://sourceforge.net/apps/trac/openmi/
...
/
You need to log in (using your source-forge username/password) in order to get full access (to edit wiki/create tickets)
7. Next Meeting
Skype session: 18th, most probably 9am