Share:
Notifications
Clear all

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.

 

Streaky comet in LRGB

4 Posts
2 Users
0 Reactions
2,017 Views
(@rickwayne)
Neutron Star
Joined: 7 years ago
Posts: 79
Topic starter  

I ran an integration on C/2017 K2 yesterday and the result was not what I expected. Sort of the obverse of deep sky stacker's "register stars and register comet" mode, APP produced L, R, G, and B integrations with both the stars and the comet trailed!

I am reasonably sure that this is due to how I interleaved the exposures. Not wanting to end up with big time offsets between the various channels, I had it swap filters with every sub, so the data comprised endless repeats of LRLGLB. When APP prompted me about using timestamp metadata, I clicked "Yes", so the file list window sorted by time, interleaving the channels exactly as shot. I had to click on just about every frame to register the comet -- no big whoop, really. But when I was done I had four streaky integrations.

I tried again, unchecking everything but 14 of the luminance frames, and the comet looks just fine. For that I wound up having to click on about every other frame to register (I clicked "Yes" for "use metadata timestamp" again).

I'm not complaining, or even sure that this is a bug -- it might just be that using timestamp metadata is the wrong choice for this situation. It is, I suppose, somewhat less convenient to select the frames and do the registration four times instead of one. This is more of a "Hmm, interesting behavior" sort of message.

Screen Shot 2022 07 20 at 12.19.00 PM
Screen Shot 2022 07 20 at 12.20.20 PM

 

 



   
ReplyQuote
(@rickwayne)
Neutron Star
Joined: 7 years ago
Posts: 79
Topic starter  

BTW I ran it again, loading only one channel. With timestamp metadata on, I get streaks, without, I get a comet. This is with 2.0.0-beta2.



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5056
 

Hi Rick @rickwayne,

Thank you very much for reporting this behaviour 😉

It sounds like APP is having difficulties on your comet data to detect the comet properly... probably best if i can have a look at your dataset to see what happens exactly and why... and then properly fix it if needed 😉

Can you upload the dataset here?

https://upload.astropixelprocessor.com/

username: upload

password: upload

Please make a folder like RickWayne-Comet-issue and let me know once uploaded 😉

Mabula



   
ReplyQuote
(@rickwayne)
Neutron Star
Joined: 7 years ago
Posts: 79
Topic starter  

OK, done. RickWayneStreakyComet.

Thanks!



   
ReplyQuote
Share: