Versions Compared

Old Version 77

changes.mady.by.user Unknown User (don)

Saved on

compared with

New Version 78

changes.mady.by.user Stef Hummel

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Are we happy with IOutputItem.IsAvailable() and with ILinkableComponent.Validate(), or do we need additional methods on LinkableComponent and/or ExchangeItem to check validity.
    Conclusion after a first discussion: we are happy. The only small change that has been proposed and has been agreed on is:
    (thumbs up) The return value will be an array of strings, to let the component compose a multi line message.
    Some second thoughts came up when Gena emphasized that by this mechanism the outer world can not determine which input/output exchange items are in erroneous state, and that a component is not able provide messages during initialization.

(question) To be rediscussed at this meeting (Thursday morning).

  1. Should we introduce a boolean argument that indicates whether the component should run in a pull mode (like in OpenMI 1.4) or in loop mode?
  2. Discuss component operation mode here comment from Peter Gijsbers need to be discussed
    Discussion/Conclusion: (thumbs up) We decided to let the LinkableComponent have a propery: CascadingUpdateCallsDisabled.
    The default is false, indicating that the component is running in Pull Driven mode (there will be a cascade of update() calls. This Pull Driven mode has to be supported by every component.
    If set to true, the component is expected to run Update()-step by Update-Step(), controlled by some outer world (which may be another component). If the component does not support this Update() by Update() way of running, it will throw an Exception when CascadingUpdateCallsDisabled= true is called.
    In the GUI, the user hat to tell which component is at the end of the chain. This controlling component will be triggered first.
  1. The Timezone issue has been re-adressed.
    Discussion/Conclusion led to the following decisions (warning) (thumbs up):
    1. Daylight Saving Time jumps in time series are not allowed
    2. The TimeSet will contain a property that expresses its offset from UTC, expressed in hours (OffsetFromUtcInHours). The Gui will check these offsets, and if they are different, it will ask the user to put a decorator in between.
      Note: in future and/or more platform specific versions of the standard we may reconsider introducing the timezone info again.

...