Velune Trace
Find where to look first in one large MCAP log. Trace ranks, per topic, the time windows with the most irregular message timing — gaps, jitter, count shortfalls, out-of-order timestamps — so you open the right range in your own viewer.
Ranked windows · /lidar_topBundled sample log
- Rank
- #1 — window 2
- Window
- 1 s · count 19 of 20 expected
- Evidence
- max gap 0.100 s · jitter 0.011 s
Real output
One command. Ranked windows.
$ ./bin/velune validation-report examples/sample.mcap \
--export-dir velune_report --window-sec 1 --top 5 --allowed-lateness-sec 2
# velune_report/summary.md (excerpt)
### /lidar_top
- Count: 99 · Expected count/window: 20
Top evidence windows:
- Window 2: count=19, expected=20, max_gap=0.100000000, jitter=0.011453071
- Window 0: count=20, expected=20, max_gap=0.050000000, jitter=0.000000000
LOCAL_ONLY_NOTICE=No telemetry or automatic upload was performed.
Output of the bundled sample log, run from the repository. Values exact; lines shortened. A ranking is a review order, not a fault probability.
What you get
Local, reproducible files.
Nothing is uploaded and the source log is not modified. The files leave out raw payloads, but their metadata can still be sensitive: review them, and have the data owner approve, before sharing any of them.
- summary.mdReadable timing summary and top evidence windows per topic. Start here.
- evidence_windows.jsonRanked windows with count, expected count, max gap and jitter.
- topic_profile.jsonTopic-level timing profile across the whole log.
- shareable_anonymous_report.jsonMachine-readable copy of the report. Despite its name it is not anonymized: like summary.md, evidence_windows.json and topic_profile.json, it contains your original topic names and the absolute recording times.
- report_manifest.json · SCHEMA.mdBundle identity and SHA-256 integrity metadata; a description of every field.
Boundaries
A starting point, not a conclusion.
Trace does
- Read MCAP files entirely on your machine
- Profile per-topic message timing
- Rank windows by gaps, jitter, count shortfall and ordering
- Write Markdown and JSON with integrity hashes
Trace does not
- Replace your viewer or recording tools
- Decide root cause, fault or safety
- Tell you whether a window is normal
- Send telemetry or upload your logs
Trace works inside one log. To see what changed between two separate runs, use VeluneOS Compare — Trace is not required for it.