Repository navigation
feat: the hotdog command for operators, status at a glance - #10
Merged
Merged
Conversation
agus-darmawan
added a commit
that referenced
this pull request
Nov 1, 2026
feat: the hotdog command for operators, status at a glance
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
Operators at a substation shouldn't type
ros2 service call /inspection/add_target hotdog_interfaces/srv/AddTarget "{...}". One command per task:hotdog(scripts/hotdog.sh, alias byscripts/setup.sh install cli, now a default component):status,patrol [route],return,stop,pause/resume,estop/release,routes,site [name],anchor,teach start | point [dwell] | target <name> [thermal] [acoustic] [strips=N] [max=C] | stop,dock,stand/sit,ambient <degC>,schedule on|off|show,reports,alert-test,logs,restart.CALL_TIMEOUT(30 s) instead of hanging on a stack that isn't running; numbers are passed as floats (Foxy refuses8for a float field);strips=/max=imply a thermal target; bad numbers fail before any call.ros2 run hotdog status: the robot at a glance in one screen — patrol (state, route, minutes, points, findings, next scheduled), health, localization drift, control (mode, e-stop, field), battery, inspection (pod / acoustic, ambient, last point), navigation, alerts waiting, report URL, disk free; colored on a terminal. Formatting inhotdog/status.py(pure, tested).scripts/env.sh: a shell with the service's environment (+hnodeto run one node like the launch).LOG_DAYS(7) deleted at each start (ExecStartPre), so~/.ros/lognever fills the disk.How it was tested
pre-commit runon every changed and new file (shellcheck incl.)scripts/test(runs in CI's scripts job, Python 3.8): every command against a stand-inros2— the exact calls, float literals, implied thermal, bad numbers refused, unknown commandhotdogunit + style: 34 (status lines, nothing received, names, colors)scripts/setup.sh install clitwice in a throw-away HOME: alias added oncehotdog statuswith the stack runningChecklist
Generated by Claude Code