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.
I did a mosaic with the beta22 and I got this weird artefacts.
Can you describe your workflow, kind of data etc?
@vincent-mod it happens when I do a mosaic pre-integrated frames, it happens often, just that sometimes is less visible than others
Are you creating panels first? That would be my advise at least. What APP version are you using?
Thank you very much for reporting this issue. It looks like another issue we are working on but I can't be 100% sure. Can you upload the data on which this happens and describe xactly what settings we need to set in menus 2) to 6) to be able to duplicate the problem?
You can upload it here:
https://upload.astropixelprocessor.com/
username: uploadData
password: uploadTestData
please make a folder with your name and issue like : DavidMitti-mosaic-artefacts
and let us know once uploaded, we will investigate as soon as we can 😉
Mabula
@vincent-mod yes, beta22 if I remember correctly. I'll try to reproduce and upload the files
Hi David,
Is this problem still occuring? If so, can you please upload data on which it occurs so I can test and fix it? Thanks 😉 You can use the upload instructions from my previous post.
Mabula
@mabula-admin I don't have the issue anymore, if I get it again I'll upload. thanks
Okay David @davemitti,
Thank you very much, I will close the issue on my list then, but please let me know if it does happen again 😉 then we really need to have a good look !
Mabula
@mabula-admin I uploaded 2 frames and integrated with average, weight quality, local normalization rejection, no LNC
there are bands at the edge of one frame in the final integration (called west_filamentary13_14.fits).
the other 2 images are the 2 panels combined
Hi David @davemitti,
Thank you very much, I have fixed this issue already in the meantime ;-). The fix will be included in 2.0.0-beta26 which I will try to release today or tommorow 😉
- Fixed, improved and faster Multi-Band Blending or MBB
As reported here : https://www.astropixelprocessor.com/community/main-forum/strange-horizontal-lines-in-mosaic-integrations/paged/2/#post-29618 MBB could remove data in overlap areas when the MBB % was set to a high level. We have found the cause of this. MBB was always removing 1% of the image borders relative to the set MBB percentage. This is completely fixed now. All data will always be used, so these strange artefacts should no longer happen. In addition, the MBB % was relative to the size of the entire field of view, which is not ideal for mosaics. Preferrably, the MBB % is relative for each image in the stack to the area where data is not 0 in that image, so we have implemented this improvement inlcluding code optimizations that improved MBB speed. For a big mosaic, the MBB calculation can be 3x-5x faster as well. This should improve Multi-Band Blending in all situations, especially when combining data from different setups and/or mosaics. The next image shows a mosaic where the issue occured which caused gaps/holes in the final mosaic. Now with beta26, this no longer happens and all data is preserved and MBB is about 5x faster causing the integration process to be faster as well. On the right side, the MBB weight map is shown where we used 50% MBB in this case:
Mabula
