JAVA error failure ...
 
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 error failure when loading final Integration image - APP crashes out

4 Posts
3 Users
0 Reactions
2,195 Views
(@rsbuckell)
White Dwarf
Joined: 9 years ago
Posts: 8
Topic starter  

Running MAC Ventura 13.1 on an M1 Mac.  APP 2.0 Beta13.  Ran a 4 panel mosaic which took 5 days to integrate.  Then on loading final Integrated image JAVA error failure.  APP crashed out and I lost all data in original process.  On loading only the final Integrated image the same thing happened twice.  Cannot load image at all in APP.  I have copied the error process to notepad and can upload if required.



   
ReplyQuote
(@mabula-admin)
Universe Admin
Joined: 9 years ago
Posts: 5379
 

Hi @rsbuckell,

That sounds like the resulting image is too big in image dimensions and you are getting an out of memory crash probably. Do you have any idea how large the integrated file is? What focal length was used?

If it took 5 days, then you are creating the mosaic not according to our recommendations here:

https://www.astropixelprocessor.com/mosaic-tutorial-milky-way-to-rho-ophiuchi-by-mabula/

The most efficient and most robust way to register any data set as a mosaic is to first integrate the individual mosaic panels. Then register the mosaic using only the individual integrated panels. This holds for other mosaics as well. Don’t try to create a mosaic out of 100s of indivdual frames. First create the mosaic panels.

If you did, and it still took 5 days, then something must be way off in terms of APP being able to register the frames correctly. In that case, did you try different settings in 4) Register?

Mabula



   
ReplyQuote
(@rsbuckell)
White Dwarf
Joined: 9 years ago
Posts: 8
Topic starter  

Many thanks for the fast reply.  The total size of the final image was 1.6GB. I simply cleared the data and reloaded the final integration and in v1.075 without any issues and it was complete.  I didn't follow the tutorial though and will give that a go and report back if necessary.  



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

It may be a good idea to update to our latest beta version (you can find it on top of the forum). This is way faster and has better memory management.



   
ReplyQuote
Share: