Java out of range e...
 
Share:
Notifications
Clear all

UPDATE FROM MABULA

I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.

 

Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.

 

APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46.  Before I release it, I will make sure that everything is working properly and then I will release it.

Java out of range error

8 Posts
2 Users
0 Reactions
2,426 Views
(@jonathankimmitt)
Main Sequence Star
Joined: 5 years ago
Posts: 21
Topic starter  

Encountered error in module:
MultipleViewDistortionAndCalibrationTask

Error message:
java.lang.ArrayIndexOutOfBoundsException: Index 10 out of bounds for length 10

Cause:
Index 10 out of bounds for length 10
sN.a(Unknown Source)
sN.doInBackground(Unknown Source)
java.desktop/javax.swing.SwingWorker$1.call(Unknown Source)
java.base/java.util.concurrent.FutureTask.run(Unknown Source)

 

This was during registration of a mosaic in 2.0.0-beta6 release under OSX M1



   
ReplyQuote
Topic Tags
(@wvreeven)
Quasar
Joined: 8 years ago
Posts: 2134
 

@jonathankimmitt Hi Jonathan,

Thank you for reporting this. The stack trace alone unfortunately isn't enough to determine what happened. Can you reproduce this error? If yes, please let us know how. 

Thank you, Wouter



   
ReplyQuote
(@jonathankimmitt)
Main Sequence Star
Joined: 5 years ago
Posts: 21
Topic starter  

OK, I'll run it again and see what happens. However as far as I know there isn't a way to dump the settings of the engine for you to reproduce.

 



   
ReplyQuote
(@wvreeven)
Quasar
Joined: 8 years ago
Posts: 2134
 

@jonathankimmitt Correct, there isn't. However, if you can reproduce the error then we will ask you to upload your dataset and tell us which settings you used in each tab so we can try to reproduce ourselves and then debug to see what's going on.

 

Wouter



   
ReplyQuote
(@jonathankimmitt)
Main Sequence Star
Joined: 5 years ago
Posts: 21
Topic starter  

Yes, it is repeatable (see attachment)



   
ReplyQuote
(@wvreeven)
Quasar
Joined: 8 years ago
Posts: 2134
 
Posted by: @jonathankimmitt

Yes, it is repeatable (see attachment)

I don't see an attachment.

In any case, can you please tell me what data you are trying to integrate? How many lights do you have? What calibration data? Are all data raw or do you use calibration masters that were created with different software? Were all data taken with the same software?

 

Thanks, Wouter



   
ReplyQuote
(@jonathankimmitt)
Main Sequence Star
Joined: 5 years ago
Posts: 21
Topic starter  

The calibration masters were created with an earlier beta of the same software. But I can rerun with raw dark frames to see if it makes a difference.



   
ReplyQuote
(@jonathankimmitt)
Main Sequence Star
Joined: 5 years ago
Posts: 21
Topic starter  

I am integrating 690 10s lights from Stellina panorama mode.



   
ReplyQuote
Share: