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.
[Solved] Error message: java.lang.Float cannot be cast to java.lang.Double
I only started using the program today so forgive me if I get this wrong, but it happens as soon as I hit normalize under step 5. It is repeatable - it's happened three times and I can't seem to get past it.
Sorry for that inconvenience, it seems to happen with specific data now and again. It's known and will be fixed in the next release. Mabula has gotten your message as well and will come back to it asap.
First of all, Christopher, thank you for sharing this issue and welcome to the APP forum š
Ā
Can you please provide more information on what kind of data you are loading into APP ?
Which camera?
Which file format? FITS, or ?
Which bitdepth (8,16,32 ?Ā )
Are you using calibration frames, if so which types?
And also, is the issue happening with and without calibration frames loaded?
Ā
The issue very likely has to do with your particular data, perhaps you can share a small subset of your data so Vincent and I can investigate why you get this error message and solve it at the same time?
I figured out that this happens if you are using a reference file and click Normalization without the reference file being checked.
My story is that I used DSS for this project and got 5 stacks that came out great, but for some reason, DSS couldn't handle the red. I even did an extra session, but it got all smeared at the bottom and any iteration of data (half from session 1, half from session 2, only session 3, etc.) just failed in the same way. Anyway, I had aligned everything with an OIII sub and didn't see any reason to restack the other five stacks (over 700 lights!) so I tried loading just the reds into APP and used the OIII as a reference. It appears you can uncheck it prior to integration and everything will work as intended, but it will crash if you normalize with the reference unchecked.
