Register with extra...
 
Share:
Notifications
Clear all

May 27 2026 APP 2.0.0-beta45 has been released !

Fully Multi-Threaded LNC, many improvements for the registration engine, platform upgrade, and further tuning of internal memory consumption and memory release back to OS.

Apr 14 2026: Google Pay, Apple Pay & WeChat Pay added as payment options

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.

 

[Solved] Register with extract Ha/extract OII problems

1 Posts
1 Users
0 Reactions
1,834 Views
(@legba42)
Molecular Cloud
Joined: 7 years ago
Posts: 1
Topic starter  

I would appreciate if anyone can provide some advice on an APP integration problem. I’m having trouble understanding the reason why in one of my processed images it looks like the flats (or something else) didn’t register correctly.

extractHa
extractOII

 

Images are from a single 4.5 hour session (California Nebula) using a cooled ASI183MC Pro and and this run included a meridian flip so some lights are rotated. I took flats/darkflats just after finishing the lights so image train and rig setup were the same, darks are from a library I made a few weeks ago and all subs including calibration are matched in temp/gain.

When using the “extract Ha” algorithm the resulting integration looks perfect, but when using “extract OII” the flats or the lights (maybe the ones after the flip?) didn’t register properly or were rotated. The only difference in APP settings are the different extract algorithms.

The results are odd too as I’ve used this same basic procedure (extract Ha then extract OII then extract mono for bicolor processing later) for approx 10 other dso projects before including some that are multisession. So far all of my previous integrations have worked out ok in terms of automatic registration of calibration frames.

I’ve also tried several different APP settings to find a solution such choosing different reference frames, forcing the reference to be before or after the flip, manually rotating the reference frame, checking “flip descriptors in x/y”, restarting APP, using individual steps 0-6 vs the push integrate once approach. All of the resulting images always have the same basic results where the extra Ha looks good and extra OII has problems with registration.

Any ideas on what is causing this problem? Maybe process the before/after flip in different sessions just for extract OII?

Thanks!

Brian



   
ReplyQuote
Share: