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 everyone,
I searched the forum, but could not find an answer to this. Is there a description of the filename naming convention that APP uses to determine what kind of image is loaded? It seems the import is quite good in guessing what Image (Channel, Session, Filter, etc.) is used by the filename. But I could not find a documentation of that. It would really help to speed up things if I just name all files from a imaging session appropriate to this naming convention and load everything in one step and let APP decide what image is what.Â
Or even better if APP could be started with a reference to a config file that defines list of image files for darks, flats, bias, lights, etc. and if possible also the parameters for the processing. This could be also a different config file so you can have presets of different processing parameters.Â
With best regards,
Mario.
APP looks at the headers of the files, for fits files at least. And if they use the regular fits header format it will assign the data properly. Not all manufacturers provide enough information, which is why you sometimes have to click "force CFA" if APP loads the image assuming it's color while the data should be mono.
The config presets, APP will get a "watch this folder" feature, mainly developed for iTelescope, but I guess it'll also be in the regular release. That would allow you to put your data in there and APP processes the data automatically when new data arrives. And maybe something like you suggest can be part of that.
