2023-04-17: APP 2.0.0-beta17 has been released !
RAW support for camera color matrix with Bayer Drizzle integration, fixed couple of image viewer issues.
We are very close now to releasing APP 2.0.0 stable with a complete printable manual...
Astro Pixel Processor Windows 64-bit
Astro Pixel Processor macOS Intel 64-bit
Astro Pixel Processor macOS Apple M Silicon 64-bit
Astro Pixel Processor Linux DEB 64-bit
Astro Pixel Processor Linux RPM 64-bit
Today APP stopped working when I calibarted a series of images. The following error message appeared:
Encountered error in module:
I have tried reinstalling the software and loaded different files that have been processed successfully earlier, but same message appears. Advise is needed...
Could you provide us with details on what you did before the error appeared? Like your workflow, type of data, camera model etc.? Thank you.
I processed a series of 19 images taken with ASI533c. FITS files of course. The same images were processed successfully yesterday, the error appeared when I tried to reprocess them today. I loaded 40 flats, a master dark, master bias and BMP. Specifically the error appeared when APP started "analyse stars".
Thank you, interesting. And there was no difference with yesterday, you used the same calibration files etc?
Yes, the only difference is that I removed one light frame because of bad tracking...
What happens when you try it without any calibration data?
Then it seems to work. Just added 19 frames and no calibration frames and they integrate fine...
I also tried without using Master Frames, just adding 40 flats, 21 darks and 50 bias frames and let APP generate new masters along the road. Now it also works! New masters were generated and the light frames were calibrated and integrated fine.
I then tried to do the proces yet again, but now using the newly generated masters from above. This also works!
The error musr be linked to the use of the masters that were generated yesterday. I shall continue to test and report if the error message shows up again...
Excellent, then it is an issue somewhere in the calibration data, we see that quite often if an error like this happens. Might be nice if we could get these errors more clear.