...
- 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?
- Discuss component operation mode here comment from Peter Gijsbers need to be discussed
- When we get loops in the compositions - we have to tell which component will be first! In the new GUI, we will let the user indicate the 'Start up component'.
- Discussion/Conclusion:
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.
- The Timezone issue has been re-adressed. The .Net TimeZone does not provide what we need, while the TimeZoneInfo is only available in 3.5, and therefore will not run on MONO.
Discussion/Conclusion led to the following decisions:- Daylight Saving Time jumps in time series are not allowed
- The TimeSet will contain a property that expresses its offset from UTC, expressed in hours (see below). The Gui will check these offsets, and if they are different, it will ask the user to put a decorator in between.
...