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.
Hi, I just encountered a small issue where I hadn't noticed my Lights were loaded into a different Session than where I thought my Flats were.
i.e.
Light Frames: Session 3
Flats and DarkFlats: Session 1
The result is Calibration gets to the end of processing, then throws a Java NullPointer Exception processing Flats with no further explanation.
Of course the user shouldn't be so careless, but sometimes coffee is slow to ignite the brain matter and I think checking the files prior to a potential lengthy operation is a good thing.
I've just realised it is possible to process Calibration frames (like Darks) without associated Lights, so perhaps this is isolated to Flats/DarkFlats [I updated the topic to specifically target these]
Hi, I just encountered a small issue where I hadn't noticed my Lights were loaded into a different Session than where I thought my Flats were.
i.e.
Light Frames: Session 3
Flats and DarkFlats: Session 1The result is Calibration gets to the end of processing, then throws a Java NullPointer Exception processing Flats with no further explanation.
Of course the user shouldn't be so careless, but sometimes coffee is slow to ignite the brain matter and I think checking the files prior to a potential lengthy operation is a good thing.
Hi @itarchitectkev,
Let me check this, I will get back to you 😉
I've just realised it is possible to process Calibration frames (like Darks) without associated Lights, so perhaps this is isolated to Flats/DarkFlats [I updated the topic to specifically target these]
Off course, that should be possible and I do it all the time ;-). Simply load some darks, bias, flats and create some masters without loading lights, that should work without any issues.
Mabula
Hi, I just encountered a small issue where I hadn't noticed my Lights were loaded into a different Session than where I thought my Flats were.
i.e.
Light Frames: Session 3
Flats and DarkFlats: Session 1The result is Calibration gets to the end of processing, then throws a Java NullPointer Exception processing Flats with no further explanation.
Of course the user shouldn't be so careless, but sometimes coffee is slow to ignite the brain matter and I think checking the files prior to a potential lengthy operation is a good thing.
Hi @itarchitectkev,
I just tested this in 1.076 beta4 and no NullPointer is thrown. In which version is this happening and does it happen everytime you try this?
Creating master frames is irrelevant to lights being loaded or not. They will simply be created. If you assinged them incorrectly. Then you can always assign them correctly, by reloading those created masters. You don't need to recreate them ;-).
Mabula
