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.
Hi,
while trying to integrate 6.200 already normalized Ha mono frames(57MB each), APP crashes with the error see below.
Subframes are located on a 4TB Nvme with 1.4TB free space. OS is Kubuntu 24.04 LTS, CPU is a Ryzen9, RAM is 64GB DDR5 and 128GB Swap Space.
Integration Mode is drizzle with scale 2.0
What can I do?
Astro Pixel Processor - 2.0.0-beta39 Oracle GraalVM 24.0.1+9.1 - Linux-64-bit Encountered error in module: CreateLightsStackTask Error message: java.lang.NullPointerException: Cannot load from object array because "<local10>" is null Cause: Cannot load from object array because "<local10>" is null astropixelprocessor@2.0.0-beta39/com.ariesproductions.registration.ac.a(RegistrationTools.java:1696) astropixelprocessor@2.0.0-beta39/com.ariesproductions.integration.d.a(IntegrateLightsActionListener.java:1766) astropixelprocessor@2.0.0-beta39/com.ariesproductions.integration.d.doInBackground(IntegrateLightsActionListener.java:1129) java.desktop/javax.swing.SwingWorker$1.call(Unknown Source)
Best,
Juergen
Ouch, I would probably divide them into smaller stacks and and those stacks afterwards.
I made another attempt: Instead of pre-normalized frames I loaded (6.200) pre-registered frames and normalized and integrated them. Then it worked without errors.
Best,
Juergen
Hi,
while trying to integrate 6.200 already normalized Ha mono frames(57MB each), APP crashes with the error see below.
Subframes are located on a 4TB Nvme with 1.4TB free space. OS is Kubuntu 24.04 LTS, CPU is a Ryzen9, RAM is 64GB DDR5 and 128GB Swap Space.
Integration Mode is drizzle with scale 2.0
What can I do?
Astro Pixel Processor - 2.0.0-beta39 Oracle GraalVM 24.0.1+9.1 - Linux-64-bit Encountered error in module: CreateLightsStackTask Error message: java.lang.NullPointerException: Cannot load from object array because "<local10>" is null Cause: Cannot load from object array because "<local10>" is null astropixelprocessor@2.0.0-beta39/com.ariesproductions.registration.ac.a(RegistrationTools.java:1696) astropixelprocessor@2.0.0-beta39/com.ariesproductions.integration.d.a(IntegrateLightsActionListener.java:1766) astropixelprocessor@2.0.0-beta39/com.ariesproductions.integration.d.doInBackground(IntegrateLightsActionListener.java:1129) java.desktop/javax.swing.SwingWorker$1.call(Unknown Source)
Best,
Juergen
Hi Juergen @neubi,
Thank you very much for reporting this issue. I have opened an issue to investigate this.
Can you confirm that this error also occurs on your data if you load only 100 or 500 pre-normalized frames and only integrate them?
Mabula
Hi Mabula,
when integrating 249 pre-normalized frames of same size, this error does not occur.
Best,
Juergen
Hi @neubi,
Okay thanks, I will have a good look at the error message and our code now, to see if I can find an explanation 😉
I will get back to you.
Mabula
Hi Juergen @neubi,
I have found the issue. The issue will occur if you have loaded the pre-normalized frames and the remove the selected reference frame before starting integration. Then this error is thrown.Â
I will fix it now for the next release.
Thanks for reporting this.
Mabula
