Apr 9 2026 APP 2.0.0-beta40 has been released !
It has a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration, for mosaics even faster! 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. Improved Outlier Rejection with LN 2.0 rejection. macOS CMD+A works now in file chooser ! And more, all will be added to the release notes in the coming hours...
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.
Stacking and post processing with Astro Pixel Processor.
Some artifacts around the stars, probably come from bad dithering.
Very nice Minusman ;-)!
I notice, you used bayer drizzle with gaussian kernel and drops of 1?
Did you try with tophat kernel and or bigger drops? Both could really help with improving SNR, but then again, maybe with a less sharp result?
I saw the artefacts near the bright stars, could it be reduced wit sigma clipping possibly?
Interesting to know, how many frames did you stack? is it 211? And no dither between each frame?
Cheers,
Mabula
There are 64 frames, with Sigma clipping. Winzored clipping had always generated error. With dropletsize 2 and tophat kernel the result looked the same.
The pixel spacing probably is not large enough. I now always use 20 pixels distance.
Thank you minusman 😉
Yes, Winsorized can give artefacts, especially with the diffraction patterns that are visible. Then normal sigma clipping is the way to go.
"The pixel spacing probably is not large enough. I now always use 20 pixels distance."
That would be enough normally. Maybe the sky conditions had influence as well here?
Mabula
Atmospheric disturbances can also be a cause. Winsorized clipping did not go in conjunction with LNC. Then the integration process always broke down. I will still test it with other settings again.
Can you give me an indication where it breaks down with winsor clipping ? Maybe console output when it does?
Mabula
These two errors came with the stacking again and again. Disable filterstar profile and
with Simga Clipping ran then error-free.
Hi minusman, is this with or without using drizzle?
It seems to be two separate bugs which I need to fix.
Could you possibly send me a subset of your data so I can find the causes of these errors and fix them ?
Mabula
What data should I send the calibrated data or raw?
Hi minusman,
If you have the calibrated frames, those should fine 😉
you can send them to: mabula@astropixelprocessor.com
Thanks,
Mabula
Hi minusman,
Did you send me some of your frames? If not, can you send me some so I can have a better look?
Cheers,
Mabula
Mabula, So you know during my I/O exceptions of my 'clear info/norton' thread I too was using windzor..
~Kevin
Mabula, So you know during my I/O exceptions of my 'clear info/norton' thread I too was using windzor..
~Kevin
Hi Kevin,
I don't think winsorized clipping will cause an IO error. I really suspect it's related to Norton claiming space, but I am not sure yet, you are the first to report that problem.
Mabula
I can unfortunately upload the frames, the data is too large for my Internet connection. Sorry
I can unfortunately upload the frames, the data is too large for my Internet connection. Sorry
No problem, minusman, I'll try to find and fix the star filter and winsor clip combined bug(s) you encountered.
Cheers,
Mabula
