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 have a small set of images from iTelescope t07 through narrow band filters. Star registration was successful for the Luminance and Halpha but fails with my Sii images. Adjusting the limit for star recognition had the side effect of making the Oiii images start to fail as well. Disabling the limit did not change this parameter. The fit files are around 40mb.
. A prior data collection with this telescope containing similar ccd column defects did process correctly so I am surprised that what appear to be better images are now failing. I have downloaded the beta3 and will be starting all over with it... a pity the file load cannot be saved.
Yes, please let us know if 1.076 is able to process it correctly as this specific part was addressed in this version. Registration should work better for this kind of data now as well.
Thanks. It actually did run correctly with 1.076, but I got interrupted and had to shut things down. Wish there were some way of persisting the loaded modules list beyond a single session. If it were my code I would just write out the list from the lower window in a form that could be reloaded, or a load/save option. I have four filters for a couple of days and re-entering them with the associated master files is a real pain, imho.
Â
greg
Yes understood, saving your settings is a top priority to include in an upcoming version for Mabula.
