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.
Encountered error in module:
AlignAndResampler
Error message:
java.lang.ArrayIndexOutOfBoundsException: Invalid coordinates
Cause:
Invalid coordinates
java.awt.image.SampleModel.getSamples(SampleModel.java:1037)
java.awt.image.Raster.getSamples(Raster.java:1743)
d.a(Unknown Source)
d.doInBackground(Unknown Source)
This has happened a few times that I didn't report because I thought it was a random failure, but seems to be somewhat repeatable. It occurs when I run the steps up through Normalize, then go into the file list and de-select frames that are worse for one reason or another (elongated stars, low quality, few stars, etc). Then I click the Integrate step, and get this error.
I'm running version 1.083.4.
Thanks for any help or suggestions! I will try the new beta to see if it does the same thing.
Would you be able to test again using beta4 of APP 2.0? You can find the download on top of the forum.
I've done two batches with Beta4, and have not come across that error again. So tentatively, I'd say it's fixed.
