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

Stokes I fitting threshold #121

Open
Cameron-Van-Eck opened this issue Mar 26, 2024 · 0 comments
Open

Stokes I fitting threshold #121

Cameron-Van-Eck opened this issue Mar 26, 2024 · 0 comments

Comments

@Cameron-Van-Eck
Copy link
Collaborator

The Stokes I fitting tool for 3D cubes has a feature where it will only fit pixels above a threshold; this saves computation working on pixels of low signal.

Paddy recently complained that the current threshold is far too permissive, in that it includes too many pixels compared to what might be expected. The current filter/threshold implementation is this: per-pixel, it checks how many channels are above the user-supplied threshold (which is either in intensity units or a multiple of the estimated channel noise); if 1 or more channels are above the threshold, the pixel is fit. Having the threshold be only one channel means that the filter is very sensitive to outliers -- even a single channel with anomalously high noise/values is enough to trigger fitting on nearly every pixel. So the threshold has to be set very high, which isn't always good.

Should we change the filter condition? For example, it could be if 50% of channels are above the threshold value -- this would be more robust against small numbers of outlier channels. It's an easy change to make, as well. I'm not sure if there's a more statistically interesting/clever/valid test we could construct for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant