2022-05-11: APP 2.0.0-beta 1 has been released !!!
Providing many improvements ! and a macOS M1 native version ! Please read the announcement here.
Download links per platform:
windows 2.0.0-beta1
macOS x86_64 2.0.0-beta1
macOS arm64 M1 2.0.0-beta1
Linux DEB 2.0.0-beta1
Linux RPM 2.0.0-beta1
Linux DEB HiDPI 2.0.0-beta1
Linux RPM HiDPI 2.0.0-beta1
Hi,
I usually use all calibration frames (Flats, Dark Flats, Darks, Bias) in pre-processing but I have a good CCD and image at -20C so in theory I shouldn't need to use Darks.
So tonight I tried using all of the above except Darks and ended up with hot pixels still showing after Calibration. I was using Average weighting and tried Windsor/Mad/Sigma rejection to no avail.
Then tried again with Darks and hot pixels are gone.
Any thoughts, do I need Darks to get rid of hot pixels?
BTW, I created a bad pixel map and it turned out looking like a grey image without the Darks - with the Darks the hot pixels show up fine. Is that expected?
Any thoughts?
Apologies, the week has been very busy overhere.
So yes, the purpose of a dark is exactly that, to identify hot pixels. And amp-glow, if that would be the case. You can create a BPM with a proper, long dark and if you have no amp-glow, you can use just a BPM. Having this grey background is normal indeed.
No worries, thanks for your patience. 😉
Latest Post: How to add the post Fits file back into APP Our newest member: ayan hanna Recent Posts Unread Posts
