15th Feb 2024: Astro Pixel Processor 2.0.0-beta29 released - macOS native File Chooser, macOS CMD-Q fixed, read-only Fits on network fixed and other bug fixes
7th December 2023: added payment option Alipay to purchase Astro Pixel Processor from China, Hong Kong, Macau, Taiwan, Korea, Japan and other countries where Alipay is used.
When creating a bad pixel map with my ASI294MC Pro something strange happens. The Amp glow is recognized as a hot pixel and if my Lightframe calibrated with it, disturbing pixels on the previously not see.
🙃
Hello Mabula, should I do without the Bad Pixel Map in this case?
Good question, I'm not sure if the BPM should include things like amp-glow actually, @mabula-admin knows all about that. But as a general rule, if the calibration frame causes a problem in the end-result, it's better to leave it out.
Hello Mabula, did you have a look at Bad Pixel Map?
Hi @minusman,
I have tested this on data that I have of a ZWO asi183mm which has very strong amp-glow.
I am seeing the problem that you have as well, allthough not so prominent, shown first is MasterDark, then BPM:
This was with APP 1.068 and a hot pixel kappa of 2.0.
I get the following calibration result (data provided by Yves van den Broek @yves_van_den_broek ) , first is shown an uncalibrated frame, then calirbated with a MasterBias, MasterDark and the Bad Pixel Map and with the Adaptive Data Pedestal on. The Adaptive Data Pedestal is needed here.
So this is fine I think.
Is the BPM in your case messing up data calibration of the light frames?
Can you show an example/screenshot ?
The issue most likely has to do with some changes that I made in the Bad Pixel Map creation. I should be able to adjust here. So I will have a look and test if I can improve this.
Mabula
Hello Mabula, I once processed another record of dark frames with cooling turned off. Since the problem hardly occurs.
I will again make new Darks and flat frames for security.
When creating BPM, do I need a Master Bias or Master Dark Flat? If I omit it comes a warning.
