View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003749 | 10000-009: Alarms and Conditions | Spec | public | 2017-02-16 15:42 | 2017-03-22 10:28 |
| Reporter | Paul Hunkar | Assigned To | Paul Hunkar | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | 1.03 | ||||
| Summary | 0003749: Limit alarms and arrays | ||||
| Description | What should the behaviour of a limit alarm be if the source variable is an array? The specification should provide discuss this. | ||||
| Tags | No tags attached. | ||||
| Commit Version | |||||
| Fix Due Date | |||||
|
|
This issue was raised in the forum |
|
|
added text that the input to a limit alarm shall be a scalar. If a limit alarm is to be defined for an array, a subtype of the limit alarm should be created that describes the expect behaviour. Option could include, all element of array over limit, any eleemtn over limit, limits must also be arrays, alarm if any of array limits exceeded by coresponding source array element. |
|
|
Agreed to changes edited in Salzburg meeting. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2017-02-16 15:42 | Paul Hunkar | New Issue | |
| 2017-02-16 15:42 | Paul Hunkar | Status | new => assigned |
| 2017-02-16 15:42 | Paul Hunkar | Assigned To | => Paul Hunkar |
| 2017-02-16 15:43 | Paul Hunkar | Note Added: 0007888 | |
| 2017-02-16 15:48 | Paul Hunkar | Note Added: 0007889 | |
| 2017-02-16 15:48 | Paul Hunkar | Status | assigned => resolved |
| 2017-02-16 15:48 | Paul Hunkar | Fixed in Version | => 1.04 |
| 2017-02-16 15:48 | Paul Hunkar | Resolution | open => fixed |
| 2017-03-22 10:28 | Jim Luth | Note Added: 0007946 | |
| 2017-03-22 10:28 | Jim Luth | Status | resolved => closed |
