rlancaste wrote: I might be reading this wrong, because it is fairly late in the evening for me, but it looks to me like this crash occurred in KStars during guiding, after StellarSolver returned the star list, but before the method to find the guide stars completed? Perhaps the list was still needed and it got deleted in KStars too soon? I will send this to Jasem and see if he agrees.
Ihoujin wrote: Can we get a warning in the status output for low star SNR with a recommendation to increase exposure time?
I just made a change to the autodownsample function for the solver, to just be a little less aggressive because it was causing some failed solves since the stars were downsampled too much and were no longer starlike.
Ihoujin wrote: KStars Built Build: 2020-10-30T03:22:05Z
Last night I compiled StellarSolver and KStars. I was pleased to find importing RAW images is now supported Thank you.
I also tested with a few other files, and noticed one of my JPG images I had successfully been solving does not load properly now. The image itself is now distorted.
The original jpg is also attached.
I also had one image I previously could solve in around 10 seconds but now took at least 80 seconds to do. My trouble is, now that half of the preset profiles have been pruned out, I am not sure what settings made up the difference. I can recall I had some of my best results with the now removed Fast Solver preset.
This image is attached. The Bubble Nebula.
Lastly. I do not believe the RAM check is reliable at the moment. I have encountered some crashes with it on. I believe I am just on the limit of stable use of Load All Indexes on a Pi with 4GB. It will either:
1. Work really fast with indexes loaded into RAM
2. Will say I do not have enough RAM and work slower
3. Or concerningly it will say I can load into RAM, but then crashes.
I have attached logs that should help, but do note they were from an earlier build, details are included.
Edit: I found that JPGs exported specifically from GIMP are distorted when loaded. Any ideas as to why that might be? The image used to load without issues until only very recently.