Ticket #942 (closed: fixed)

Opened 11 years ago

Last modified 5 years ago

Find how to use Mantid tools to find monitor peaks

Reported by: Steve Williams Owned by: Steve Williams
Priority: major Milestone: Iteration 21
Component: Keywords: Excitations, corrections, detectors, monitors
Cc: Blocked By:
Blocking: Tester:

Description

The peaks can be small and asymetric but it is important to accurately measure where the peaks oocur. First find the TOF window where the peak must be, then use a peak finding algorithm and perhaps then do an Ikeda Carpenter fit.

In Mari the peaks can be found in spectra 2 and 4 in Maps it's 41474 and 41475

Toby Perring has written an algorith to do this which we can use where existing tools fail.

It is an error if the peak is more than 4% away from where it is expected and it must be at least 4 bins wide.

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 [3494]) Added more tests to the getEi algorithm and stopped another Linux crash refs #942

comment:3 Changed 11 years ago by Steve Williams

  • Status changed from assigned to accepted

The Jon Taylor of from the Excitations Group have supplied us with four test cases and the answers are within his tolerance for three of those. In run MAR15306 Mantid gives a different result but Jon Taylor said he is happy with it becuase the engery gives a good units conversion to deltaE (their (HOMER) energy doesn't).

MANTID (meV) HOMER (meV) Run number 12.9448 12.973 meV MAR11001 included in unit tests 6.82198 6.518 meV MAR15306 included in unit tests 717.9795 718.716 meV MAR15317 included in unit tests 97.3475 97.140meV MAR15297

comment:4 Changed 11 years ago by Steve Williams

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

(In [3533]) After feedback on getEi from Jon Taylor improved the documentation and opened up the peak search window closes #942

comment:5 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 1790

Note: See TracTickets for help on using tickets.