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.
In 1.066 I have been trying to create a BPM but have noticed an error if you select "detect bad columns", process the appropriate images to get a BPM, then uncheck "detect bad column" and reprocess. A severe artefact hangs around as if its related to the previously bad column detection causing the values and BPM to be incorrect.
To recreate:
1. Process Darks, Flats and DarkFlats, selecting create Bad Pixel Map with "detect bad columns" unselected
2. View the BPM
3. Check "detect bad columns" and reprocess
4. View the BPM. For me, this isn't appropriate for my camera
5. Uncheck "detect bad columns" and reprocess
6. Data and image changes show the bad column data interfering
First image is Good/Expected
Second image shows that "detect bad columns" has an adverse affect so I uncheck it and reprocess
Third image should be exactly like the first one - same settings (detect bad columns unchecked) but it is wrong and the values are completely wrong too.
Hi @itarchitectkev,
Thank you for sharing this. I will test this myself using APP 1.068 to see if the issue still exists. I will report back on my findings.
Mabula
Hi @itarchitectkev,
I have tried to reproduce the issue that you described in APP 1.068. But it all works well I believe.
Perhaps the issue was resolved in the latest versions.
Can you test again and let me know if all is allright in APP 1.068 ?
4. View the BPM. For me, this isn't appropriate for my camera
I don't think your camera suffers from bad columns. Your camera has a rather new CMOS sensor 😉 . The bad columns are mostly only an issue with CCD technology.
Thanks in advance 😉
Mabula
Â
I can't recreate this on 1.068.
One minor point though - if the option is "*detect* bad columns", then in theory this option shouldn't make any difference if selected or not, but it does. It does affect the BPM. It therefore must be making some wrong decision during it's detection, else it shouldn't be called "detect". Perhaps, "mask bad columns" is more appropriate so it doesn't imply the processing is making a decision?
