FWHM and Brightness filter for frame selection problem
Posted: Tue Mar 11, 2025 6:15 pm
Hi Robin
It is very useful to be able to select which frames to save and which to reject during capture. It enables leaving capture running even during nights of broken skies with clouds moving over while saving on data storage and downstream processing. I have been in the habit of using the FWHM and Brightness filters.
However the two measurements are clearly not orthogonal and the measurement of FWHM moves up and down with brightness in a consistent way -- in fact I'd estimate that - in a quantitative sense - most (60-80%?) of the variation in FWHM mirrors that in brightness. So by putting in a cut off value for FWHM I suspect that the unintended effect has been to exclude potentially the best and brightest frames?
The next stage on from Sharpcap selection is (for me anyway) to use Subframe selector in PixInsight to select the best frames on the basis of the FWHM and - a function that the PI developers have been gradually evolving and improving - it combines he most critical quality factors (signal, noise, PSF dimensions and shape, background gradients) in a single function that sort of expresses how well correctly shaped sharp PSFs emerge from the murk. Not surprisingly -- in this case high values of PSFSignalWeight tend to correlate with low values of FWHM -- so by itself it is usually probably all the selection that is needed cf FYI
https://pixinsight.com/doc/docs/ImageWe ... 20function.
For Sharpcap wondered whether it might make sense to try a selection parameter that was some combination of Brightness and FWHM ? Brightness already works well by itself as a selection criterion --- maybe FWHM/ brightness would provide a sort of 'brightness-normalised' FWHM value ?
Tim
It is very useful to be able to select which frames to save and which to reject during capture. It enables leaving capture running even during nights of broken skies with clouds moving over while saving on data storage and downstream processing. I have been in the habit of using the FWHM and Brightness filters.
However the two measurements are clearly not orthogonal and the measurement of FWHM moves up and down with brightness in a consistent way -- in fact I'd estimate that - in a quantitative sense - most (60-80%?) of the variation in FWHM mirrors that in brightness. So by putting in a cut off value for FWHM I suspect that the unintended effect has been to exclude potentially the best and brightest frames?
The next stage on from Sharpcap selection is (for me anyway) to use Subframe selector in PixInsight to select the best frames on the basis of the FWHM and - a function that the PI developers have been gradually evolving and improving - it combines he most critical quality factors (signal, noise, PSF dimensions and shape, background gradients) in a single function that sort of expresses how well correctly shaped sharp PSFs emerge from the murk. Not surprisingly -- in this case high values of PSFSignalWeight tend to correlate with low values of FWHM -- so by itself it is usually probably all the selection that is needed cf FYI
https://pixinsight.com/doc/docs/ImageWe ... 20function.
For Sharpcap wondered whether it might make sense to try a selection parameter that was some combination of Brightness and FWHM ? Brightness already works well by itself as a selection criterion --- maybe FWHM/ brightness would provide a sort of 'brightness-normalised' FWHM value ?
Tim