It did take a long time to have the work finished on this and it will have a major performance boost of 30-50% over 2.0.0-beta39 from calibration to integration. We extensively optimized many critical parts of APP. All has been tested to guarantee correct optimizations. Drizzle and image resampling is much faster for instance, those modules have been completely rewritten. Much less memory usage. LNC 2.0 will be released which works much better and faster than LNC in it's current state. And more, all will be added to the release notes in the coming weeks...
Update on the 2.0.0 release & the full manual
We are getting close to the 2.0.0 stable release and the full manual. The manual will soon become available on the website and also in PDF format. Both versions will be identical and once released, will start to follow the APP release cycle and thus will stay up-to-date to the latest APP version.
Once 2.0.0 is released, the price for APP will increase. Owner's license holders will not need to pay an upgrade fee to use 2.0.0, neither do Renter's license holders.
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).
