2023-09-16: APP 2.0.0-beta23 has been released !
Improved performance again, CMD-A now works in macOS File Chooser, big improvement for bad column cosmetic correction, solved several bugs
We are very close now to releasing APP 2.0.0 stable with a complete printable manual...
Astro Pixel Processor Windows 64-bit
Astro Pixel Processor macOS Intel 64-bit
Astro Pixel Processor macOS Apple M Silicon 64-bit
Astro Pixel Processor Linux DEB 64-bit
Astro Pixel Processor Linux RPM 64-bit
General
4
Posts
2
Users
2
Likes
782
Views
Topic starter
January 24, 2022 23:21
I've looked around for answers but not sure they're specific to my questions!
I'd like to create a BPM as best I can, but I'm unclear on several aspects.
Here we go:
- Can I use any flats and darks? Or does it have to be specific to a project? If not specific, then is it better if I include a mix of calibration files from different projects?
- Do I have to use darks, or can I use a bias instead?
- Is it better to use as many calibration files as possible?
- Can a BPM then be reused across all projects?
Thanks, Brendan
January 25, 2022 17:57
- You can use any flats and darks, but if you want to make a really good BPM a good idea would be to do this separately. With a longer exposed dark, no cooling etc. so you can produce the noisiest noise the sensor can make. 🙂
- You do need a dark as a BPM is detecting hot- and cold-pixels
- It's fine to use 1 dark, but make it a noisy one
- A BPM can be used for the same camera for a long time yes, it's not destructive to your data. I'd day up to a year.
BrendanC reacted
Topic starter
January 25, 2022 21:23
And what's what we call brilliant moderation!
Thank you Vincent, this is perfect. Exactly what I needed. 🙂
Vincent-Moderator reacted
January 25, 2022 21:41
Thank you Brendan, that's appreciated! Hope it works. 🙂
