Ticket #812 (closed enhancement: fixed)

Opened 7 years ago

Last modified 6 years ago

prompt

Reported by: payoung2 Owned by: aivar
Priority: major Milestone:
Component: slim-plugin Severity: serious
Keywords: Cc:
Blocked By: Blocking:

Description

Hey Aivar! I'm working with SLIM Pluggin again because I plan to present it at the M&M meeting in August. I was wondering if you can make it take binning and cursor placement into account when you select "Use Current XY" as your IRF. Right now it doesn't appear to take cursors or binning into account at all. And after a discussion with Axel Bergmann from SPCImage, he recommends we bin up until we have ~10,000 peak counts for our IRF. So it would be good if we could bin and then use the cursors to select which part of the IRF data is good (and eliminate the noise at the end). THANKS!

Change History

comment:1 Changed 6 years ago by aivar

If you select a pixel to be the IRF the entire decay is saved, ignoring the current cursors. However then the window that pops up showing the IRF has a new set of cursors so you can chop off the start and end. So there are two sets of cursors involved currently. The initial position of the IRF cursor is estimated (using different criteria than the decay cursors) and can be tweaked afterward.

This current scheme is basically the same as in TRI2. It seems very flexible that you can tweak the IRF cursor independently you don't specify these one-time as you save the IRF. Of course cursor placement remains one of the most mysterious elements of SLIM Plugin usage, so perhaps we can improve on this.

Binning the IRF sounds like a great idea.

comment:2 Changed 6 years ago by aivar

Just checked TRI2 and it does indeed bin the IRF data as you need.

comment:3 Changed 6 years ago by aivar

  • Component changed from other to slim-plugin

comment:4 Changed 6 years ago by aivar

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.