Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Binning IRF #21

Open
grislis opened this issue Dec 6, 2013 · 0 comments

Comments

@grislis
Copy link
Contributor

commented Dec 6, 2013

"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)." Pam Young

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.

TRI2 does indeed bin the IRF data as you need.

The IJ2 version incorporates IRF binning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
1 participant
You can’t perform that action at this time.