Null Pointer except...
 
Share:

Null Pointer exception  

Page 1 / 2
  RSS

(@gotak)
White Dwarf Customer
Joined: 1 year ago
Posts: 15
August 12, 2019 23:24  

Trying to integrate a mosaic and getting null pointer exception.

Encountered error in module:
LanczosResamplerWorker

Error message:
java.lang.NullPointerException

Cause:
null
no trace

 

08:17:52 - IMAGE CONVERTER: image conversion not needed, data is already normalized...
08:18:06 - GENERAL IMAGE LOADER: frame E:\Photos\DSS\M31_Mosaic\Light\http___www.astrobin.com_360949__nc=user-5_150sec_1x1__frame19.fit was loaded successfully
08:18:07 - 6) INTEGRATE: integrate light frames: loaded frame 116 of 117 frames
08:18:27 - 6) INTEGRATE: integrate light frames: wrote frame: 116 to file mapper
08:18:38 - 6) INTEGRATE: integrate light frames: wrote weights of frame: 116 to file mapper
08:18:38 - GENERAL IMAGE LOADER: loading frame E:\Photos\DSS\M31_Mosaic\Light\http___www.astrobin.com_360949__nc=user-5_150sec_1x1__frame20.fit
08:18:41 - 2) CALIBRATE: Adaptive Data Pedestal: enabled
08:18:41 - 2) CALIBRATE: Adaptive Data Pedestal set at: 1.371E-01
08:18:41 - 2) CALIBRATE: WARNING !!! we have detected a possible sensor offset issue between the MasterBias and the Masterdark !
08:18:41 - 2) CALIBRATE: WARNING !!! the MasterBias has a median value of: 4.172E-02 for channel 1
08:18:41 - 2) CALIBRATE: WARNING !!! the MasterDark has a median value of: 3.858E-02 for channel 1
08:18:41 - 2) CALIBRATE: WARNING !!! normally, the median value of the MasterDark should be the same or larger than the median value of the MasterBias
08:18:41 - 2) CALIBRATE: WARNING !!! because a dark should always contain the entire bias signal plus the dark current and possible amp glow signals
08:18:41 - 2) CALIBRATE: WARNING !!! some CMOS sensors however exhibit this behaviour due to CMOS technology.
08:18:41 - 2) CALIBRATE: WARNING !!! we have detected a possible sensor offset issue between the MasterBias and the Masterdark !
08:18:41 - 2) CALIBRATE: WARNING !!! the MasterBias has a median value of: 4.160E-02 for channel 2
08:18:41 - 2) CALIBRATE: WARNING !!! the MasterDark has a median value of: 3.833E-02 for channel 2
08:18:41 - 2) CALIBRATE: WARNING !!! normally, the median value of the MasterDark should be the same or larger than the median value of the MasterBias
08:18:41 - 2) CALIBRATE: WARNING !!! because a dark should always contain the entire bias signal plus the dark current and possible amp glow signals
08:18:41 - 2) CALIBRATE: WARNING !!! some CMOS sensors however exhibit this behaviour due to CMOS technology.
08:18:41 - 2) CALIBRATE: WARNING !!! we have detected a possible sensor offset issue between the MasterBias and the Masterdark !
08:18:41 - 2) CALIBRATE: WARNING !!! the MasterBias has a median value of: 4.162E-02 for channel 3
08:18:41 - 2) CALIBRATE: WARNING !!! the MasterDark has a median value of: 3.853E-02 for channel 3
08:18:41 - 2) CALIBRATE: WARNING !!! normally, the median value of the MasterDark should be the same or larger than the median value of the MasterBias
08:18:41 - 2) CALIBRATE: WARNING !!! because a dark should always contain the entire bias signal plus the dark current and possible amp glow signals
08:18:41 - 2) CALIBRATE: WARNING !!! some CMOS sensors however exhibit this behaviour due to CMOS technology.
08:18:41 - 2) CALIBRATE: WARNING !!! we have detected a possible sensor offset issue between the MasterBias and the Masterdark !
08:18:41 - 2) CALIBRATE: WARNING !!! the MasterBias has a median value of: 4.174E-02 for channel 4
08:18:41 - 2) CALIBRATE: WARNING !!! the MasterDark has a median value of: 3.884E-02 for channel 4
08:18:41 - 2) CALIBRATE: WARNING !!! normally, the median value of the MasterDark should be the same or larger than the median value of the MasterBias
08:18:41 - 2) CALIBRATE: WARNING !!! because a dark should always contain the entire bias signal plus the dark current and possible amp glow signals
08:18:41 - 2) CALIBRATE: WARNING !!! some CMOS sensors however exhibit this behaviour due to CMOS technology.
08:18:41 - 2) CALIBRATE: performing calibration in 32bits normalized floats...
08:18:41 - 2) CALIBRATE: converting data to 32bits normalized floats...
08:18:45 - IMAGE CONVERTER: image conversion not needed, data is already normalized...
17:23:26 - GENERAL IMAGE LOADER: cancelled loading frame E:\Photos\DSS\M31_Mosaic\Light\http___www.astrobin.com_360949__nc=user-5_150sec_1x1__frame20.fit
17:23:26 - 6) INTEGRATE: integrate light frames: integration task was cancelled
17:23:26 - MEMORY TO FILE MAPPER: closing memory to file mapper...E:\Photos\APP\Light.dat
17:23:26 - MEMORY TO FILE MAPPER: removing mapped file
17:23:28 - MEMORY TO FILE MAPPER: closing memory to file mapper...E:\Photos\APP\Light.dat
17:23:28 - MEMORY TO FILE MAPPER: removing mapped file
17:23:28 - MEMORY TO FILE MAPPER: closed succesfully
17:23:28 - MEMORY TO FILE MAPPER: closing memory to file mapper...E:\Photos\APP\Light-weights.dat
17:23:28 - MEMORY TO FILE MAPPER: removing mapped file
17:23:28 - MEMORY TO FILE MAPPER: closed succesfully
17:23:28 - 6) INTEGRATE: integrate light frames: integration task finished
17:23:28 - FRAME DETAILS UPDATER: starting...
17:23:28 - FRAME DETAILS UPDATER: no new frames to add
17:23:28 - FRAME DETAILS UPDATER: rebuilding all frame details...
17:23:28 - FRAME DETAILS UPDATER: checking if frames were identified earlier...
17:23:28 - FRAME DETAILS UPDATER: adding frame marks...
17:23:28 - FRAME DETAILS UPDATER: updated succesfully

 

