-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add calc_spoiler_impact function and use instead of box filter for acq #165
Conversation
The basic idea is the same as for guide, details slightly different. |
Interesting. I had played with using the fm centroid, but didn't have this idea of using a mean high background estimate. There are the couple of edge cases that I think of wrt to this approach... that multiple spoilers can "balance out" (should be rare and we don't care for acquisition) or that the spoiling star right on the edge of the 6x6 ends up coming more onto that pixel than modeled here. For acquisition I didn't know if that second case might be an issue, because I thought the placement of the 8x8 is hits-based not coordinate based. But probably all in the noise. |
@jeanconn - good points. I had been making a validation notebook for this function anyway, and I think that your concerns are addressed now. The notebook might be useful if you want to play around and decide to use this for guide. http://nbviewer.jupyter.org/url/asc.harvard.edu/mta/ASPECT/proseco/spoiler-impact.ipynb On the "balancing out", I put in code to insist that if there are multiple spoilers, they all get stacked in the same quadrant of the image readout window. On the issue of critical behavior near a pixel boundary, the plots in the notebook show that there does not appear to be very strong pixel-related changes in the output values. There is some discernible effect, but not strong. Also, in practice what is going to cause a rejection is the |
Gotcha. There's not much text there to hold my hand through what you've done to validate that, so it is going to take me longer to understand. |
If you look at the images showing centroid offsets, they are relatively smoothly varying and you don't see strong square-like structures corresponding to pixel boundaries. That's all I meant. |
To be clear you can see evidence of the pixels, but not like a wall somewhere. |
For use with acq selection, I think this is good and I'm merging. |
This computes the centroid offset and fractional change in summed counts caused by spoilers.
It runs in about 1 msec for a single spoiler.
To do: