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.
I've getting the following dialog come up (Encountered error in module Integrator)
Encountered error in module:
Integrator
Error message:
java.lang.NullPointerException
Cause:
null
pj.a(Unknown Source)
pj.a(Unknown Source)
pj.doInBackground(Unknown Source)
javax.swing.SwingWorker$1.call(SwingWorker.java:295)
And then it just bombs out on me. All steps pretty much with defaults except on one frame Star Analysis failed and I deselected and removed that frame. I chose Mosaic Registration and accepted the dialog suggestions that go along with that.
The console just shows the following:
2:26:39 - 6) INTEGRATE: integration: total exposure time: 7020 seconds = 117.00 minutes = 1.950 hours
12:28:39 - FRAME DETAILS UPDATER: starting...
12:28:39 - FRAME DETAILS UPDATER: no new frames to add
12:28:39 - FRAME DETAILS UPDATER: rebuilding all frame details...
12:28:39 - FRAME DETAILS UPDATER: checking if frames were identified earlier...
12:28:39 - FRAME DETAILS UPDATER: updated succesfully
12:28:39 - CONSTRUCT FRAME DETAILS LIST: starting...
12:28:39 - CONSTRUCT FRAME DETAILS LIST: sorting frames...
12:28:39 - CONSTRUCT FRAME DETAILS LIST: Fixing file arrays...
12:28:39 - CONSTRUCT FRAME DETAILS LIST: numbering frames...
12:28:39 - CONSTRUCT FRAME DETAILS LIST: adding frame marks...
12:28:40 - CONSTRUCT FRAME DETAILS LIST: finished
Any idea of the cause? Let me know if there is anything to try, I can post a video of the whole process to youtube if it is going to help at all.
Oh, ok, so Mabula says this will be fixed in the next version:
Â
https://www.astropixelprocessor.com/community/main-forum/error-in-new-1-078-version/
Hopefully it's the same thing yes, but there indeed is a bug unfortunately that is fixed for the next release.
Hopefully it's the same thing yes, but there indeed is a bug unfortunately that is fixed for the next release.
I can confirm that it happens only on 1.0.78 (Linux in my case), I did the exact same mosaic task on my laptop (Windows 1.0.77, not Linux) and it went through and completed integration fine.
I do with there was a save state/save project, so that I didn't have to re-run Calibration, Registration etc... on the laptop, but in any case, I have a workaround until we see 1.0.79 surface.
Very interesting. I reproduced one of these crashes on MacOS as well (somewhat similar to Linux) so it might be correlated. I'll keep this in mind, thanks!
