Ticket #2274 (closed: fixed)

Opened 10 years ago

Last modified 5 years ago

IdentifyNoisyDetectors algorithm [TOSCA Requirement]

Reported by: Michael Whitty Owned by: Michael Whitty
Priority: major Milestone: Iteration 27
Component: Mantid Keywords:
Cc: Blocked By:
Blocking: Tester: Owen Arnold

Description

For support of the TOSCA instrument, TRC requires a method to identify which detectors are "bad" in the raw file.

Looking at the current selection of similar sounding algorithms we have, it would appear we do not have anything that is of the same spirit as what Timmy used within OpenGENIE.

Create an algorithm that takes a TOF workspace and outputs a masking workspace (1s & 0s) stating which detectors are to be considered "no good".

Decision based on whether the integrated value over a specified range is within 3 * std deviation of the mean. This should prune out the "empties" and the detectors in the instrument that are just noise.

Repeat the process a couple of times so that the mean is recalculated when the largest differences have been sacked off.

Change History

comment:1 Changed 10 years ago by Michael Whitty

  • Status changed from new to accepted

comment:2 Changed 10 years ago by Michael Whitty

(In [8934]) refs #2274 - algorithm for determining which detectors are dud in TOSCA

comment:3 Changed 10 years ago by Michael Whitty

  • Status changed from accepted to verify
  • Resolution set to fixed

algorithm & test are there and working. getting the same results as in OpenGENIE.

comment:4 Changed 10 years ago by Owen Arnold

  • Status changed from verify to verifying
  • Tester set to Owen Arnold

comment:5 Changed 10 years ago by Owen Arnold

  • Status changed from verifying to closed

comment:6 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​3121

Note: See TracTickets for help on using tickets.