NegativeArraySizeEx...
 
Share:
Notifications
Clear all

2023-09-16: APP 2.0.0-beta23 has been released !

Improved performance again, CMD-A now works in macOS File Chooser, big improvement for bad column cosmetic correction, solved several bugs

We are very close now to  releasing APP 2.0.0 stable with a complete printable manual...

Astro Pixel Processor Windows 64-bit

Astro Pixel Processor macOS Intel 64-bit

Astro Pixel Processor macOS Apple M Silicon 64-bit

Astro Pixel Processor Linux DEB 64-bit

Astro Pixel Processor Linux RPM 64-bit

NegativeArraySizeException error on combine RGB tool

13 Posts
3 Users
0 Likes
211 Views
(@uu_vee)
White Dwarf
Joined: 1 year ago
Posts: 12
Topic starter  

Hi I am trying to combine 3 already integrated and registered frames into the RGB combine tool and have received the following error when re-calculate is hit.

Screenshot 2022 11 28 213420

Further info - The 3 frames are from two different cameras with different frame sizes [OSC and Mono] so on the registration page checked use dynamic distortion correction and unchecked same camera/optics. On testing these frames integrate without any issues, I juts cannot RGB combine them.

Thank you

rgds kurt


   
ReplyQuote
(@uu_vee)
White Dwarf
Joined: 1 year ago
Posts: 12
Topic starter  

Hi has anyone seen this error? I have recieved a second error same message - this time 2 master frames which have been star analysed and registered and then on saving the registered files one file saves successfully, the second generates the message below:

image

   
ReplyQuote
(@wvreeven)
Quasar
Joined: 5 years ago
Posts: 2118
 

@uu_vee Hi Kurt,

Which version of APP are you using? And on which OS are you?

Thanks, Wouter


   
ReplyQuote
(@uu_vee)
White Dwarf
Joined: 1 year ago
Posts: 12
Topic starter  

@wvreeven Hi Wouter running APP v1.083.4 on windows 10 pro v21H2 


   
ReplyQuote
(@wvreeven)
Quasar
Joined: 5 years ago
Posts: 2118
 

@uu_vee Hi Kurt,

Can you upload the files that produce the error in Combine RGB to our file server? Upload instructions are at the top of any forum page. Please create a folder called uu_vee_combine_rgb and put your files in there. Then let me know when the upload is done and I will see if I can find out what's going on. Thanks!


   
ReplyQuote
(@uu_vee)
White Dwarf
Joined: 1 year ago
Posts: 12
Topic starter  

@wvreeven Hi Wouter thank you for your help.

I tried to do a couple of things to see if I could resolve the issue. To set context I have 2 master files which are the summary of previously integrated frames. One master file a gray file shot with AS1600MM pro the other RGB with the ASI294MC pro. Same optics / set up were used

 

The original master file for the 1600MM was really "messy" due to multiple sessions and the camera being in different positions so I cropped this to use for this purpose.

I have uploaded these 2 files into the folder named above.

 

The last attempt to register these 2 files; the star reg performed ok; the first part of registration appeared to be OK without any errors, but on saving the files i had this message:

image

The files saved though [the resulting new reg file sizes were very large - up to 7GB] and the resulting images were very interesting to say the least! - I did not upload these due to the file sizes but here are two screenshots:

image
image

register tab settings used:

image
image

   
ReplyQuote
(@wvreeven)
Quasar
Joined: 5 years ago
Posts: 2118
 

@uu_vee Please enable advanced mode in tab 5 and see if that helps.


   
ReplyQuote
(@uu_vee)
White Dwarf
Joined: 1 year ago
Posts: 12
Topic starter  

@wvreeven Hi thanks for your response. I'm a little confused here as this issue arises during the register process; save registered frames [Tab 4] which precedes Normalise [Tab 5] 

My plan here is to take the registered frames to do further processing and try some combination outcomes rather than completing integration.

rgds

kurt


   
ReplyQuote
(@wvreeven)
Quasar
Joined: 5 years ago
Posts: 2118
 
Posted by: @uu_vee

The last attempt to register these 2 files; the star reg performed ok; the first part of registration appeared to be OK without any errors, but on saving the files i had this message:

image

This simply means that the resulting image is too large for APP to be able to process. How much RAM do you have allocated to APP? You can see (and configure) this by clicking the CFG button to the upper left of the APP screen.

Posted by: @uu_vee

Hi thanks for your response. I'm a little confused here as this issue arises during the register process; save registered frames [Tab 4] which precedes Normalise [Tab 5] 

Sorry for my previous short answer. It was referring to the distorted images that were produced by APP. So my question remains: did you enable advanced mode in tab 5?


   
ReplyQuote
(@wvreeven)
Quasar
Joined: 5 years ago
Posts: 2118
 
Posted by: @uu_vee

I tried to do a couple of things to see if I could resolve the issue. To set context I have 2 master files which are the summary of previously integrated frames. One master file a gray file shot with AS1600MM pro the other RGB with the ASI294MC pro. Same optics / set up were used

 

The original master file for the 1600MM was really "messy" due to multiple sessions and the camera being in different positions so I cropped this to use for this purpose.

I have uploaded these 2 files into the folder named above.

Thanks for uploading the files. I loaded the two lights in APP 2.0.0.-beta8 and normalized them. All I needed to do was uncheck "same camera and optics" in tab 4. When trying to save them as FITS files, I get an error. I'll check with Mabula to see what the cause is.


   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 6 years ago
Posts: 3812
 

Hi Kurt @uu_vee,

Thank you for reporting this, I will test and fix as soon as possible 😉

Did you also try this in 2.0.0-beta9 ?

Mabula


   
ReplyQuote
(@uu_vee)
White Dwarf
Joined: 1 year ago
Posts: 12
Topic starter  

@mabula-admin Hi Mabula no; I am only using v 1.083.4

 

Rgds

Kurt


   
ReplyQuote
(@uu_vee)
White Dwarf
Joined: 1 year ago
Posts: 12
Topic starter  

@wvreeven Hi Wouter re you question on RAM; system has 32GB and I have allocated 30GB to APP. I would hope this would not be the issue! Thanks for the update on your tests with the actual files.

 

Rgds

Kurt


   
ReplyQuote
Share: