...
maybe change the names for OpenMI Standard2 interface specification and OpenMI Standard2 Reference manual
Add text from "Explanation of OpenMI Standard Extensions" to some other document - or change its format to follow style of the other documents (Peter: I would integrate the explanations into the interface specifications as the central document).
1.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, will just to be sure when migrating Sobek |
Upgrading from 1.4 using the upwards compatible wrapper | Did it work now? Will be included to the official release? | - | To be released after more experience |
time-dependent / time-independent mixing | how to mix time-dependent and time-ignorant model components | - | - |
1.3. SDK
We will leave SDK like it is just now. New documentation will not be created.
There are memory problems with large element sets.
Not to long from Jesper will copy the 1.4. fix for this into the 2.0 SDK.
2. Various issues
2.1. Final agreement on the extensions
- not clear if OAEC agrees with it or not.
- proper 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 . Also when mixing OpenMI endorsed and 3rd party extensions.has been written (see action above).
2.3. Mixing time-dependent and time-independent components
- Clarify what should happen when time-dependent and time-independent model components are mixed in a model chain. Is there enough "contextual" information available for processing?
Has been discussed and solved. 
Yet to be documented, however This was discussed at the previous meeting, and was solved by wrapping the "ignorant" component in a component that knows about time / space.
To illustrate it, someone will create a how to, with a statistical component (min/max/avg etc.) as example. See status of the How To pages.
3. Remaining issues from meeting no 33/34
...