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.
Wow, I guess v1.60 was just released today? I attempted to use the MC/MS calibration flow and for some reason, it seams the dark subtraction, or flattening is not occurring.Â
I have tried this three times now. The data set is fairly large, about 30 frames each R,G,B across two nights. I have master dark, and bias which have proven good with recent data from my camera. So, made master flats for each night, then tried to use those all with the R,G,B light frames doing the per channel option and integrate all (sessions I assume).
The resultant master integrated frames look like they have amp glow on the sides which would occur of dark subtraction failed somehow. It could be vignetting, not being cleaned up by flattening, I can't tell exactly. What I know is the calibration is failing somehow.
Hi Stephen @st1_armen,
I think I know what's happening. You are using old master frames right? The masterbias should be fine. But there could be a problem with the old masterdark. Let me explain:
In APP 1.059 and below (so with the old calibration engine), if you loaded both bias and darks to create both a masterbias and masterdark, APP created a MasterDark with the MasterBias alrady subtracted. This is a problem which has to do with black clipping of calibration data in the MasterDark.
This is also on of the reasons why the new Calibration engine is better. Any MasterDark created with the new calibration engine will never have the MasterBias subtracted. The actual subtraction of the bias signal from the masterdark happens now in calibration of the data without black clipping which ensures no calibration data is lost/wasted.
We can verify if this is the problem that you face with your old Master frames. Can you share the fits header information for both the masterbias and the masterdark? (if you load them into the image viewer, you can see the header information with the details checkbox above the image viewer).
Another way to test this, is to create a new masterdark from 1 or a couple of darks. Then calibrate your data and it should be okay.
Since the calibration engine is changed considerably, there are some big changes and I am very confident that it's much better and easier for everyone.
The only problem that I am aware of that could happen is a problem with an old MasterDark that already had the Bias signal subtracted, so I really think that is the issue here.
I will be happy to have a look at your masters as well to confirm that this is the case. You can send the masters and some lights to support@astropixelprocessor.com using wetransfer.com
Kind regards,
Mabula
Hi Mabula,
Thank you again for all the help. I came to the same conclusion which shouldn't have surprised me after many image projects. The FITs head of my master dark does not give a clue if bias subtracted, however I'm fairly sure that was the root cause (besides my being slow to figure things out :-).
Normally, I remove the raw darks/biases from my hard drive to keep it clean. Thankfully, I had backed up my machine prior and had the raw darks from February. Ok, today generate a new master dark without bias subtract to do it all again. The MC/MS flow should be very convenient once I get the correct pieces in place.
best regards,
-Steve
Â
Hi Mabula,
Thank you again for all the help. I came to the same conclusion which shouldn't have surprised me after many image projects. The FITs head of my master dark does not give a clue if bias subtracted, however I'm fairly sure that was the root cause (besides my being slow to figure things out :-).
Normally, I remove the raw darks/biases from my hard drive to keep it clean. Thankfully, I had backed up my machine prior and had the raw darks from February. Ok, today generate a new master dark without bias subtract to do it all again. The MC/MS flow should be very convenient once I get the correct pieces in place.
best regards,
-Steve
Â
Hi Steve @st1_armen,
If you still have trouble with calirbation, do send me a subset of your data. Then I will give you feedback about what happens or has happened and why it failed previously.
Cheers,
Mabula
