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.
Those errors are weird and should be fixed. I have never seen this in all my testing to be honest. Is this happening with this dataset each time? Or did these problems only happen once?
If it happens each time, we need to see the data so we can fix it properly, please upload the data here then:
I have fixed the issue in FindBestRegistrationModel. I will work now on the other bug in FrameDataCalibration. Can you possible upload your data so I can solve this properly?
Fixed ArrayIndexOutOfBoundsException in FindBestRegistrationModel
As reported here https://www.astropixelprocessor.com/community/main-forum/arrayindexoutofboundsexception-in-findbestregistrationmodel-while-registering/#post-34227 an ArrayIndexOutOfBoundsException could be thrown when registering in the FindBestRegistrationModel module. The issue will be caused when dynamic distortion correction is enabled. When disabled all works as expected. The issue would manifest if APP tries to calculate distortion correction on data that really does not need it for already perfect registration. The issue is now solved and prevented by simply disabling distortion correction completely in the 2-view registration phase on data that has very little movement in the stars between the images. The user can simply leave distortion correction enabled, internally, APP will disable it for the specific registration task.
Thank you dear Mabula. That’s good News. Please tell me whats kind of info do you need me to upload? I have been experience this with any of my integrations. Didn’t happened with older versión. I changed with the 40 and 39 versión and happened similar. But I know you will fix it
This post was modified 5 months ago by hector Duran
Please make a folder with your name and issue like: Hector-CalibrationError
and upload the dataset into that folder. Then please let me know once you have completed the upload. I will make sure the issue will be properly fixed then.
I already located the error to the Bias calibration. Do you load many bias frames to make a masterbias, or do you load perhaps multiple masterbias frames? Please share as much detail as you can, so I can repeat the error on solve it with 100% certainty.
