Ticket #3358 (reopened)
Correct handling of Zeros
Reported by: | Owen Arnold | Owned by: | Owen Arnold |
---|---|---|---|
Priority: | major | Milestone: | Backlog |
Component: | GUI | Keywords: | |
Cc: | Blocked By: | ||
Blocking: | Tester: |
Description
Can have zero's as in no signal recorded, or zero as in no detector at that location. Should be possible to distinguish between the two via the API.
Change History
comment:2 Changed 9 years ago by Nick Draper
- Milestone changed from Iteration 32 to Iteration 33
Moved to iteration 33 at iteration 32 code freeze
comment:3 Changed 9 years ago by Owen Arnold
- Status changed from new to verify
- Resolution set to invalid
comment:4 Changed 8 years ago by Nick Draper
- Status changed from verify to reopened
- Resolution invalid deleted
Hmm,
I'm not really sure we have resolved this yet. Let me know if I've missed something.
comment:5 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.1 to Release 2.2
Moved at end of release 2.1
comment:6 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.2 to Release 2.3
Moved at the end of release 2.2
comment:7 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.3 to Release 2.4
Moved to release 2.4
comment:8 Changed 8 years ago by Nick Draper
- Milestone changed from Release 2.4 to Release 2.5
Moved at the code freeze for release 2.4
comment:11 Changed 7 years ago by Nick Draper
- Milestone changed from Release 2.6 to Backlog
Moved to the Backlog after the code freeze for R2.6
comment:12 Changed 7 years ago by Nick Draper
- Milestone changed from Backlog to Release 3.0
moved to Release 3.0 as these all seem to be active
comment:13 Changed 7 years ago by Nick Draper
- Milestone changed from Release 3.0 to Backlog
Moved out to backlog as not enough time in R3.0
comment:14 Changed 5 years ago by Stuart Campbell
This ticket has been transferred to github issue 4205
Note: See
TracTickets for help on using
tickets.
Bulk move of tickets to iteration 31 at the iteration 30 code freeze