Error when normalis...
 
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 normalising (index out of bounds)

13 Posts
3 Users
3 Reactions
4,097 Views
 Nick
(@n-a-hardygmail-com)
White Dwarf
Joined: 8 years ago
Posts: 10
Topic starter  

Hi All,

I am trying to combine a RGB fits image with an Ha fits image.
But when i try to integrate them i get an error during normalising.

Encountered error in module:                     
NormalizationActionListener

Error message:
java.lang.ArrayIndexOutOfBoundsException: 1

Cause:
1
y.a(Unknown Source)
y.doInBackground(Unknown Source)
javax.swing.SwingWorker$1.call(SwingWorker.java:295)
java.util.concurrent.FutureTask.run(FutureTask.java:266)

I could be doing something wrong, but i don't think this error should show up.

I'm using APP version 1.071
If you need any other information just ask.

Kind regards,
Nick



   
ReplyQuote
(@markm75)
Main Sequence Star
Joined: 7 years ago
Posts: 23
 
Posted by: @n-a-hardygmail-com

Hi All,

I am trying to combine a RGB fits image with an Ha fits image.
But when i try to integrate them i get an error during normalising.

Encountered error in module:                     
NormalizationActionListener

Error message:
java.lang.ArrayIndexOutOfBoundsException: 1

Cause:
1
y.a(Unknown Source)
y.doInBackground(Unknown Source)
javax.swing.SwingWorker$1.call(SwingWorker.java:295)
java.util.concurrent.FutureTask.run(FutureTask.java:266)

I could be doing something wrong, but i don't think this error should show up.

I'm using APP version 1.071
If you need any other information just ask.

Kind regards,
Nick

Im running into the same error on integrating one Ha frame with a bunch of RGB osc lights



   
ReplyQuote
 Nick
(@n-a-hardygmail-com)
White Dwarf
Joined: 8 years ago
Posts: 10
Topic starter  

@markm75

Hi Mark,

It turns out that you don't have to normalise and integrate them.

First stack all the osc subs, then stack the ha subs. You can also do remove light pollution and things like that to those stacked images.

Then clear everything on tab 1 and load the stacked images as lights.

Just go up to registering on tab4 and start registration.

Then save the registered frames.

You can then use the combine tool on tab 9 to combine the osc and ha registered frames.

Nick



   
ReplyQuote
(@markm75)
Main Sequence Star
Joined: 7 years ago
Posts: 23
 
Posted by: @n-a-hardygmail-com

@markm75

Hi Mark,

It turns out that you don't have to normalise and integrate them.

First stack all the osc subs, then stack the ha subs. You can also do remove light pollution and things like that to those stacked images.

Then clear everything on tab 1 and load the stacked images as lights.

Just go up to registering on tab4 and start registration.

Then save the registered frames.

You can then use the combine tool on tab 9 to combine the osc and ha registered frames.

Nick

Thanks for the tip... That kinda worked, until i realized i didnt have it on force cfa mode.. (everything was grayscale)

When i redid it with force cfa the combine tool says the two types are incompatible.

I'm not sure if i did the original ha one correct perhaps (it says gray scale, i thought this was correct).  I may need to post this in its own thread



   
ReplyQuote
 Nick
(@n-a-hardygmail-com)
White Dwarf
Joined: 8 years ago
Posts: 10
Topic starter  

@markm75

I've never needed force CFA.

What camera do you use?

Make sure to set the algorithm to Ha when use use a osc camera with an ha filter.

It will save the the settings in the fits header. Just open the file in APP and check the info screen just left of the picture.



   
ReplyQuote
(@markm75)
Main Sequence Star
Joined: 7 years ago
Posts: 23
 
Posted by: @n-a-hardygmail-com

@markm75

I've never needed force CFA.

What camera do you use?

Make sure to set the algorithm to Ha when use use a osc camera with an ha filter.

It will save the the settings in the fits header. Just open the file in APP and check the info screen just left of the picture.

I've always found that if i dont enable force cfa, the final (color) image wont have color, unless i'm doing something wrong (for normal filters not ha).

I'm using the asi294mc pro in this case.

Shouldnt the Ha be grayscale when done integrating? (chose the ha option when the type of filter is asked)  And of course the lum is color.



   
ReplyQuote
 Nick
(@n-a-hardygmail-com)
White Dwarf
Joined: 8 years ago
Posts: 10
Topic starter  

@markm75

