(30) Any input arriving after the input time becomes available at the next input time. This may be the input time for the next dispatch, or the next input time in the same dispatch, if multiple input time values are specified.
-> clarify the notion of next input time.
(33) Arrival of events on event ports can also trigger a mode switch if the event port is named in a mode transition originating in the current mode (see Section 12). Events that trigger mode transitions are not queued at event ports.
=> should we consider mode-triggering ports differently from other ports?
i.e. cannot be part of a dispatch trigger, not subject to freezing rules, etc but instead only be considered by the RTS itself for reconfiguring the system?
Generally speaking, reorganize text to follow a natural order of definitions. E.g. (34) and (35) both mention how data port are handling data streams.
jjhugues
commented
3 years ago
9.2.4 introduces port communication timing.
(30) Any input arriving after the input time becomes available at the next input time. This may be the input time for the next dispatch, or the next input time in the same dispatch, if multiple input time values are specified.
-> clarify the notion of next input time.
(33) Arrival of events on event ports can also trigger a mode switch if the event port is named in a mode transition originating in the current mode (see Section 12). Events that trigger mode transitions are not queued at event ports.
=> should we consider mode-triggering ports differently from other ports? i.e. cannot be part of a dispatch trigger, not subject to freezing rules, etc but instead only be considered by the RTS itself for reconfiguring the system?
Generally speaking, reorganize text to follow a natural order of definitions. E.g. (34) and (35) both mention how data port are handling data streams.