Ticket #840 (closed: fixed)

Opened 11 years ago

Last modified 5 years ago

Add feedback from DIAG gui

Reported by: Nick Draper Owned by: Steve Williams
Priority: major Milestone: Iteration 19
Component: Keywords:
Cc: Blocked By:
Blocking: Tester:

Description

Each step should tell the user how many spectra were considered for masking, allow the user to list the detector ids, and display them on the instrument view.

Change History

comment:1 Changed 11 years ago by Steve Williams

  • Status changed from new to assigned

comment:2 Changed 11 years ago by Steve Williams

(In [3182]) A new GUI for running diagnostic tests that find also over-reading, under-reading and fading-out and dead detectors refs #840

comment:3 Changed 11 years ago by Steve Williams

  • Status changed from assigned to closed
  • Resolution set to fixed

comment:4 Changed 11 years ago by Steve Williams

  • Status changed from closed to reopened
  • Resolution fixed deleted

comment:5 Changed 11 years ago by Steve Williams

(In [3185]) Giving the diagnostics interface a sensible name and stopping some crashes refs #840

comment:6 Changed 11 years ago by Nick Draper

  • Milestone changed from Iteration 19 to Iteration 20

Moved as part of the end of Iteration 19

comment:7 Changed 11 years ago by Steve Williams

(In [3189]) Small change to the error reporting by the diagnostic test UI and satisfied jon.taylor@… request for user definition of good and bad values in MedianDetectorTest and DetectorEfficiencyVariation refs #840

comment:8 Changed 11 years ago by Nick Draper

  • Status changed from reopened to closed
  • Resolution set to fixed
  • Milestone changed from Iteration 20 to Iteration 19

comment:9 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​1688

Note: See TracTickets for help on using tickets.