Source: NASA ( Kevin Rice)
RangeForm now appears in Static, Change and the multi band. It's not clear these all make sense to me.
In the static ranges – having the red be the most severe inner band and green "good" on the outside does make sense although I get the impression the use cases are less in number than the standard way folks think of limits. (you're going too fast! not – you're not going fast enough!)
In the change alarm, which I think of mainly as deltas – again intuitively checking for big changes make sense. Unwanted big jumps are intuitive. But unwanted little jumps? That is big jumps are good? Is there a real use case – perhaps we can jam it into the annotation.
Finally for the multirange alarm. The rangeForm is at each band. I suspect but don't know that this was to change the range set meaning...
Intuitively "inside" would be something like this: [min, max] – where x is between them is "ok" ...
And "outside" would be (-inf, min] and [max, inf) ... that is ranges point 'away'...
But maybe not – who knows!? Given that though the default is "outside" when perhaps most would want it to be "inside" etc...
I just wonder if we have done this correctly or its slipped through and is overly general because we inherited the various types, etc...
Reported: XTCE 1.2 — Thu, 3 Oct 2019 14:46 GMT
Updated: Wed, 9 Oct 2019 10:51 GMT
XTCE13 — Is rangeForm specialization needed for Change and Multi band alarms?
- Key: XTCE13-74
- OMG Task Force: XML Telemetric & Command Exchange Format 1.3 (XTCE) RTF