name: route-log-analysis
description: "Guides openpilot route identifiers, qlog/rlog access, LogReader
APIs, message filtering, event summaries, and route-cache troubleshooting."
disable-model-invocation: true
metadata:
disco-role: operating
license: MIT
route-log-analysis
Use this sub-skill when a task involves openpilot route IDs, segment ranges, qlogs/rlogs, LogReader, Route, SegmentRange, logMessage, alerts/events, CAN messages, route cache/source behavior, or local-vs-remote log access.
Read first
Bundled helpers
Workflow
- Normalize the route selector first. A task may use
dongle|timestamp, dongle/timestamp, --segment, /segment, ranges such as /4:6, and selectors /q or /r.
- Decide whether the user has local files or needs remote route access. Remote routes may require authentication and network/cache space.
- Prefer
qlog for quick event/alert/fingerprint scans; use rlog when full message fidelity is required.
- Keep analysis finite: avoid loading large videos, all segments, or route ranges without a reason.
- Route CAN/FW fingerprint results or process-replay validation to car-ports-and-controls.
- Route live service timing or Params/msgq behavior to core-services-and-runtime.
Validation choices
Good CPU-safe checks are route string parsing, synthetic local qlog reads, help/parser checks for bundled scripts, and selected openpilot/tools/lib/tests cases. Skip route downloads, account-only routes, GUI replay, and process-replay reference downloads unless prerequisites and time budget are explicit.