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.
(I did a forum search and did not find any topic relevant.)
I am a very new user to APP (3/21/21) and like the quickness of processing through 'integration'. Immediately prior to the imaging session I took 20 'sky flats' and already had 20 'darks' with a similar exposure/temp as the 'lights/ and 20 'bias' frames.
I ran through the APP sequence and it appeared the 'flats' were not subtracted out and in fact, looking at the images below, it appears the 'flats' were add to the light image. I used the default settings for each of the processes.
The image on the left is the result of using flats and the image on the right is without flats.
There was a 'Master Flat' and a 'Bad Pixel Map' created and applied per the file window.
What did I do wrong?
My imaging equipment is an ASI294MC-Pro taken using SGPro 4.0.0.661.
@mikisj Hi Michael. If inverting the flats gives the result that you expect then that probably means that your flats are much too dim and need to be a lot brighter. Can you post a screenshot of APP with a flat loaded in it showing the histogram with the "stretch" checkbox unchecked? In any case, you should not need to invert the flats to be able to use them with APP.
I am a new user, so be gentle - how do I load a single 'Flat' into APP?
I am using Dusk Sky Flats and the ADU is ~23,000 for a well depth of 63,000. The Flats should be bright enough.
When you load in the flats, you double-click on one in the list and it is shown in the preview. Would be nice to see a screenshot of that and also, when you look at the right hand side where there is a stretch preset (it says 15% BG standard), select "no stretch" there. That will show the actual histogram of the flat without stretching and that peak should be clear of the left side of the histogram (and from the right), but doesn't necessarily need to be in the middle.
It may also be interesting to see what happens when you use bias frames here I think. The bias signal needs to be corrected from the flats for them to work well, APP does this automatically when you have bias or darkflats.
@mikisj Thanks very much Michael and sorry for jumping deeply into technicalities straight away. Your camera is a color camera and APP should be able to turn the black and white images into color images automatically. To do so, go to tab 1 and select RGGB in the pattern drop down and then enable "force Bayer/X-Trans CFA". Then go back to tab 1 and double click a flat again as Vincent explained. You should see that the peak to the right is for the green color channel and the other peak for blue and red. However, I suspect that that may not be the case for you and that the left peak is for green. Can you follow these steps please and post a new screenshot?
Hi Michael @mikisj & @wvreeven,
First of all, flats are never subtracted/added, the light frames are divided by flats. Vignetting is a multiplicative process on the incoming light. So to correct that, you need to have a model of that vignetting (our flats) and to correct that problem, you need to divide the original with the model to remove the problem.
I have never come across a situation where you would need to invert flats to make them work, so that is not very logical at all to me, I suspect something else is the problem here.
So, your camera is a OSC camera and you obviously need to enable Force CFA to have APP interpret the data correctly, right? This is because relevant metadata is not in your fits frames apparently, this is caused by the capture software most likely.
Now, what happens when you process your data with the NOT-inverted flats with this setting enabled? So make new masters now and integrate all data. Is then everything okay?
If not, I think we should have a closer look at your data 😉
Mabula
With apologies. I had another AP'er look at my raw images (lights, Flats, Darks) and it was determined I had really bad date.Â
Thank you for taking the time to answer my query.