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 tried to do a comet registration but APP continuously gives me an error like this popup window, eventhough when I raise the amount of stars, and do all what is suggested it still fails. When clicking image by image on the comet nucleus, then Skip view to continue, finally the error message pops up. Anything I do wrong, any instructions on how to use this?
I'm using the Beta 7 version, works nice and a lot faster then before but I encountered this problem. Trying to process with DSS I had no problem, APP does more or less the same, first registers on the stars and then registers each frame on the comet nucleus ( you have to indicate by hand every frame sadly enough ).
I thought that indicating the first frame of th sequence and the last one would suffice for APP to extract the comet's position in each frame.
If you need a couple of frames please tell me so that I can create a folder and upload there. I have 45 frames of 10 seconds each so please indicate how many of them you need.
There was a problem with the capture program, so I had to reinitiate it and then the camera was uncontrolled, likely the sensor got cooled too fast and showed some dark spots, likely ice.
Yes it can do that automatically, but that also depends a lot on if APP is able to detect the nucleus properly and it sounds like it can't in your data. This can be due to the data. You can upload the frames to our server so I can have a look (please allow for a few days):
Ok, I just created that folder and uploaded 15 frames.
I would highly apreciate if there is some help on how to use this comet registration automatically since when you image a fast moving comet, you need a lot of short exposure frames and indicating manually where the comet nucleus is takes a lot of time!
Maybe in my case there is some problem since the comet is close by a star.
Hope to hear from you when you had time to check my data!
No problem, being very close to a star may also throw it off. But it's always nice to have more data to test our algorithm on and improve it for sure. I'll let you know what I see later.
So I could register the data you uploaded fine, but the comet needs manual confirmation indeed. It may be due to the low signal on it, but Mabula is going to inspect both registration and see if we can improve the comet detection algoritm as well with your data (that will take longer).
