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'm sorry, I must have a different version. Once I clicked cancel, I cannot find a way to resume the process. I had clicked "integrate" and quickly realized I want to make a minor change. So I hit cancel. It will not let me resume. Do I really need to start all over again????
It has happened to me several times, I cant locate when or why it freezes. Sometimes it freezes and sometimes all button are just greyed out. So the solution is... Dont cancell it unless you absolutely need to.
Okay, I have opened a separate issue on my issue list to thoroughly test this and fix it. Can you tell me if this problem occurs always at the same spot, like always if you cancel 3) analyse stars, or perhaps 4) register? The problem has to do with concurrency, so the specific behaviour of when it goes bad, can help me find the issue.
Hi @heylers, Thank you very much for your feedback.
Can you share with me what settings you use in 2) Calibrate? Is it defaults or do you enable/disable certain settings? Is it misbehaving when you push cancel at the start of calibration of later on? Please be as specific as you can, that will really help me to sort it out. It is very likely a concurrency issue, so that means it has to to with multi-threading and the moment that you push cancel during the calibration can really help me to find the issue in our code.
It's the default settings. Usually what happens is it starts and a say a few to maybe 15 seconds later (maybe at 30% or so?) I notice the calibration assignments aren't right. So insted of running it further, I cancel. It just stops there with "cancel" and everything greyed out and stays there.Â
@mabula-admin I have just worked it out - its when I am typing the file name - every time I press the space key in the name it is toggling the selection in the background 🤣
 Â
The reason the file is selected (sometimes) is that I occasionally like to view the calibrated image to get an idea of what it looks like before I perform the integration.
Please accept my apologies for missing this issue earlier. I have added it to the top of my issue list and will fix it as soon as possible. I will report back when it is fixed.
@mabula-admin I have just worked it out - its when I am typing the file name - every time I press the space key in the name it is toggling the selection in the background 🤣
 Â
The reason the file is selected (sometimes) is that I occasionally like to view the calibrated image to get an idea of what it looks like before I perform the integration.
FIXED space bar can no longer deselect/select a frame in the frame list while entering a name in the Enter DeepSky object name field in 1)LOAD
Previously, if you have loaded a frame into the image viewer, and you would enter a name with spaces in the Enter DeepSky object name field in 1)LOAD, the space bar would toggle the frame in the frame list from selected to deselected or back. This is no longer the case and thus fixed.
@mabula-admin thank you very much. This was an incredibly annoying bug and one of the main reasons I stopped work on my high resolution full Milky Way project.
It's the default settings. Usually what happens is it starts and a say a few to maybe 15 seconds later (maybe at 30% or so?) I notice the calibration assignments aren't right. So insted of running it further, I cancel. It just stops there with "cancel" and everything greyed out and stays there.Â
It's the default settings. Usually what happens is it starts and a say a few to maybe 15 seconds later (maybe at 30% or so?) I notice the calibration assignments aren't right. So insted of running it further, I cancel. It just stops there with "cancel" and everything greyed out and stays there.Â
I have fixed the issue with the cancel button not working properly in 2) Calibrate, thank you very much for reporting this. The fix will be part of 2.0.0-beta38 which will soon be out.
