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 am on 1.067. I always just use default settings except for 6). Got a message that APP could not detects stars and that I had to lower kappa value. in 3). I then started playing around with the values but with no success. Could it be calibration data that perhaps need to be redone?
My humble apologies. APP works perfect! I really do not know what I did wrong. I just closed down everything and started from scratch and all worked out 100%. This was just a test in Lum on NGC 55 to see what I can get if I spend some time on it. Your prompt assistance are much appreciated and apologies for wasting time on this.
My humble apologies. APP works perfect! I really do not know what I did wrong. I just closed down everything and started from scratch and all worked out 100%. This was just a test in Lum on NGC 55 to see what I can get if I spend some time on it. Your prompt assistance are much appreciated and apologies for wasting time on this.
I am glad that all is allright now. If such a thing happens again, do check the calibrated data with the l-calirbated image viewer mode. That is very usefull to point out a problem with the data or the calibration frames 😉
