APP fails to regist...
 
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.

 

APP fails to register meridian flipped subs - what am I doing wrong?

4 Posts
3 Users
0 Reactions
1,061 Views
(@cdp17)
White Dwarf
Joined: 6 years ago
Posts: 9
Topic starter  

Hi,

I've integrated E and W files many times before, and APP has never had a problem.  But with this new set of subs, suddenly every single W sub fails; you can see this in the attached illustration on several different nights, for images that were taken just 10 minutes apart, but had a meridian flip in between.

My assumption is that I've accidentally hit some switch in APP, but what?

This is happening on all channels, but for clarity in the attached illustration I've included just a snapshot of some luminance subs.

Note:  Using APP 1.083.4

Failed registration M81

 Thanks in advance for help!



   
ReplyQuote
(@wvreeven)
Quasar
Joined: 8 years ago
Posts: 2134
 

@cdp17 Hi Charles. There is no switch in APP that would introduce that behavior. Just to be absolutely sure, you are not using a rotator on your telescope that has a different position W with respect to E? I don't think you are but I'd like to be absolutely sure.

Are you sure that the W images cover a large part of the field of view of the E images? I have seen cases where star analysis would fail after a flip because unexpectedly the telescope was pointing several degrees away from the target after a meridian flip. Perhaps you can plate solve one E and one W image to make sure that this is not the case.



   
ReplyQuote
(@cdp17)
White Dwarf
Joined: 6 years ago
Posts: 9
Topic starter  

Hi Wouter (I think that's your name!),

Thank you for confirming that the issue is probably not a setting within APP.  I will reach out to the telescope support staff and ask them about rotation coverage after a flip, and ask them to review the FITs files that were delivered to me.

Visually it looks to me as if the E and W images do cover the same area, so this is a puzzle.

Regards,

Charles



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

The overlap has to be good, is that indeed the case? Say at least 50% or more? Because if it's not, that would mean the scope didn't center the target really well. APP should still be able to register that, but it'll depend a bit on the quality of the data and the overlap with the normal settings.



   
ReplyQuote
Share: