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 APP team,
I'm currently having a problem with rejection on a series of images. I had never encountered this concern before.
The main difference with my previous series is that this one is made of 8 images per color whereas before I had at least 12.
Could my rejection problem be due to this insufficient number of images?
I live not far from a major airport and aircraft dragging is a problem.
I have read all the tips related to rejection but I have not found any clues.
You could tell me: "Go back to taking more pictures", but the weather has decided otherwise 😣Â
For all intents and purposes, I tried it under PixInsight. Same results, the rejection is not going well.
I think the solution will be to go back to the field: 😎Â
By any chance, I make the files available on this dropbox
I had a try on your data and even with the most aggressive settings couldn't get rid of all of the trails. Judging by eye, the data are filtered to the noise level. But the tricky part is that the eye and brain are extremely good at detecting straight lines, even well below the noise level of a single pixel. But when brain-processing the information from hundreds or even thousands of pixels, the very faint residual lines still jump out at you.
In case @mabula-admin feels up for a challenge: one way I'd try to find and filter these data are with a Hough transform, which is a way of identifying straight lines in the data, and would then allow more explicit filtering. Another option could be to use the identified outliers, create a map, and perform a grow operation on it to exclude adjacent pixels from the stack as well, even though they otherwise pass the outlier rejection filter.
