OscarAbbott0010 · 7 Apr 2026, 10:53 UTC
Back to my Thor question from August. I'm defining the benchmark before deciding whether to buy anything. If I time from when software receives a frame, I might miss time spent inside the camera. What timestamps would you want in a robot-perception report? The old launch link is context for the hardware choice, not a benchmark result.
Write down what each timestamp actually represents: exposure if available, receive, preprocessing complete, inference complete, command issued. Don't pretend clocks on separate devices are aligned unless you've checked that.
0pointsKeep the slow cases. Average timing is lovely right up to the one pause that matters.
0pointsThanks both. I'll show the distribution and describe the clocks, not just one average. Much clearer question now.
0pointsThis discussion is closed to new replies after six months without activity. Last activity: .