Conversation
Detect ArUco markers from extracted frames, persist ArUco detections, and merge them with existing portal observations so loop-closure and manifest outputs can use both marker sources without breaking legacy scans. Made-with: Cursor
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
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.
Detect ArUco markers from extracted frames, persist ArUco detections, and merge them with existing portal observations so loop-closure and manifest outputs can use both marker sources without breaking legacy scans.
Summary
utils/aruco_detection.pyto detect ArUco markers from extracted frames, estimate 6-DoF marker poses with camera intrinsics, convert to OpenGL coordinates, and writeArUcoDetections.csvprocess_frames()and beforeload_scan()so detections are available to loop-closure inputsload_scan()while preserving DMT priority (PortalDetections.csvthenObservations.csv) and improving resilience when legacy portal files are missingportal_sizesforaruco_*IDs using the default marker size so downstream portal CSV and manifest generation remain valid