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.
The quality scores I see during "analyze stars" often vary substantially from one subframe to the next. For example, I am doing a data reduction right now. Just saw a quality score of 182. But then a quality score of 45 on a subsequent frame. Should I be rejecting the lower score frames during integration? Or do even the lower quality frames add light to the result and so including those should still improve the final integration?
See Mabula's comments here: https://www.astropixelprocessor.com/community/main-forum/is-fwhm-the-best-measure-to-use/#post-30695
Looked at Mabula's comments. He refers to looking at the FITS header of the integrated file, and specifically mentions, for example, the Signal to Noise Ratio. I looked at the header using MaxIM DL Essentials. I see the total exposure time and other data, butI do not see the SNR listed. Do I need a different software to see that information?
With the integration open in APP, I think all of SNR and other FITS header data are displayed in the Header/Metadata window along side the image display window.
Ah yes. I had not noticed it there since it needs to be expanded to see the information. But I see the same header information as I see in MaxIm DL Essentials. I cannot see a SNR I have attached a screen shot showing the expanded header information in APP. Is the SNR there and I am simply not seeing it?
I think if you upgrade to the latest 2.0 beta version of APP, you will get a much more robust FITS header for your integrations, including SNR data.
I have been avoiding doing that because it is in beta. I suppose If I have trouble with the beta version I can revert to the last known stable version.
you can easily switch back and forth with the betas by just reinstall the desired version... For my purposes the beta29 is stable...
I have installed beta29. I was happy at first to see I was still able to retain the previous stable version after installation of the beta. Unfortunately, if I try to launch the earlier version, I have to re-enter the license info. Then if I try to launch beta 29 again, I must enter the license info yet again. Too bad entering the license info once into each version does not allow both versions to remain active at the same time.
Ok. I only< switched between the 2.0.0 betas. There it was not necessary to enter the code again. But as I wrote I had never problems with beta29.
And I installed only one version at a time.
