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 saw this interesting video about the analysis of a flat panel
In a nutshell you take a flat image and divide it by its 2nd degree Polynomial Surface Fit, then by looking at the histogram, specially the standard deviation vs the mean will give you an idea how "flat" your panel really is.
My flat panel is illuminated from the sides, which makes it darker on the center, you can only notice this with very slow shutter speeds. This specific case of vignetting effect is a property of the panel and not of my image train, my image train will introduce a second layer of vignetting.
My panel light source is even to around 1.1%.
As this "second" layer of vignetting is only present when I use my flat panel a not on my data, is it possible to correct for it and leave only the vignetting from the imaging train ?
