Error when integrat...
 
Share:
Notifications
Clear all

2026-10-09 APP 2.0.0-beta48 has been released !

This is mainly a bug fix release for the reported bugs in beta47. In addition it has a significant User Interface performance improvement noticable when you need to process 1000s of images in APP.

2026-10-03 APP 2.0.0-beta47 has been released !

This is a very big release... many code optimizations/rewrites, many parts of APP are much faster and more precise, especially star analysis and registration are much faster ! Big mosaics will go much faster 🙂

And we introduce a new preview filter, which includes the new Adaptive Deep Sky Stretch and a General Levels Stretch, this has been long over due. The old preview filter (the panel on the right side to stretch and preview your data) has not been updated for a couple of years and it is a critical part of any APP session.

Adaptive Deep Sky Stretch or ADSS is a much more intuitive stretch algorithm. It is also color preserving (which is a great new addition in itself ! ) which means that the highlights are no longer bleached, color is maintained from the linear data while stretching. You can simply stretch your data using the sky background level and signal width sliders which work much easier and more intuitive. You no longer need to fiddle with the old complicated sliders with zoom buttons. All the zoom buttons for the sliders are made redundant. And you can enter slider values in the slider value fields yourself. I will make a youtube video in the coming days to explain and fully introduce ADSS. Once the video is ready, it will be highlighted on the forum.

RGB Combine upgrade !. The RGB Combine Tool has been rewritten mostly. The tool is faster and easier to use and most importantly, the Luminance slider to inject a luminance channel or channels into the RGB composite is now working correctly. It no longer bleaches the RGB colors. Combined with the new ADSS preview, you will get much better and easier great composites with great color! I will also explain this in a new youtube video.

Error when integrating 2 images obtained from Ha-OII and SII-OIII

4 Posts
2 Users
0 Reactions
750 Views
(@lammertus)
Neutron Star
Joined: 9 years ago
Posts: 134
Topic starter  

Hi Mabula,

 

I just ran a session of APP beta39 on frames taken with Ha-OIII and SII-OIII filters

and aftrwards wanted to integrate the 2 seperate OIII results to get a master OIII.

APP runs fine doing that but once it is constructing the final image it throws an error

message:

imagen

Anything special I should take in account for or might this be a hickup on my PC?

It does generate the resulting integration file on disk so I  can continue with my

workflow.

Evenso this is a bit worrying me.

If you find time, please let me know!

Best regards,

Mert



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 10 years ago
Posts: 5468
 

Hi Mert @lammertus,

Thank you very much for posting this error.

The error seems to indicate that a certain image is not there and also that it is still trying to process extract O3 actually. Do you have the Force CFA enabled by any chance while trying to process the 2 OIII masters?

Maybe you can explain the workflow in more detail step-by-step with the settings of 0) Color settings?

Then I can find this problem and hopefully fix it.

Mabula



   
ReplyQuote
(@lammertus)
Neutron Star
Joined: 9 years ago
Posts: 134
Topic starter  

Hi Mabula, thanks a lot for getting back to me!

Likely it is a user error because I have these settings in tab 0:

imagen

So I am afraid I tried to integrate the 2 OIII images with this setting and should have changed it to

adaptive airy disk for the 2 OIII master integrations.

Will try again when I get home and let you know!

Best regards,

Mert



   
ReplyQuote
(@lammertus)
Neutron Star
Joined: 9 years ago
Posts: 134
Topic starter  

Hi Good evening Mabula,

I just tried again loading the 2 OIII integration files of both filters changing

the algorithm to Adaptive Airy disk and all works flawless!

Sorry for my mistake, the error was caused by user error not by APP!!

Best regards,

Mert



   
ReplyQuote
Share: