Hi everyone,

I’m currently working on a rather ambitious astrophotography project and would really appreciate some advice from experienced Astro Pixel Processor users and the developers.

The project

I captured a large 21-panel (7 × 3) mosaic of the Rho Ophiuchi region from Isabis, Namibia, under exceptional Bortle 1 skies.

The dataset consists of approximately 105 hours of total integration time, with around 5 hours per panel and 25% overlap between adjacent panels.

My imaging setup:

• Telescope: Askar SQA55
• Camera: ToupTek 24AC (full-frame OSC)
• Mosaic: 7 × 3 panels
• Overlap: approximately 25%
• Total integration: approximately 105 hours
• Location: Isabis, Namibia (Bortle 1)
• Processing: Astro Pixel Processor
• Computer: MacBook Pro M3 Max, 36 GB RAM

My processing workflow so far

I calibrated, registered and integrated each of the 21 panels individually in APP.

Afterwards, I loaded the 21 integrated panels into APP to create the final mosaic.

I’ve experimented extensively with different mosaic integration and normalization settings, including:

• Multi-Band Blending (MBB), including 25%
• Local Normalization Correction (LNC), including second-degree LNC with 5 iterations
• Different normalization approaches
• Different reference panels, including a central panel
• Full Image normalization
• Background neutralization and gradient correction
• Different mosaic integration settings

I’ve also been experimenting with Drizzle during the individual panel integrations. Due to APP’s practical image-size and memory limitations, I cannot currently process the entire mosaic at its maximum potential resolution.

The problem

Despite numerous attempts, I’m still struggling with visible transitions between the individual panels.

The attached image illustrates the problem.

There are noticeable horizontal and vertical structures along the panel boundaries, often appearing as yellowish lines or areas with different background brightness and color.

Interestingly, some of the overlapping regions appear to have a more uniform or cleaner background than the central areas of the individual panels.

This makes me wonder whether the normalization and gradient correction are treating the overlap regions differently from the rest of each panel.

Increasing the strength of LNC and other corrections can improve the visible transitions, but unfortunately it also seems to suppress faint dust and nebulosity.

And that is exactly what I want to avoid.

The Rho Ophiuchi region contains extremely faint and complex dust structures, and with 105 hours of exposure under Bortle 1 skies, preserving those structures is particularly important to me.

I’ve successfully processed smaller mosaics, including 4 × 4 panels, without encountering these problems to the same extent. The difficulties seem to become much more pronounced with this larger 21-panel project.

My questions

1. What would be the recommended APP workflow for a 21-panel mosaic with significant faint dust structures and 25% overlap?
2. Would you recommend applying gradient correction individually to all 21 integrated panels before creating the mosaic, for example using APP, GraXpert or PixInsight DBE?
3. Could normalization based primarily on overlapping regions explain why those regions sometimes look better than the central areas of the panels?
4. What combination of LNC, MBB and normalization settings would best preserve faint nebulosity while eliminating visible panel boundaries?
5. Could Drizzle integration followed by downsampling or resampling contribute to these artifacts, or is this most likely an independent normalization/gradient issue?
6. Is there a recommended strategy for processing such a large mosaic at full resolution, potentially by dividing the mosaic into smaller sections before the final integration?

My goal

I want to achieve a seamless mosaic with a consistent background, natural colors and, most importantly, without sacrificing the extremely faint dust structures captured during those 105 hours.

I’m more than willing to reprocess all 21 panels if necessary, but before investing another significant amount of processing time, I would really appreciate some guidance on the most effective workflow.

I’ve attached an image showing the current result and the visible transitions between the panels.

Any suggestions, recommended APP settings or insights from users who have successfully processed similarly large mosaics would be greatly appreciated.

Thank you very much for your help!

Best Joerg

Original image:

Stars removed

For comparison, here's an earlier image processed with APP version 2.0.0-beta44:

Am I missing something?

Hank

The second image shows the stretch with the colour preservation set to 20% - what I find looks more realistic.

What do you think? Is the saturation extreme? Am I using the right method to tone it down?

I have a suggestion for registration of images in mosaic mode. I don't know if this would work, but who knows. I run app on a mac m4 max with quite a lot of memory, but registration of a mosaic using about 150 images takes ages because it seems it is trying all combinations 1 by 1. I wondered if this process wouldn't be much quicker if there would be a plate solving before doing the registration? When you have the coordinates and boundaries of images you can do the registration based on that and very quickly select which images have a direct overlap. It's just an idea, but maybe interesting to think about?

APP beta48 MacOS Sequoia 15.7.9.  Stacking 213 subs.

APP is frequently warning that I am running out of disk space. Then I test disk space and there is enough and APP continues.

JSYK

This was one of the first targets I took a photo of when I got my first dedicated astrophotography camera five years ago. Of course, I didn't know what I was doing back then and it didn't turn out very good so I have been wanting to try it again. The weather usually turns cold too soon here in Michigan so I need some decent fall weather to get this target. Luckily I am getting that this week. It doesn't rise til midnight but I can still get 7 hours of data. Hoping to get SII and OIII in the next few days. These are stacked in APP, then run through BlurXTerminator and NoiseXTerminator in SAS Pro, then Starnet to remove stars and a little extra noise reduction in Topaz Denoise for the starless version. Can't wait to have RC Astro tools implemented in APP. Mabula, any chance you can look into R.A.'s Aberration Correction ( Riccardo Alberghi ) being added to APP? It is included in SAS Pro so I am guessing it may be an open source program.

Thanks,   Tom