Drift during integr...
Clear all

2023-04-17: APP 2.0.0-beta17 has been released !

RAW support for camera color matrix with Bayer Drizzle integration, fixed couple of image viewer issues.


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

Drift during integration causes uneven background

2 Posts
2 Users
Molecular Cloud
Joined: 2 years ago
Posts: 1
Topic starter  

For some of my captures, star tracking fails occasionally (typically when the tracking star is too faint, or there is some wind) resulting in some overall drift over time. Most of my frames are still good, I just reject the ones where stars are elongated or have other artefacts.

Because of the drift, when I stack the result, I don't have the same number of stacked frames at every pixel.

Now I'm in a site with some light pollution, and so in positions in the final stacked image where I have many frames, the background looks very light and obvious. Were I have fewer frames, it is darker. The attached stacked image shows what I mean. The result is disappointing because it lack color and contrast.

This effect is very difficult to deal with on the stacked result. Is there a way to correct the background on every frame so it is darker, so when I combine all the frames, it stays dark everywhere ? In other words I would like to estimate the background light pollution pedestal on every frame and subtract it on each of these frames, so when I combine all the stacked images, it is not as bothering. Is there a way to do this in APP ?

On the attached image, see how the background is much darker near the top of the image than near the middle? this is not due to the C12 galaxy presence, but due to the light pollution background.



Universe Admin
Joined: 6 years ago
Posts: 5456

It does look like the background is black there, which would be too dark I assume? 🙂 Did you use some Light Pollution Correction to see if that would help (it only does properly when you do have data of course)?