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.
Looking for help with error message when calibrating
not sure if this helps but I am experiencing a similar (but not exactly the same) error with beta 37 which I have not seen before:
This occurs (sporadically) after a normal integration sequence when I go back to save the calibrated lights. The lights save fine but then the console seems to keep on doing 'something' in the background for some time and eventually this error is produced.
It doesn't seem to have have any real consequences (at least for me) as the calibrated lights are saved OK before any of this happens...
I was using an M1 MacBook, and I've figured out what happened—100% user error on my part. Scale master dark was selected for the calibration, which requires the master bias. I had mapped the master bias file to the bad pixel map by mistake.
Regarding your last post, I may be wrong but my understanding is that a Master Dark used for Scaling must be created with Dark frames and Bias frames, not using a Master Bias file????
I was using an M1 MacBook, and I've figured out what happened—100% user error on my part. Scale master dark was selected for the calibration, which requires the master bias. I had mapped the master bias file to the bad pixel map by mistake.
TY to all who considered this.
Hi Kevin @kevinkalikimaka, that is great. Thank you very much for your feedback. I did implement a fix for this error and it should not happen again with 2.0.0-beta38 or later 😉
@jhart that is not correct, to have scaling working on the masterDark, the MasterBias must be present. The MasterBias is subtracted form the MasterDark and then a noise analysis on the subtracted MasterDark determines the scaling factor(s).
not sure if this helps but I am experiencing a similar (but not exactly the same) error with beta 37 which I have not seen before:
This occurs (sporadically) after a normal integration sequence when I go back to save the calibrated lights. The lights save fine but then the console seems to keep on doing 'something' in the background for some time and eventually this error is produced.
It doesn't seem to have have any real consequences (at least for me) as the calibrated lights are saved OK before any of this happens...
