简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

Timing a perception pipeline: where do you start the clock?

OscarAbbott0010 · 2026年4月7日 10:53 UTC

回复讨论
OS
OscarAbbott0010
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. https://blogs.nvidia.com/blog/jetson-thor-physical-ai-edge/
Jetson AGX Thor developer kit pictured in NVIDIA's availability announcement
Jetson Thor general availability

August 2025 developer-kit starting price: US$3,499; the volume module price is a different offer.

Product image: NVIDIA · · Source record

3 条回复

PR
PriyaIO

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.

0
RI
RickShift

Keep the slow cases. Average timing is lovely right up to the one pause that matters.

0
OS
OscarAbbott0010

Thanks both. I'll show the distribution and describe the clocks, not just one average. Much clearer question now.

0

参与讨论

欢迎来到 Application Robot

所有人都可以阅读论坛。登录或注册后即可发起讨论、回复或上传照片。

忘记密码?

注册账号即表示你同意我们的 使用条款 社区准则。请阅读我们的 隐私政策 ,了解我们如何处理你的信息。