Mosaics and Filters...
 
Share:
Notifications
Clear all

MAY 4 2026: APP 2.0.0-beta44 has been released !

New improved internal memory controls should now work on all computers

May 1 2026: APP 2.0.0-beta43 has been released !

Improved internal memory controls (much more stable and faster on big datasets), fixed CPU image viewer, fixed Narrowband extraction demosaic algortihms.

Apr 29 2026 APP 2.0.0-beta42 has been released !

New improved Normalization engine, Fixed random crashes in integration, fixed RGB Combine & Calibrate Star Colors, fixed Narrowband extraction algorithms, new development platform with performance gains, bug fixes in the tools, etc...

Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options

Update on the 2.0.0 release & the full manual

We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.

Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.

 

Mosaics and Filters/RGB combine

9 Posts
2 Users
0 Reactions
2,359 Views
(@connor231)
Neutron Star
Joined: 6 years ago
Posts: 106
Topic starter  

I'm currently working on a mosaic of the Carina nebula. Four panels - mono camera - four filters (HaRGB).

This means I will have 16 integrations to combine. It seems to me there are two ways to go:

     Option 1 - Mosaic the panels for each filter. Then do RGB combine, light pollution reduction, etc on the "mosaiced" images.

     Option 2 - Start with RGB combine, LPR, etc for each panel and combine the mosaic as the last step in APP.

I think each option has some advantages. I have been using Option 1 for testing while I am still getting data and it seems to work OK.

My question is - can a strong case be made for one of these options over the other ? Or does it just come down to minor differences/personal preference ?

I don't know enough about the interaction between normalisation and mosaic processing, but I would not be surprised if Option 2 was technically superior. I would apreciate any comments.

thanks

JC



   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

Option 2 is better I think (there are more ways to Rome for sure), but I would also try option 3. Which is creating the panels first, so panel 1 fully integrated as HaRGB. This panel doesn't have to be corrected yet as creating a mosaic will change things anyway. Load these panels as lights and then create the mosaic. This mosaic can then be fully corrected.

ps. I guess your option 2 is basically this, I just removed the correction steps. 🙂



   
ReplyQuote
(@connor231)
Neutron Star
Joined: 6 years ago
Posts: 106
Topic starter  

Vincent

Thanks for your comment. I hadn't even considered your option 3, but I suspect you may be on the right track.

I was hoping for a technically based/justified response - maybe even some words of wisdom from the man himself, although I wouldn't want to distract him from getting 2.0.0 stable ready for release (grin).

regards

JC



   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

The man himself is very busy, but I can ask if you really need that. 🙂 One of the things to use my option is that, while you can correct the panels first as well, the calculation of creating the mosaic changes the background again. This has to do with the overall statistics in that algorithm. Which makes that it's better to correct after creating the mosaic.

Besides that combining entire mosaics and registering those with each other is an ok option as well, but less manageable when the mosaic gets bigger. The algorithm is optimized for creating the mosaic from the panels.



   
ReplyQuote
(@connor231)
Neutron Star
Joined: 6 years ago
Posts: 106
Topic starter  

Thanks Vincent

I think you have given me enough to think about and move forward - probably don't need to bother the man.

regards

JC



   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

No worries if you do need more detailed information. If anything is unclear in your further testing, just give us a shout.



   
ReplyQuote
(@connor231)
Neutron Star
Joined: 6 years ago
Posts: 106
Topic starter  

Vincent

Here is my finished mosaic, probably with too much colour saturation as I can't help myself.

I tried processing this the way you suggested in option 3, but it didn't work well. I ended up with something with different colour issues in different parts of the image. Perhaps I stuffed something up, but anyway it was worth a try.

I ended up going back to option 1. I started by first creating a mosaic for each filter, then LPR for each filter and then processed more or less normally from that point onward. The star colour calibration step didn't work as normal - I suspect the starfield was so dense that APP mistook stars for nebulosity, but I'm just guessing about that. One thing that supports that guess is that I tried a star reduction and it only changed a tiny fraction of the stars in the image. I ended up doing star reduction outside of APP.

Still, I'm fairly happy with the end result.

Carina Nebula (downsampled) 2x2 mosaic.

Eta Carina Nebula E100 mosaic 2023 04 21 HaRGB downsized


   
ReplyQuote
(@Anonymous 174)
Joined: 9 years ago
Posts: 5702
 

The different colors in the end result can be normal, due to variations in calibration between the panels. But that usually is solved with some careful light pollution correction. In any case, you found another workflow that seems to have worked nicely. If you want I can always have a go as well. 😉



   
ReplyQuote
(@connor231)
Neutron Star
Joined: 6 years ago
Posts: 106
Topic starter  

Thanks Vincent - I think I'm good for now. I did try to fix the local colour issues with LPR, but it was pretty difficult with the way the nebula sat in each panel.

Anyway - thanks for your help.

JC



   
ReplyQuote
Share: