It is a good practice to include messages that indicate what the program is doing. But we must do it without compromising on the efficiency of our software and the clarity of its output. In ROS, we have an API that covers both features, built on top of log4cxx
(a port of the well-known log4j
logger library). In brief, we have several levels of messages, which might have a name (named messages) and depend on a condition or even throttle. All of them have a null footprint on performance if they are masked by the current verbosity level (even at compile time). They also have full integration with other ROS tools to visualize and filter the messages from all the nodes running.
Learning ROS for Robotics Programming Second Edition
Learning ROS for Robotics Programming Second Edition
Overview of this book
Table of Contents (27 chapters)
Learning ROS for Robotics Programming Second Edition
Credits
About the Author
Acknowledgments
About the Author
Acknowledgments
About the Author
Acknowledgments
About the Author
Acknowledgments
About the Reviewer
About the Reviewer
Acknowledgments
About the Reviewers
www.PacktPub.com
Preface
Free Chapter
Getting Started with ROS Hydro
ROS Architecture and Concepts
Visualization and Debug Tools
Using Sensors and Actuators with ROS
Computer Vision
Point Clouds
3D Modeling and Simulation
The Navigation Stack – Robot Setups
The Navigation Stack – Beyond Setups
Manipulation with MoveIt!
Index
Customer Reviews