Skip to content

pointing precision #32

Description

@gasilvis

Did a run with the S50 in alt-az and all attempts failed due to pointing problems:
22:56:55 [INFO] seevar.pilot — A7 solve-field start: file=NSV_23386_scope01_20260620T025655_VERIFY.fits ra=264.6651 dec=61.2378 radius=5.0 timeout=35s
22:57:09 [WARNING] seevar.pilot — A7 solve-field failed: rc=0 stderr=
22:57:09 [INFO] seevar.fsm — Bridge: [A7] Verify solve failed: solve-field failed (0)
22:57:09 [INFO] seevar.pilot — [A7] Verify solve failed: solve-field failed (0)
22:57:09 [INFO] seevar.fsm — Bridge: [A7] Pointing verify failed: solve-field failed (0)
22:57:09 [INFO] seevar.pilot — [A7] Pointing verify failed: solve-field failed (0)
22:57:09 [ERROR] seevar.fsm — [A11] Frame 1 failed: Verify solve failed after retries: solve-field failed (0)
22:57:09 [INFO] seevar.fsm — 🔄 FSM State updated to: ERROR
22:57:09 [INFO] seevar.orchestrator — [A12] Commit failure state

I found the pointing image in data/verify_buffer and ran it through nova.astrometry.net. Some of them were off by a mile. Like 32 deg in RA and 4 deg in dec.

I saw the note in config.toml:

For quick pre-alignment before a session, run:

.venv/bin/python dev/tools/telescope/prealign_pointing.py --points 3 --exposure-sec 5

But this faulted with:
raceback (most recent call last):
File "/home/sgeo/seevar/dev/tools/telescope/prealign_pointing.py", line 31, in
from alpaca.camera import Camera
ModuleNotFoundError: No module named 'alpaca'

Recommendations?

Could the Verify step, when it fails, do a re-sync of the S50 position to the results of the last plate solve?

George

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions