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.
Firstly, just want to congratulate the team behind APP for developing an excellent tool. It has simplified my pre-processing immensely, and I don't use any other programs for pre-processing DSOs now. I have a couple of suggestions which I think have already been made, but just to re-iterate:
1. Previously, integrated files had naming conventions which would detail every area e.g. exposure time, binning, LNC, MBB etc. This seems to have been removed. There should be an option in settings to enable it so that people can choose if they want the naming convention to be kept. I personally found it very useful.
2. There should be an option to save a set of parameters starting from star analysis to integration as a file so that it can be loaded when required. For example, I use a particular set of parameters for regular integrations versus mosaics. If each of these settings could be saved as a file which can then be loaded, it would save time.
3. Automatic rejection of frames which cannot be registered/star analysed and proceeding to the normalisation/integration process without aborting the whole process would be good.
Again, thank you to the APP team on their hard work!
Thank for the suggestions!
1) This information is now in the header file, but indeed when the settings is a possibility this might be a good thing to support.
2) Yes, this is on our list to do, I don't have a way to see the roadmap though
3) Agreed, that may be nice indeed. I think things like this will get implemented as we want to automate quite a few steps while retaining the best quality where possible
