19 June 2021: Our upload server https://upload.astropixelprocessor.com/ has been migrated successfully to our new office with higher upload and download speeds (nearly 10MByte/sec up/down ) ! We now have 1 general upload user called: upload with password: upload. The users upload1 - upload5 have been disabled.
31 May 2021: APP 1.083-beta2 has been released ! APP 1.083 stable will follow soon afterwards. It includes a completely new Star Reducer Tool, New File Saver Module, Improved Comet registration and much more, check the release notes here!
Analyse Stars failure
I'm having issues with a multisession stack, where the star analysis fails at 64% completion with this message:
Encountered error in module:
Any ideas what's wrong?
Mm, might be an issue with the calibration data somewhere. Could you try without darks to see if that solves it?
I had this happen before too. What I do now is first make all the calibration masters (one at a time), then I restart APP, load all the lights for all sessions and attach the masters. This usually solves this for me.
Hope this helps!
Yes, you were right.
It's a multisession stack and I wrongly loaded all my lights into their respective sessions, instead all-in-one, as per the software's recommendation.
1.083.2 beta. About 400 light frames (three sessions) with corresponding calibration shots (flats, Dark flats, and two sets of darks - the first session had different time and gain).
On Mac with Catalina. Crash with java:266 error. Sigh.
Let's try it now on a windows computer (win 10) with a fresh installation of APP. 1.082 just downloaded. This time I use the calibration masters, as APP had created them in the previous attempt. Crash with java:266 error. Ainsss.
Back to the Mac computer. This time I choose three already calibrated images from another object (Ha+OIII+CMOS). I upload them as lights and press the integrate button. Crash with java:266 error. Argg
I attach screenshots. I don't know what to do anymore... This has never happened to me before... Any guidance on what I'm doing wrong
So did you try a stack without calibration files, as mentioned above? Just to see if APP hits an error due to a problem in the calibration data?