ROS 2 gotcha: use node.get_clock().now(), not time.time(), in simulation
4310sy · x · 2026-09-03
A common robotics pitfall: in ROS 2, don't grab timestamps with Python's time.time() (system clock). Use node.getclock().now() instead.
Simulation nodes may run on a different time axis from the real world, so ROS 2's clock API is required to stay consistent with sim time.
More from coding & agent
- Vector Ingestion at 50M Rows: The Pitfalls Your 1,000-Doc Prototype Won't Reveal — victorialslocum · 2026-09-03
- Reddit user swears by local AI harness Vellum: free, proactive, but nobody talks about it — Cooperman411 · 2026-09-03
- Qwen Code v0.23.0 ships Anthropic stream hang fix, daemon memory tasks and more — qwen-code-ci-bot · 2026-09-03
- Dev Builds an Interactive 'Multiverse TV' Where Twitch Chat Picks What Plays Next — d_pit · 2026-09-03
- Brian Kernighan and Rob Pike wrote a regex matcher in a few dozen lines of C — blaizedsouza · 2026-09-03
- tinyfool: doing research with AI is like having grad students write your code — tinyfool · 2026-09-03