The OpenMI documentation

(warning) Please notice:
The previous version of the OpenMI was associated with a series of documents (documents A to E). With the OpenMI 1.4.0.0 release documentation is provided online through this web site. However, the previous set of documents contains useful information that at this time is not available directly on the web site. Therefore, direct access to these documents is provided below. Please be aware that some information provided in these documents may not be totally updated to the 1.4.0.0 version.

All aspects of the project are documented in the OpenMI report series, comprising the following titles:

  • Scope
    Describes the scope of the OpenMI architecture and the organisation behind it.
    Open document

  • The OpenMI Guidelines
    Describes how to migrate, link and run OpenMI-compliant models. The document includes sample code and tutorial examples.
    Open document

  • OpenMI.Standard interface specification (C)
    Describes the interface specification of the org.OpenMI.Standard namespace (the OpenMI standard interface specification). The specification is expressed in Universal Modelling Language (UML) and in API-terms. This specification has to be adopted for a model to become OpenMI-compliant.
    Open document

  • OATC.OpenMI.Backbone technical documentation
    Describes the default implementation (i.e. the classes that implement the org.OpenMI.Standard interface). This implementation is the basis of the OpenMI environment.
    Open document

  • OATC.OpenMI.Development Support technical documentation
    Describes a generic set of low-level classes that can be used in the development of an OpenMI system.
    Open document

  • OATC.OpenMI.SDK technical documentation
    Describes the org.OpenMI.Utilities namespace, which contains useful low-level classes and packages that have been tailored to help with the development of OpenMI-compliant systems. Their use is entirely optional and is not a requirement of compliance. Typically, the classes within this namespace have been developed to reduce the amount of re-engineering needed when migrating existing model engines and software systems to become OpenMI-compliant. In particular, the utilities provide facilities to support the wrapping of legacy code. The namespace contains packages for wrapping, buffering, spatial mapping, advanced control features, configuration and deployment.
    Open document

Other documents:

Links:

  • No labels

Disclaimer