Changes between Version 8 and Version 9 of Java API
- Timestamp:
- 10/16/12 15:16:18 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Java API
v8 v9 12 12 * terminal, for terminating empty conduits. 13 13 14 These elements are all supported in the MUSCLE API. Of these elements, only submodels have the explicit concept of scale. In MUSCLE this is mapped to one temporal scale and multiple spatial scales. The temporal scale is used to determine the simulation time at the current iteration, see the [[C xA Documentation|configuration documentation]] on how to set the scales. Conduits and parameters are used the same in MML-based or free-form code.14 These elements are all supported in the MUSCLE API. Of these elements, only submodels have the explicit concept of scale. In MUSCLE this is mapped to one temporal scale and multiple spatial scales. The temporal scale is used to determine the simulation time at the current iteration, see the [[Configuration|configuration documentation]] on how to set the scales. Conduits and parameters are used the same in MML-based or free-form code. 15 15 16 16 === Conduits === … … 18 18 The conduit is the mechanism in the MUSCLE runtime environment to send data. In the API, the {{{ConduitEntrance}}} and {{{ConduitExit}}} are accessible. The {{{ConduitEntrance}}} is used to send data, while the {{{ConduitExit}}} receives data. These entrances and exits, as we call them, can be accessed in two ways. Either they are created in the {{{addPortals()}}} method, or they are called on the fly in the code using the {{{out()}}} and {{{in()}}} methods. 19 19 20 The [doxygen: muscle_java_api/addPortals] {{{addPortals()}}} method is called before the submodel starts, so the exits and entrances are stored as fields of your class. The conduit exit and entrance uses Java Generics to define what kind of data will be received or sent, both in the field declaration and in the addExit or addEntrance method. This allows for compile-time and run-time checking of data that is sent over the conduit.20 The [doxygen:addPortals] {{{addPortals()}}} method is called before the submodel starts, so the exits and entrances are stored as fields of your class. The conduit exit and entrance uses Java Generics to define what kind of data will be received or sent, both in the field declaration and in the addExit or addEntrance method. This allows for compile-time and run-time checking of data that is sent over the conduit. 21 21 {{{ 22 22 ConduitExit<double[]> exitA;