2023-03-15: APP 2.0.0-beta14 has been released !
IMPROVED FRAME LIST, sorting on column header click and you can move the columns now which will be preserved between restarts.
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
Problem using frames from different sessions
I just finished processing OIII and SII files from this nights session and I run into some problem.
I used Dark frames I gathered the previous night and after integration both the OIII and SII channel showed no data.
After a second try OIII still stayed dark and SII came out like this:
I had some OIII data from the previous night and once I added it APP seemed to process this data correctly but then ignored the data from the following session.
Multi Session processing is selected and I correctly assigned the frames to the sessions.
I didn't change anything in my imaging setup between the two sessions and never had a problem in previous runs, at first I thought it maybe didn't apply the dark frames but it seems like APP did do something to the light frames and I have no idea what could cause this.
After stacking only my light frames without any calibration frames I get an image, so definitely a problem with the calibration frames coming from another session.
Ah crosses, I've seen that weird thing before a long time ago. So it only happens with your latest darks? If that's the case there might have been a setting wrong when you took those. Check offset etc.
I did shoot another batch of darks a day later and tried them.
I'm at the point where I suspect there's a problem with at least some of my light frames. I did try to stack them with DSS but I get the same result so I'm pretty sure the problem has something to do with my data.
Once I'm able to get some new images I'll report back if I was able to get rid of this.
Yeah, unfortunately I can't remember what caused this specifically (which is why I write this kind of stuff down now 😉 ). If the issue remains I'd like to have a look at the data as well.