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] Pure red pic - beginner's mistake? - SOLVED, data is only 8bits
Unfortunately I uninstalled APP, thought that would help - sorry. Now I can't get into APP anymore for the starting routine asks for the license code - but the old one doesn't go through:
I don't have a new license code, just the old one. But in my account's download section there is written the new expire date on 26 July 2020 as you can see on his screenshot (blue marking):
Pls do not spend too much time sorting out this problem! Most likely I'll buy a renter's license for one year anyway.
Have some nice Pentecost holidays or "Pfingsten" as we say in German!
Well, that should work so we have to get that fixed. 🙂 I've notified Mabula so when he has time to have a look it will get sorted. Thanks for wanting to purchase a licence anyway! Much appreciated.
Habe schöne Ferien! (my German is rusty, been a few years) 😉
I don't have a new license code, just the old one. But in my account's download section there is written the new expire date on 26 July 2020 as you can see on his screenshot (blue marking):
Pls do not spend too much time sorting out this problem! Most likely I'll buy a renter's license for one year anyway.
Have some nice Pentecost holidays or "Pfingsten" as we say in German!
I have added 15 days to your Trial license starting today 😉 You should have received a separate confirmation of this as well.
The mentioned expiry date of 26 July 2020 for the downloads is not the same as the expiry date of the license. When someone orders a Trial we set the download expiry date 3 months later to start with.
The red picture problem sounds very odd Peter & Vincent, any idea know what happened on the first dataset? perhaps it is a good idea that I see this for myself 😉
As you requested I uploaded the frames producing that pure red pic into the folder named "PeterJK-redIssue". Some of the lights are spoilt apparently, I left them out. To all this some additional details for you:
All frames were captured by the ASI533MC-Pro camera without a flattener (late shipment) using StellarMate v1.5.2, a Rasperry Pi based astrophotography tool you certainly know. The autoguiding was quite bad because I tested the alignment process offered by Ekos which was a bit tricky to do. In the end I wasn't sure which was the alignment star and therefore the autoguider had heavy discrepancies to compensate.
Furthermore I had an issue with StellarMate's instable Wifi connection to download the frames directly to my Windows 10 notebook; it's solved now by an update. So at that time I used KStars/Ekos locally installed on the Rasperry Pi and stored the frames locally on the Linux device at first. Later I transferred them to my notebook via USB stick.
I tried processing the frames in APP back and forth with bias and darks and without each but it resulted in a pure red pic again and again. Once I got a pure black pic in a constellation I can't recall unfortunately. Of course I tried to process the lights separately but it resulted in a pure red pic, too.
That's all I remember now, if you have more questions pls let me know.
Hello, I am an APP beginner, seems I've done some basic mistake: the result after batching my captures was a pure red pic - see two page appendix! I really don't know what's the issue, is someone able to give me a helping hand? Best regards, Peter
Thank you very much for sharing your data with us 😉
Your issue is a data capture issue. You have stored all the lights, bias, darks, flats in only 8bits with your capture software. That is very destructive for your data. By storing the data in only 8bits, you throw away a lot of information immediately.
This is the metadata of one of the frames, APP shows it in the left part of the image viewer:
You need to make sure that the capture software stores the data in 16bits Fits files, then all should work and look good 🙂 !
Especially data calibration with bias, darks, flats will never work properly if you only have 8bits data...
Shoot in 16bits next time, and you will a huge difference in results 🙂 , no doubt !
