Summary
An end user, for example an EU policy expert, looking at results calculated by a chain of models for different policy scenarios requires information about the uncertainty of the data. This uncertainty is some kind of "total" of the measurements and models used in the model chain. The uncertainty information is essential to the end user for evaluating the results.
How to address in Version 1
I don't think OpenMI 1.0 provides any mechanisms for indicating data uncertainty and how it affects the end results of linked models. Guess it is up to the person using the system to decide.
Drawbacks
List all possible problems that you may expect in version 1.x of OpenMI.
How to address in Version 2
Present ideas in any form how you'd expect it to work in the OpenMI 2.0
| scrollbar |
|---|
h2. Summary
{graphviz}
digraph flow {
rankdir=LR;
node [shape = rect]
"Component 1" -> "Component 2"
}
{graphviz}
_See documentation for graph language [here|http://www.graphviz.org/Documentation/dotguide.pdf]._
_Describe components and all data types which should be connected. Try to avoid use of OpenMI-specific terms like ExchangeItem, ElementSet ets. if they are not used in a context of your application._
_Explain typical scenario with all steps required to run all these components together._
_Describe data flows data structures involved at configuration and run-time._
h2. How to address in Version 1
_Describe how you'd approach above mentioned use case in terms of OpenMI 1.0. Example source code can be listed using \{code\} macro._
h3. Drawbacks
_List all possible problems that you may expect in version 1.x of OpenMI._
h2. How to address in Version 2
_Present ideas in any form how you'd expect it to work in the OpenMI 2.0_
|
|---|
|