European AstroFest 2023 - 3 & 4 February 2023 - Kensington Conference and Events Centre, London.
Please come all to AstroFest in London to ask us (Mabula & Vincent) questions and to see live demos of APP!
Please note our new Downloads page here
2023-01-19: APP 2.0.0-beta13 has been released !
!!! Big performance increase due to optimizations in integration !!!
and upgraded development platform to GraalVM 22.3 based on openJDK19
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
If I remove the flats and darks, this error message does not come. BIAS work alone.
This is with 1.077 right? And the exact same frames didn't cause an issue with 1.076 or 1.075?
Yes, that happened with the update to 1.077
I have now installed 1.075 again. Now I have the same error message here.
I'm testing other data, here is the same error message.
Obviously this error message comes from the Darks. Now I only used 30 of the 50 from the middle. And now it works 🙂
I uploaded the 50 darks here. Maybe this will help you find the mistake.
Ah great, yes it sometimes happens when calibration data has some issue. Might be worth for you to check the difference between the darks that didn't work and those that did, just to prevent it in the future. Thanks for uploading, can you pinpoint which frames caused the issue?
I looked through the darks one by one and saw no anomalies.
That error is indicative of a problem where you are calibrating data that incomaptible like monochrome data with Bayer CFA or 3-channel (RGB) Master frames or vice versa... check your data, if it's Bayer CFA data, have you enabled Force CFA in 0) RAW/FITS? Are all masters created as CFA masters?
Can you share frames of all types? Some lights, darks, flats, bias? I will make sure that it is solved.
Mabula