Ticket #696 (closed: fixed)

Opened 11 years ago

Last modified 5 years ago

Further work on Peak finding and integration with peak fitting

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

Description (last modified by Nick Draper) (diff)

As part of this ticket the number of peak finding routines should be reduced. See #470

Change History

comment:1 Changed 11 years ago by Nick Draper

  • Milestone changed from Iteration 18 to Iteration 19

Moved as part of iteration 18 end

comment:2 Changed 11 years ago by Russell Taylor

(In [3020]) Widen range over which candidate peaks are fitted in FindPeaks. Re #696.

comment:3 Changed 11 years ago by Russell Taylor

(In [3021]) Fix test. Re #696.

comment:4 Changed 11 years ago by Nick Draper

  • Description modified (diff)

comment:5 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:6 Changed 11 years ago by Russell Taylor

(In [3196]) Improve the fitting of the background in FindPeaks. Re #696.

comment:7 Changed 11 years ago by Nick Draper

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

From Aziz:

Stripeaks: ALL FINE for HRPD! Hi, I guess everything works fine the peak backgrounds are all better fit for all peaks with the automated procedure. There are area for improvements (tiny peaks not found) but for me, I believe that’s USABLE as such. Thanks a lot, Aziz

comment:8 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue ​1544

Note: See TracTickets for help on using tickets.