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 just got a new camera and I am in the process of creating a set of Master Calibration files. As part of this process I am creating a new BadPixelMap. After running the Calibrate module APP output two BPM master files BPM-1 and BPM-2. It's been a while since I did this but I do not recall two files being created in the past. When I examine them it only looks like BPM-1 contains any information (BPM-1 shows a lot of bad pixels and BPM-2 doesn't appear to show any). So I have a couple of questions: What are the two files for and is it ok to delete BPM-2 (no apparent info) and just use BPM-1? Thanks
@batch Hi Bill,
What input data are you using for creating the BPM? Are there files that have a different temperature, gain, offset or exposure time than others? Are you loading all data into one session or two? Please try to give us as much information as possible.
Thanks, Wouter
Hi Bill,
have You checked the exposure times in the frame list? I came across a similar issue as the camare reports slightly different exposure times (e.g. 60s vs 61 s), hence APP would create 2 MasterDarks resulting in 2 BPM's.
You can avoid this by unchecking the "seperate darks acc. to exposure time box at the very bottom of tab 2) (You need to watch out not to throw in lights with really different exposure time, though , e.g. 60s vs 120s), which would require individual Masterdarks.
Hope this helps,
Jochen
@wvreeven Hi Wouter
I've tried multiple variations by processing individual channels/single session to multiple channels/single session. All temps and gain are the same on a per channel basis and darks match lights. I have tried setting the BPM parameters myself as well as running it with the automatic option selected. I am using vr 2.0.0beta4. Regardless of what iteration I run it still results in two BPMs being produced. One thing of note is that I am reporting a Hot Pixel count of about 2.7% and 0% Cold pixel count so I'm wondering if BPM-1 which clearly shows multiple pixels is the Hot pixels and BPM-2 which shows nothing (flat white) is the Cold pixels. Would this make sense? If so I could discard BPM-2 and just use BPM-1 going forward.
@jochen-scharmann Hi Jochen,
Thanks very much for the suggestion. I did check the exposure times and everything matches as well and in every instance only one MasterDark was created.
Regards,
Bill
