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.
Hi, Im having real problems processing all my latest images. I use an ASI294MC Pro and have not had any problems in the past. I use NINA for acquisition and it all looks fine on there. However, when I include calibration frames in APP I get a severe halo in the final integration. It seems more the Flat frames rather than the Dark frames (bias arent used with the 294).
It has only recently been happening and I cant find a way around it. As an experiment Ive used old and new dark and flat frames (that have previously been fine) with the same outcome and its driving me mad. If I dont include calibration frames its then over exposed. Ive attached a screen shot of a final integration. You can ignore the dust bunny as I can usually edit any out and that was a result of me trying to look for dew on the sensor so I will correct that soon. I just cant figure it out. Its driving me mad.
Â
@richielisa Hi Richard, which calibration frames are you using exactly? You should use darks of the same temperature, gain, offset and exposure time as the lights as well as flats and dark flats with the same temperature, gain, offset and exposure time as the flats. If the exposure time of the darks or dark flats (or both) are different then you'll need bias frames as well.
Hi Wouter,
Â
Ive never used dark flats and I understand that I dont need bias with the ASI294MC Pro. As for the other frames I do exactly what you have said. In the past it has always been brilliant and its only just started doing this.
Â
Just trying some totally new flat frames to see if that helps. Other than that Im not sure what else is the problem.Â
@richielisa Hi Richard. For calibration of the flats, dark flats are needed. It is possible for APP to use the darks for that but then bias frames are needed to be able to properly scale the darks to the exposure time of the flats. If the darks have a different exposure time than the lights then bias frames are needed as well. In any other case scaling of the darks or dark flats cannot be done correctly which will introduce all kinds of artifacts that may well be an explanation for the result you got.
Hmmm.... I will have to look at how to do dark flats.....never done them before so if you can point me in the right direction it would be appreciated.
Â
Also, the new Flats Ive taken have worked well and I will need to throw the others away. Seems it was a flat problem. Thanks Wouter!
@richielisa Dark flats simply are darks with the same exposrue time as the flats. So if you take, say, 2 second flats then you'll need 2 second darks and you then load them as dark flats.
Glad to read that the new flats work!
