Repository navigation
chore: dev container and tmux layouts for HotDog on Foxy - #13
Merged
Merged
Conversation
…, alerts and status
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.
What and why
Loose ends of the developer and debug tooling:
fast_lio(the same problem CI had): skip FAST-LIO, legKILO and Livox indocker/Dockerfiletoo.compose.yamlandscripts/dev.shdrop the Humble and Jazzy containers from the template; HotDog runs Foxy on the robot and CI. CI's compose check follows.robotgets the pod, inspection, patrol, reports and alerts windows and ahotdog statuspane;simwatcheshotdog status.timesync.sh: written for any PTP LiDAR (it said Livox Mid-360); notes that the Airy are stamped on arrival and need no PTP.How it was tested
pre-commit run,bash -n,scripts/testGenerated by Claude Code