Yes, it does come out in gray-scale.

But I used to choose the correct algorithm on tab 0 and only load the Ha subs and integrate them separately.

Never tried the different channels back then.

I now have a mono cam so everything is gray-scale 😉

So, what happens if you only load the color subs and stack them separately?

Do you get a colour integration?

I always got colours in the integration.



   
ReplyQuote
(@markm75)
Main Sequence Star
Joined: 7 years ago
Posts: 23
 
Posted by: @n-a-hardygmail-com

@markm75

Yes, it does come out in gray-scale.

But I used to choose the correct algorithm on tab 0 and only load the Ha subs and integrate them separately.

Never tried the different channels back then.

I now have a mono cam so everything is gray-scale 😉

So, what happens if you only load the color subs and stack them separately?

Do you get a colour integration?

I always got colours in the integration.

Mono would make this easier ha, yeah.

I can integrate the ha ones, get grayscale.. so thats good.  

Then in another session i integrate the color.. get color.. good as well.

New session, now i add the two integrations as "lights" ( double checked without cfa checked the lum one did show color in the preview, strange).

At this point i can try to normalize the two integrations, get the index error of course.. so skipping that and just doing "save registered frames" as two new files.  (not doing the integrate tab on the two integrations).

Leaving all as is, it seems now i can actually load them in without App blowing up on combine rgb (3 channels each i think).  When i click calculate, or even create though, the final image says RGB in the info but it comes out black and white.  It should have color data.



   
ReplyQuote
 Nick
(@n-a-hardygmail-com)
White Dwarf
Joined: 8 years ago
Posts: 10
Topic starter  

@markm75

Yeah, that final step is weird.

I don't use luminance in the combine tool. I haven't got it to work well.

Maybe add the ha to red and green or so.

Sorry, can't help much further than this. My experience goes about this far.



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

I've asked Mabula to shine his light on this one, I have to practice with these combinations a bit more. I never had an issue with it, so not sure what is wrong here. I hope he's able to respond soon.



   
markm75 and Nick reacted
ReplyQuote
(@markm75)
Main Sequence Star
Joined: 7 years ago
Posts: 23
 
Posted by: @vincent-mod

I've asked Mabula to shine his light on this one, I have to practice with these combinations a bit more. I never had an issue with it, so not sure what is wrong here. I hope he's able to respond soon.

Thanks for this.

Just a side note.  In the combine rgb i had been trying to add an integrated frame.. i tried both registered combined with calibrated/normalized versions and each time it would add that frame as 3 separate luminance channels.  Without adding any ha data the result was a black and white image each time.  Now when i later tried the same add of an integrated frame but this time one that was further processed in APP, not just integration only, this time it added it automatically as red, then green, then blue and the result is color (again without adding the Ha portion).

I may just have this process out of order or out of whack since i'm still learning the ropes with the osc and ha and the combine tool, but thought this was worth mentioning.k



   
ReplyQuote
(@markm75)
Main Sequence Star
Joined: 7 years ago
Posts: 23
 

Ok i've found some success, listing the steps here (i think they are correct, though OSC ha comes in gray and only one channel for me when it works), no index errors or image mismatch errors:

 

Step1:  Do the Ha integration procedure per normal using all subs:

Check off force CFA on tab 0, then go through integration, fine tuning, cleanup, perfecting, save that image (ends up a 32bit grayscale image)

Step2:  Do the OSC regular color procedure per normal:
Check off force CFA on tab 0, then go through integration, fine tuning, cleanup, perfecting, save that image (ends up a 32bit RGB image)
 

Step3:

Bring the results of step1 and step2 (two files) into a new session, do NOT check off force CFA this time, uncheck autodetect masters
Open up Registration, click register, then click save registered files.

Step 4:

Open combine RGB
Open each of the files from Step3 that are ending in -reg

The color one should open 3 times, each for red green blue.
The Ha one should be set to either custom or Ha and only prompt one time (one channel) if this is correct.

Step 5:

Take the red slider on ha to 50% and the Xx top slider on Ha up a bit to increase the red hue’s in the image.



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

That seems a good flow actually, sorry for the confusion also on my part. I'm going to practice more on these types of data to be of better assistance. Plus the upcoming manual will help a lot. I do wonder if this CFA setting is causing a problem in a logical flow, did you actually select the HA algorithm on tab-0 for the HA data? That should produce the best HA signal and have only 1 channel.



   
ReplyQuote
Share: