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'm encountering a new problem that I've not seen before, and I can't figure out what the issue is.Â
Two nights ago I shot (in NINA 1.10) and fully calibrated a narrowband target data set with the attached bias and darks.
Last night, I shot a new narrowband target in NINA 1.10 HF1, and used the same attached bias and darks to calibrate this new set of narrowband images. I've examined the headers and they appear to be identical to the previous set of images, but for some reason when calibrating this new set of images, applying darks is doing something very strange. I can't imagine there's a big difference between these two versions of NINA. But when creating new masters, two BAD pixel maps are created because the lights and flats have CCD in the camera name, and the bias and darks don't even though the camera is the same for both.
Here's the stacked uncalibrated image.
And then the stacked and calibrated image showing the issue. These are stretched images.
Here's a link to download a set of 10 light, bias, dark, and flats that I'm using if anyone can tell where the issue is.
Â
OH, I should add one crucial bit of information. I used the same darks and bias to calibrate LRGB from last nights session, and it calibrated perfectly. It's only the HA that did not calibrate, and those are the files I included above.
I've completely reshot all masters, this includes new master dark, flat, dark flat, and bias. Doing a full calibration run exhibits the same results.
Running flats only results in a more normal image.Â
Running darks only results in the same issue as above. So this has something to do with darks.
Here's a close up image showing the results of a calibrated integration.
I think I've tracked this issue down to a pedestal issue. The median ADU of both my bias and dark are above the median ADU of my lights. But I cannot seem to get pedestal values added to the images using the batch add process.Â
What steps and value would I need to add to get these images to work?
Solved my own problem. I had to add a pedestal value of 1800. The program shows 0.0 for the pedestal value in the header, but it is applying a pedestal to the images, and they process correctly once you get the right value.
Ok lots going on here, so basically the pedestal is not updating in the header you say?
