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.
Hello again with a new "issue?". I try out to drizzle my new data from sadr region and surroundings. I show you a few screenshots from the settings and in my opinion issues with drizzle in APP.
Any idea? Is it just a wrong setting?
@tobiasthale Hi. I'm not that drizzle specialist, but I think you have tom play with "droplet size". I think 0.5 is too small. I usualy work with values around 0.8, depending on the quality of my lights.
Hi,
I agree with Juergen. Think of fine rain falling on a dry pavement. Unless the drizzle is very persistent not every part of a paving slab will get wetted.
I thing this is what has happened with your drizzled image. Not every pixel in every channel of the output grid has received data from the available input files, hence eg the red dots etc: the corresponding pixels in blue and green channels have not picked up any signal. As Mabula has often stated drizzle can cause a major injection of noise and really requires reasonably plentiful input data.
If you are using say a drizzle value of 2, I would suggest you experiment with a lower value, say 1.5, and increase the droplet size.
When I first started experimenting with drizzle I got similar weird results but with persistence it can be made to work.
I've also found it informative to play with Russ Croman's MTF Analyser ( https://www.rc-astro.com/mtf-analyzer/) to gain an idea of what amount of spatial resolution I was actually missing out on with my imaging rig, in my case only a 3-4%, so I concluded using a high drizzle value was going to gain me very little .
Best of luck
Tobias
For a colour camera I've had good results with a droplet size of 0.8 and a scale of 2. Remember with a colour camera you are sort of working with 2x2 cells, so a scale of 2 is a good place to start (but experiment).
My impression is that your images result from too small a droplet size possibly combined with not enough lights. I don't know how many lights you have used, but I would get at least 60 for a bayer drizzle - preferably more. Obviously with frequent dithers, preferably dither with every light (unless you are taking hundreds of lights). I'm no expert, but these parameters have worked well for me.
JC
My current goto settings for bayer drizzle with a CMOS camera , with my image scale of 1” per pixel are:
Scale 2.0x and droplet size of 1.0 with at least 80 (preferably 100) frames, with drizzle every frame.
If I have less frames, or noisy data, then I use 1.5 drop.
this gives me good results. If I have too few frames, or I push the droplet size too small, I get a ‘basket weave’ effect on the background, and a high instance of false coloured pixels.
