Skip to content

Patch v2.2.7 - Rerun Post-Match Logging

Choose a tag to compare

@Unknownuserfrommars Unknownuserfrommars released this 11 Jul 07:02

v2.2.7 - Rerun Post-Match Logging On By Default

Config-only release on top of v2.2.6 (which is frozen at its released state). Implements the team's rerun.docx usage guide, adapted to tournament conditions where matches run unobserved (ethernet unplugged, no live monitoring allowed).

What changed

  • rerunLog.enable_file: true - every match now writes .rrd recordings to /home/booster/Workspace/rrlog, split into 5-minute files. This is the post-match flight recorder: camera stream with detections, field-map replay (green circle = self), every tree/Decide decision with its reasons, team lead/cost election, comms latency, debug/RLVisionKick and debug/teamSignal channels.
  • rerunLog.img_interval: 1 -> 10 (~3 fps image logging instead of every frame) - protects match-day CPU on the Orin and keeps file sizes sane.
  • enable_tcp stays false for matches; the config now documents the live-view workflow for pre-match testing: set enable_tcp: true + server_ip to your PC's wired IP, open the Rerun Viewer on the PC first, then ./scripts/start.sh.

Usage

  • After a match: scp booster@<robot>:~/Workspace/rrlog/*.rrd . and open in the Rerun Viewer (top-left menu -> Open). File names are the recording start timestamp.
  • Viewer/SDK version must match: check the robot's rerun_sdk version, then pip install rerun-sdk==<version> on your PC (the rerun command is the viewer) or download the matching viewer binary from Rerun's GitHub releases.
  • Housekeeping: clear ~/Workspace/rrlog before each match day so disk does not fill.
  • Calibration check trick (from rerun.docx): place the ball at a measured spot; the viewer shows ball X/Y/C in robot frame. If off, adjust vision.yaml pitch_compensation (shifts X) / yaw_compensation (shifts Y) until they match reality.

Packaging

  • Repository source folder v2.2.7/ excludes TensorRT .engine model files.
  • Release asset v2.2.7.zip contains the full patch folder, including model engines.
  • Config-only change vs v2.2.6 - no rebuild needed on robots that already built v2.2.6; just update src/brain/config/config.yaml (it is read at launch).