Add automated ARUCO logging mode#58
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Draft for #57.
This adds a pipeline ARUCO logging mode for the pilot view. The camera frame path now detects ARUCO markers, records each marker ID once in first-seen order, and exposes the current mode/log state through small API endpoints.
The pilot HUD gets Start/Stop and Clear controls plus visible marker IDs and the ordered log, so operators can run the pipeline challenge logging without leaving the camera view.
Validation:
env UV_CACHE_DIR=/tmp/uv-cache uv run --frozen --group dev pytestenv UV_CACHE_DIR=/tmp/uv-cache uv run --frozen --group lint ruff check .git diff --check