Bug 462813 - platesolving module - if platesolving fails not obvious why and also seems to get in a loop
Summary: platesolving module - if platesolving fails not obvious why and also seems to...
Status: REPORTED
Alias: None
Product: kstars
Classification: Applications
Component: general (other bugs)
Version First Reported In: 3.6.0
Platform: Other Other
: NOR wishlist
Target Milestone: ---
Assignee: Jasem Mutlaq
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-09 11:22 UTC by sequel.county_0d
Modified: 2022-12-09 11:22 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sequel.county_0d 2022-12-09 11:22:16 UTC
SUMMARY
***
Do a capture and solve and get an image back with stars (to human eyes) the solve can fail. At which point it tries again which can/will fail again as nothing as changed until you click stop.

The loop is pointless or at the very least should only try a set number of times, however the bigger “problem” is the complete lack of any feedback as to why it’s failed. Yes logging can be turned on and there may be some details there if you have a dig around but it would be better if as it’s running it returned some details like how many stars has it found or which bit has actually failed -the image, the extractor or the solver.

***


STEPS TO REPRODUCE
1.  Run platesolving 
2.  image returned which looks to have stars


OBSERVED RESULT
when platesolving fails it tries again but gives no hint as to the problem 

EXPECTED RESULT

Error message gives you a clue as to why it’s not working 

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: astroberry
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
No idea why my platesolving failed. I tried both the guide and main cameras both of which has worked fine earlier in the session and the conditions had if anything improved. Suspect the problem was down to a kstars crash earlier (unknown reason possibly to do with autofocus during a sequence) though I’m pretty sure I rebooted as ekos/indi decided it couldn’t connect to my main camera again.