This topic was modified 1 month ago by Vincent Groenewold - Moderator
This topic was modified 1 month ago by Mabula Haverkamp - Admin

ReplyQuote
(@gotak)
White Dwarf Customer
Joined: 1 year ago
Posts: 15
August 13, 2019 02:56  

Same thing with bilinear. 


ReplyQuote
(@vincent-mod)
Galaxy Moderator
Joined: 2 years ago
Posts: 725
August 13, 2019 11:06  

Hi @gotak,

Could you describe which steps you took before the error appears and at what stage exactly (during normalization, registration...)? Thanks.


ReplyQuote
(@gotak)
White Dwarf Customer
Joined: 1 year ago
Posts: 15
August 15, 2019 05:33  
  • 116 frames from a 163C camera over 6 sections of the skies (about 20 frame for each section)
  • 10% overlap in the frames
  • Everything works fine up to integration. Integration fails at it looks like the part where it starts pixel interpolation?

Not sure what else I can add to this.

Is there a location for the full log files? 


ReplyQuote
(@vincent-mod)
Galaxy Moderator
Joined: 2 years ago
Posts: 725
August 15, 2019 10:45  

The error is that of java, so the log won't really help in this case. Could you maybe upload like 5 frames per section for me to try and have a look?

You can upload them to the APP server, using login and password "appuser" (without the "). Please create a folder with your name on it first, thanks!

 


ReplyQuote
(@gotak)
White Dwarf Customer
Joined: 1 year ago
Posts: 15
August 16, 2019 02:56  

Uploading now.


ReplyQuote
(@vincent-mod)
Galaxy Moderator
Joined: 2 years ago
Posts: 725
August 16, 2019 10:42  

Downloading. I'll try to have a look somewhere today.


ReplyQuote
(@jamesmrobins)
Brown Dwarf Customer
Joined: 1 year ago
Posts: 6
August 18, 2019 10:15  

I also get this error, on as few as a 2 panel mosaic. It happens during integration. Changing the pixel interpolation method has no impact even though this is where the error appears to be. Screen shots attached

Screen Shot 2019 08 18 at 6.09.26 pm
Screen Shot 2019 08 18 at 6.08.05 pm

 


ReplyQuote
(@vincent-mod)
Galaxy Moderator
Joined: 2 years ago
Posts: 725
August 18, 2019 11:20  

Ok, thanks for letting us know! I didn't get the error as of yet, but Mabula knows about it and is going to investigate further and hopefully fix it for the next release.

@jamesmrobins it would be great if you could share some of the data as well, Mabula is then able to have a better look to reproduce the issue.

This post was modified 1 month ago by Vincent Groenewold - Moderator

ReplyQuote
(@jamesmrobins)
Brown Dwarf Customer
Joined: 1 year ago
Posts: 6
August 19, 2019 10:36  

Uploaded. The panes are each stacks of 4 images.

Settings as follows

REGISTRATION:

quadrilaterals, scale start 1, scale stop 10, flip descriptors on, use dynamic distortion correction on, same camera/optics off, mosaic mode.

NORMALIZE:

Regular, multiply scale, neutralise background off

INTEGRATE

equal weight, media, 1st LNC 1 iteration, MBB 25%, scale 0.3


(@vincent-mod)
Galaxy Moderator
Joined: 2 years ago
Posts: 725
August 19, 2019 10:40  

Greatly appreciated James! I'll let Mabula know.


ReplyQuote
(@jamesmrobins)
Brown Dwarf Customer
Joined: 1 year ago
Posts: 6
August 19, 2019 11:20  

I am wondering if it is memory related. I have 12GB allocated to APP. If I build my stacks with a reduced scale then it sometimes works... my results are inconsistent on this, I can't seem to nail it down.


ReplyQuote
(@vincent-mod)
Galaxy Moderator
Joined: 2 years ago
Posts: 725
August 19, 2019 13:19  

Yeah it would be great to have a consistent bug, way easier to find. But I think Mabula could try to avoid a null pointer situation. Which platform are you using btw?


ReplyQuote
(@mabula-admin)
Quasar Admin
Joined: 2 years ago
Posts: 2127
August 20, 2019 00:32  

Hi @gotak, @jamesmrobins & @vincent-mod,

I am investigating this issue right now 😉 thank you very much for uploading your data.

I will report back as soon as I have reproduced and solved the issue.

Kind regards,

Mabula

Main developer of Astro Pixel Processor and owner of Aries Productions


ReplyQuote
(@mabula-admin)
Quasar Admin
Joined: 2 years ago
Posts: 2127
August 20, 2019 01:51  

Hi @gotak, @jamesmrobins & @vincent-mod,

I have run several tests using a SSD harddrive in my laptop, the nullpointer never happens whatever setting i use from registration to integration. So I am starting to suspect an issue with using either an external drive or using a network share.

Can you both give addtional information on where the data is? External/network?

And where have you set the work directory?

Maybe that will explain where the issue is coming from. In the mean time I will continue investigating 😉 with additional test.

Kind regards,

Mabula

Main developer of Astro Pixel Processor and owner of Aries Productions


ReplyQuote
(@gotak)
White Dwarf Customer
Joined: 1 year ago
Posts: 15
August 20, 2019 02:04  
Posted by: @mabula-admin

Hi @gotak, @jamesmrobins & @vincent-mod,

I have run several tests using a SSD harddrive in my laptop, the nullpointer never happens whatever setting i use from registration to integration. So I am starting to suspect an issue with using either an external drive or using a network share.

Can you both give addtional information on where the data is? External/network?

And where have you set the work directory?

Maybe that will explain where the issue is coming from. In the mean time I will continue investigating 😉 with additional test.

Kind regards,

Mabula

Local drive in raid mirroring array on two 3tb conventional drives.


ReplyQuote
(@mabula-admin)
Quasar Admin
Joined: 2 years ago
Posts: 2127
August 20, 2019 02:37  

Hi @gotak,

Okay, thanks, then I think it's safe to assume that this issue is not related to network shares/external drives.

Can you share more on the settings that you use that trigger the error? Does the error always occur? I mean each time that you try to process the data?

On which Operating System does it happen?

Thanks in advance 😉

Mabula

Main developer of Astro Pixel Processor and owner of Aries Productions


ReplyQuote
(@gotak)
White Dwarf Customer
Joined: 1 year ago
Posts: 15
August 20, 2019 02:49  

@mabula-admin

I am on windows 10.

I tried a few different thing and it always seems to happen.

Do you need the full set of settings? I'll have to go and try to regenerate them. Is there a log somewhere that would provide the settings?

 


ReplyQuote
(@jamesmrobins)
Brown Dwarf Customer
Joined: 1 year ago
Posts: 6
August 20, 2019 10:58  

I am on OSX, data is in a network share with local working directory. 

The error occurs consistently for a given set of data - if it is going to happen it always happens with that data. But if I change the data a bit eg reduce the number of input files or scale down the input files then sometimes I can make the error go away. I can't get this workaround to be successful every time however. 


ReplyQuote
(@mabula-admin)
Quasar Admin
Joined: 2 years ago
Posts: 2127
August 20, 2019 18:43  

Hi @gotak & @jamesmrobins & @vincent-mod,

I have run both your datasets many times now and I never get the error unfortunately, so I suspect that I am not doing things exactly the way you are doing it. To be able to solve this issue I would need to know exactly what you are doing.

@gotak, in your first post we can see that you are using Master calibration frames.. which were not part of your upload. I have only part of your light frames. Maybe the issue is related to the calibration masters? Did you verify calibration is looking okay with the L-calibrated image viewer mode? What happens if you process your lights without calibration frames? Does the error still occur?

It would really help me if you can both provide me with a step by step record of what you are doing with the data that you sent me that will give the error on your computer, so I will be able to reproduce this error and solve it 😉

This is gotak's data and it processes without problems whatever I do until now:

So no calibration frames are used since I don't have these and this is just a small subset of gotak's data..

Gotak data no issue

Kind regards,

Mabula

Main developer of Astro Pixel Processor and owner of Aries Productions


ReplyQuote
Page 1 / 2
Share: