2023-01-19: APP 2.0.0-beta13 has been released !
!!! Big performance increase due to optimizations in integration !!!
and upgraded development platform to GraalVM 22.3 based on openJDK19
We are very close now to releasing APP 2.0.0 stable with a complete printable manual...
Strange trails or (bad?) pixels
I just tried to stack some long exposure (30 to 90 sec.) of comet Neowise and got strange pixel trails in an opposite direction of the startrails. Would this be solved if I had made darks and bias etc.?
Very likely yes, these can be bad pixels.
@vincent-mod Thanks for your reply... Is there any way to minimize them without darks etc.?
You can try to use cosmetic correction in tab 2, switch the options on for hot pixels, I'm not entirely sure if that works without any calibration data (never tried that). Brin the hot pixel kappa down to maybe 2.5 or lower to make it more aggressive.
@vincent-mod Thanks! I’ll just give it a try... And maybe I’ll make some darks too... If they are bad pixels, they might appear at the same place anyway!?
Yes that's why darks work. If you make some proper darks a BPM will be made automatically as well, this you can use on all your data taken with the same sensor. It removes bad pixels and never hurts the data, so always use one is my advice.
You could try some retrospective darks.
Good suggestion Steve, you can try that indeed and make a bpm with those.