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 hope someone can help with my problem.
I have a data set which, after loading lights, darks, bias and flats, runs the calibration tab and I can look at the maste results on screen and all look fine.
I press callibrate stars and get a screen pop up and that is as far as it will go.
Is this a data set problem or the programme ?
Regards
Steve
Might be an issue in the calibration data, what happens when you integrate without any calibration frames?
I am just trying the same data on another computer.
When thats done I will try without calibration frames.
S
OK so it turns out the bias files are the problem. Leave them out and all goes to plan.
The only difference I can see is the colour space. lights are 16b RGB and NO in CFA column
Bias frames are 16b Grey and RGGB in the CFA column.
I think I read something about APT doing its Bias frames in grey because thats what it does for CCD mono. I think I will have to find out how to do colour bias frames as that seems to be the problem.
Regards
S
That might be of influence (not 100% sure), at least we narrowed it down now. 🙂
So, as far as I can tell ticking the force CFA in the 0 tab has cured the problem. All files went through the complete process with no issues.
Found this by reading similar problem by another member and just trying it out. The file set was created in APT if that makes any difference.
S
Ah, yes that could be the issue. Some capture software don’t add proper FITS keywords in the resulting subs and APP then can’t know what the type of data is.
