Bug 458257 - Polar Alignment Assistent - Refresh Phase failing
Summary: Polar Alignment Assistent - Refresh Phase failing
Status: RESOLVED FIXED
Alias: None
Product: kstars
Classification: Applications
Component: general (other bugs)
Version First Reported In: 3.6.0
Platform: unspecified Microsoft Windows
: NOR major
Target Milestone: ---
Assignee: Jasem Mutlaq
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-24 14:58 UTC by ubit.de
Modified: 2022-09-21 06:52 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ubit.de 2022-08-24 14:58:45 UTC
Using astroberry on the Raspi 4 2GB the new polar alignment assistent is not working. I have tried this on a windows pc with a remote connection the the indi drivers running on a Raspi too. Both behave the same. My settings lead to a FOV of 39,2' x 39,2' with a focal length of 1009 mm (effective) running on a EQ6-R Pro. But i have tested this with the INDI simulators with the same result. Because of the narrow FOV the usual polar alignment by visually moving a star is very uncomfortable as i have to repeat the PA multiple times until i have the triangle completely drawn in the image.

Description:
Plate solving in general is functional. I tried different solvers - everything is fine.

During the polar alignment 3 images are taken and solved without problems. When i choose to use "Plate Solve" and hit the Refresh button i only get error messages about the solver:

"Refresh solver failed: 3,4s"

Depending on the solver activated sometimes i even get the message that the solver has timed out.

I found in the sourcecode that the solver timeout during Refresh Phase is set to 10 seconds fixed - regardless of the settings in the align options. For ASTAP on a slow Raspi this is maybe not enough time.

In addition the solver radius is doubled  - compared to the normal solver process. Maybe this leads to problems with the solver? I am not fast enough to "capture" the generated files (*.cfg etc.) in the /tmp directory to compare them to successful solving - the are removed after a failed solver process and replaced by an empty /tmp/*.cancel file.

In general:
During the refresh phase the solver is not called the "usual way" like it is for the 3 images before. There are no entries in the "Solution Results" list in the EKOS align tab - nor is the command used for an external solver reported in the log area. There is no "real" error message parsed from the solver to the log are. This makes it nearly impossible to find out more detail about the error. At least the usual entries in the "Solution Results" and the "Command:..." in the log area should be added.

And it would be nice if the timeout for the solver during PA Refresh gets configurable through the settings. And maybe the find area for the solver too.

Sorry - i am unable to provide a detailed "verbose" log as my Raspi freezes if i try to enable logging for the solver.
Comment 1 Jasem Mutlaq 2022-08-25 05:06:54 UTC
Did you try to increase the exposure for refresh as well?

Please note that a long timeout is not going to work for PAA. It can work for plate-solving generally, but when performing PAA, you need to complete the process in a limited time.
Comment 2 ubit.de 2022-08-25 10:03:18 UTC
Yes - i tried different exposures. But there is no reason why the plate solving of the 3 align points is working and the refresh is not.

I know that the usual 500-600s timeout is not working for the refresh phase, but setting the timeout to fixed 10s maybe is a little short for slow systems and slow solvers. This timeout should be configurable.

And the logging and general procedure for the refresh solver calls should be identically to the normal plate solving - maybe except for some minor adjustments to prevent problems when turning the knobs on the polar wedge is done a little far to ensure that the plate solver finds a solution.

As we should be alway very close to the target position it maybe is possible to prevent the solver from trying a blind solve to speedup things if the captured image is blurred due to the motion from adjusting the mount.
Comment 3 Jasem Mutlaq 2022-09-21 06:52:38 UTC
This is fixed and should be resolved in 3.6.1