Wierd result of mos...
 
Share:
Notifications
Clear all

Mar 28 2026 APP 2.0.0-beta40 will be released in 7 days.

It did take a long time to have the work finished on this and it  will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...

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.

 

Wierd result of mosaic integration

4 Posts
2 Users
0 Reactions
1,269 Views
(@rapid)
Brown Dwarf
Joined: 6 years ago
Posts: 4
Topic starter  

Hello!

I just finished my longest project. It's a 3x2 mosaic of the Veil Nebula. It took me 12 sessions to finish the shooting and I ended up 599 frames.

I put everything in APP, carefully matching the sessions of lights and flats together.

The integration ran more than 8 hours and I needed to uninstall almost everything from my computer, because it needed 900+ GB of space. 😀 

 

And the result was quite wierd and I don't know why.

In Calibrate and Analyse stars menu, I didn't change anything.

In the Register menu I set the registration mode to mosaic.

Nothing changed in Normalize.

In the Integrate menu I set MBB to 10%.

Is it connected to the Dynamic distortion correction, because it is enabled by default and I let it that way?

Can you help me determine the problem?

 

veil

This topic was modified 3 years ago 3 times by Zoltán Incze

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

It may be that you need to disable the distortion correction, some data doesn't actually require it and if the data is good by itself it can cause weird behavior indeed. Normalization I would switch to advanced mode btw.



   
ReplyQuote
(@rapid)
Brown Dwarf
Joined: 6 years ago
Posts: 4
Topic starter  

@vincent-mod Your suggestion worked. Thanks! However the processing took quite a lot of time (19 hours on a Ryzen 9 5950x with 32GB RAM)  and needed 1.2TB storage space to finish.

Also, these strange artifacts appeared in several places on the final image and not just in red, in green and blue too. Any idea?

artifact

This is the final image. I removed all of these artifacts.

VeilFull Layers Small

Thank you again!



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

Those red dots are likely hot pixels, when a mosaic is created there is no outlier rejection taking place, you can set that up manually if you want though. If you make the panels one by one first (recommended) these should be gone already.



   
ReplyQuote
Share: