Generated by GPT-5-mini| RViz | |
|---|---|
| Name | RViz |
| Author | Willow Garage |
| Developer | Open Robotics |
| Released | 2011 |
| Programming language | C++ |
| Operating system | Linux, macOS (partial), Windows (ROS 2) |
| License | BSD |
RViz is a 3D visualization tool used primarily within the Robot Operating System ecosystem to inspect sensor data, state estimates, and simulated environments. It provides realtime rendering for robotics researchers and developers collaborating across projects at organizations such as Willow Garage, Open Robotics, Stanford University, Massachusetts Institute of Technology, and industry labs like Toyota Research Institute and NVIDIA. RViz integrates with simulation and middleware tools including Gazebo (software), ROS 2, and frameworks used by teams at NASA, European Space Agency, and commercial partners.
RViz serves as an interactive viewer for robot models, point clouds, occupancy grids, and transform trees produced by middleware such as Robot Operating System and ROS 2. It visualizes inputs from sensors and estimators used in projects by Google robotics initiatives, Amazon Robotics, and academic groups at Carnegie Mellon University, ETH Zurich, and University of Oxford. Users commonly employ RViz alongside simulation platforms like Gazebo (software), Webots, and CoppeliaSim as well as mapping tools developed in research consortia like Open Source Robotics Foundation and industry teams at Bosch.
Development began at Willow Garage during early Robot Operating System adoption, with contributions from engineers who later joined organizations such as OSRF (now Open Robotics), Google, and Intel. RViz evolved through community-driven releases coordinated by maintainers from Open Robotics and contributors affiliated with universities including University of Washington and Imperial College London. Milestones include integration with simulation systems like Gazebo (software), support for ROS 2 driven by efforts at Open Robotics and standardization influenced by projects at IEEE working groups and collaborative code contributions from companies such as Microsoft and NVIDIA.
RViz is implemented mainly in C++ and leverages graphics libraries and window systems employed by tools from KDE and GNOME ecosystems; it interfaces with OpenGL and visualization libraries used by projects at Kitware and The Khronos Group. Core components include the display manager, render panel, and plugin loader; these interact with middleware stacks like ROS 2 and build systems such as CMake. RViz consumes transform data from the tf (ROS) system and robot descriptions authored in URDF and xacro, which are commonly produced by teams at Boston Dynamics and research labs at Harvard University.
RViz renders 3D meshes, point clouds, laser scans, and occupancy grids used in mapping and planning applications pioneered at institutions like ETH Zurich and Carnegie Mellon University. It supports visualization of trajectory planning outputs from packages developed in collaboration with groups at Google and Toyota Research Institute, and displays diagnostics and action states employed by systems built by NASA robotic teams. Visual tools include adjustable color maps, clipping planes, and interactive camera controls familiar to users of ParaView, MeshLab, and tools developed at Kitware.
RViz subscribes to message types standardized across ROS and ROS 2 specifications, including sensor messages used by platforms from Clearpath Robotics and TurtleBot projects, navigation messages used in software from Autoware, and custom messages contributed by laboratories at UC Berkeley and University of Michigan. Typical supported types include point cloud formats produced by sensors from Velodyne, Ouster, and Leica Geosystems; image streams from camera vendors like Intel (RealSense) and FLIR Systems; and transforms published by localization stacks such as those developed at Oxford Robotics Institute.
A typical workflow involves launching RViz while bringing up a robot description, sensor drivers, and state publishers used in demonstrations by teams at Willow Garage and Open Robotics. Users configure displays and fixed frames, inspect tf trees and diagnostics produced by controllers from ROS Control and planners from MoveIt!, and iterate on perception stacks tested in benchmarks organized by DARPA and European Commission projects. RViz is integrated into development cycles with continuous integration tools used by contributors at GitHub, GitLab, and automated testing systems employed by Travis CI and Jenkins.
RViz provides a plugin architecture widely extended by community packages from groups at Open Robotics, ROS Industrial, and academic labs at University of Toronto and Technische Universität München. Plugins enable custom display types, interactive markers used in human-robot interaction studies at MIT Media Lab, and panel widgets for mission control developed by companies like Siemens and ABB. The extensibility model aligns with component systems used in projects such as Qt and fosters integrations with perception stacks from Intel and planning frameworks from Autoware.
RViz has limitations in headless or cloud-native deployments compared with web-based visualizers and browser UIs developed by teams at Google (e.g., internal visualization tools), or streaming viewers used by NVIDIA and Microsoft. Performance issues arise with very large point clouds from vendors like Velodyne or dense meshes produced in photogrammetry workflows by Agisoft, prompting users to consider alternatives such as Foxglove Studio, custom OpenGL applications, or visualization packages like ParaView and Open3D favored by research groups at Stanford University and University of Cambridge.
Category:Robotics software