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...I spent seven hours on a cloudy night creating an assortment of calibration frames to include flats,dark flats and darks (30,60,90,120,180,300 sec) at ambient and 0C degrees.
When I created a BPM using the 31x 2 sec flats, 30x 2 sec dark flats and the 20x 180 second darks, it generated what I believe is a good BPM with 2.7% bad pixels. (I used auto settings). However, after I saved the BPM to a folder, and then tried to load it into APP, I get the message that it "does not appear to be a Bad Pixel Map" as it lacked the BPM metadata. When I clicked YES to load it anyway it loaded OK -it appeared identical when zoomed in- (third image, below) but it no longer displays the metadata as it does in the first image, below. Did I do something wrong? Will the BPM work in future processing attempts as it should? Thanks!
Mmm that is weird, you didn’t change anything in between for the BPM? It should just be created and that’s it. No further processing should be done on it, or loaded into another program and then saved again. Things like that might change the fits data.
Well, that is what I suspected. Although it was automatically saved to the directory folder after it was created, I did 'save' it again, and added a suffix to identify it (e.g. "-0C"). Will it need to stay in the original folder or can it be moved to a "Bad Pixel Map" folder without changing the name?...would simply moving it change the metadata? Thanks for the reply!
No that should be fine, also renaming it would be ok I think as the fits header is what matters. But to be on the safe side for now, just save it in a folder for you to keep. A BPM can be used for at least a year on all your data, it never degrades data.
@vincent-mod Thanks again...slowly getting more familiar with APP! I just now processed my first ever meridian flip in APP...no issues.
Here is an image from July!
Excellent! Good to hear. 🙂 I would make the background less dark though, but the signal is great!
