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 just given this error message and have no idea what it means:
Astro Pixel Processor - 2.0.0-beta39
Oracle GraalVM 24.0.1+9.1 - Windows-64-bit
Encountered error in module:
StarAnalysisActionListener
Error message:
java.lang.NullPointerException: Cannot invoke "com.ariesproductions.myProgressMonitor.a.c()" because "this.a.a" is null
Cause:
Cannot invoke "com.ariesproductions.myProgressMonitor.a.c()" because "this.a.a" is null
astropixelprocessor@2.0.0-beta39/com.ariesproductions.starAnalysis.j.a(StarAnalysisActionListener.java:444)
astropixelprocessor@2.0.0-beta39/com.ariesproductions.starAnalysis.j.doInBackground(StarAnalysisActionListener.java:299)
java.desktop/javax.swing.SwingWorker$1.call(Unknown Source)
java.base/java.util.concurrent.FutureTask.run(Unknown Source)
Hi Julian @jaop2p,
Thank you very much reporting this error. I have not seen this error myself yet, but i have put the error on my issue list, to try to solve it 😉
I think that we can click the error message away, that all still works fine, or did it not? Did you see this error more frequently or just only once?
Mabula
Hi Mabula
The error message clicked away and the I was able to complete the stack. It has occured only once.
Thanks
Julian
Okay Julian @jaop2p,
Thank you very much. I have made a note of the error and I will try to avoid it from happening in the next release 😉
Mabula
