Publish-subscribe communication model in ROS - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the publish-subscribe communication model in ROS?

It is a way for nodes to communicate by sending messages without knowing each other directly. Publishers send messages to topics, and subscribers receive messages from those topics.

beginner

What is a 'topic' in the publish-subscribe model?

A topic is a named channel where messages are sent by publishers and received by subscribers. It acts like a radio station frequency for messages.

beginner

How do publishers and subscribers interact in ROS?

Publishers send messages to a topic. Subscribers listen to that topic and get the messages. They do not communicate directly but through the topic.

intermediate

Why is the publish-subscribe model useful in robotics?

It allows many parts of a robot system to share information easily and independently. Nodes can join or leave without breaking communication.

intermediate

What happens if no subscriber listens to a topic?

The publisher still sends messages, but no one receives them. This does not cause errors; the system is designed to handle this gracefully.

In ROS, what does a publisher do?

A Sends messages to a topic

B Receives messages from a topic

C Creates a new node

D Subscribes to a service

Publishers send messages to topics for subscribers to receive.

What is the role of a subscriber in the publish-subscribe model?

A To send messages to other nodes

B To listen and receive messages from a topic

C To create topics

D To manage node connections

Subscribers listen to topics and receive messages published there.

If a topic has no subscribers, what happens to the messages published?

A They are sent to all nodes

B They are stored until a subscriber appears

C They cause an error

D They are lost and not delivered

Messages sent to topics without subscribers are not delivered or stored.

Which of these best describes a topic in ROS?

A A direct connection between two nodes

B A hardware interface

C A named channel for message exchange

D A service call

A topic is a named channel where messages are published and subscribed.

Why is the publish-subscribe model preferred in ROS for communication?

A Because it allows flexible, decoupled communication

B Because it requires nodes to know each other

C Because it uses less memory

D Because it is synchronous

The model allows nodes to communicate without direct knowledge of each other, making the system flexible.

Explain how the publish-subscribe communication model works in ROS using a real-life analogy.

Think of a radio station and listeners.

Describe the advantages of using the publish-subscribe model in a robot system.

Consider how different parts of a robot share information.

Practice

1. What is the main role of a publisher in the ROS publish-subscribe model?

easy

A. To create new topics dynamically

B. To receive messages from a topic

C. To store messages in a database

D. To send messages to a topic

Solution

1. Step 1: Understand the publish-subscribe roles

   In ROS, publishers send messages to topics, while subscribers receive messages from topics.

2. Step 2: Identify the publisher's function

   The publisher's job is to send data to a topic so subscribers can receive it.

3. Final Answer:

   To send messages to a topic -> Option D

4. Quick Check:

   Publisher = sends messages [OK]

Hint: Publisher sends, subscriber receives messages [OK]

Common Mistakes:

• Confusing publisher with subscriber
• Thinking publisher stores messages
• Assuming publisher creates topics

2. Which of the following is the correct way to create a ROS publisher in Python?

easy

A. pub = rospy.Publisher('topic_name', callback, queue_size=10)

B. pub = rospy.Subscriber('topic_name', String, callback)

C. pub = rospy.Publisher('topic_name', String, queue_size=10)

D. pub = rospy.Subscriber('topic_name', String)

Solution

1. Step 1: Recall publisher syntax in ROS Python

   The correct syntax uses rospy.Publisher with topic name, message type, and queue size.

2. Step 2: Check each option

   pub = rospy.Publisher('topic_name', String, queue_size=10) matches the correct syntax. Using Subscriber instead of Publisher is incorrect. pub = rospy.Publisher('topic_name', callback, queue_size=10) incorrectly uses callback instead of message type.

3. Final Answer:

   pub = rospy.Publisher('topic_name', String, queue_size=10) -> Option C

4. Quick Check:

   Publisher syntax = rospy.Publisher(topic, type, queue_size) [OK]

Hint: Publisher uses rospy.Publisher(topic, type, queue_size) [OK]

Common Mistakes:

• Using Subscriber instead of Publisher
• Passing callback instead of message type
• Omitting queue_size parameter

3. Given the following ROS Python code snippet, what will be printed when a message with data 'Hello' is published?

import rospy
from std_msgs.msg import String

def callback(msg):
    print(f'Received: {msg.data}')

rospy.init_node('listener')
sub = rospy.Subscriber('chatter', String, callback)
rospy.spin()

medium

A. Received: Hello

B. Hello

C. Received: msg

D. No output

Solution

1. Step 1: Understand the callback function

   The callback prints 'Received: ' followed by the message's data field.

2. Step 2: Analyze the message content

   The message data is 'Hello', so the print statement outputs 'Received: Hello'.

3. Final Answer:

   Received: Hello -> Option A

4. Quick Check:

   Callback prints 'Received: ' + msg.data [OK]

Hint: Callback prints 'Received: ' plus message data [OK]

Common Mistakes:

• Printing message object instead of data
• Expecting just the message data without prefix
• Thinking no output occurs without explicit print

4. Identify the error in this ROS Python subscriber code:

import rospy
from std_msgs.msg import String

def callback(msg):
    print(msg.data)

rospy.init_node('listener')
sub = rospy.Subscriber('chatter', String)
rospy.spin()

medium

A. Incorrect message type used

B. Missing callback function in Subscriber

C. Node not initialized

D. No import for rospy

Solution

1. Step 1: Review Subscriber syntax

   Subscriber requires three arguments: topic name, message type, and callback function.

2. Step 2: Check the given code

   The Subscriber call misses the callback argument, causing an error.

3. Final Answer:

   Missing callback function in Subscriber -> Option B

4. Quick Check:

   Subscriber needs callback argument [OK]

Hint: Subscriber must include callback function [OK]

Common Mistakes:

• Omitting callback in Subscriber
• Confusing Publisher and Subscriber arguments
• Forgetting to initialize node

5. You want to create a ROS system where multiple nodes publish sensor data to the same topic, and one node subscribes to process all data. Which feature of the publish-subscribe model makes this possible?

hard

A. Topics allow multiple publishers and subscribers to communicate independently

B. Each topic can have only one publisher and one subscriber

C. Publishers must know all subscribers to send messages

D. Subscribers can only listen to one topic at a time

Solution

1. Step 1: Understand topic communication in ROS

   Topics support multiple publishers and subscribers simultaneously, enabling flexible communication.

2. Step 2: Analyze the scenario

   Multiple nodes publishing to the same topic and one subscriber processing all data is possible because topics allow many publishers and subscribers.

3. Final Answer:

   Topics allow multiple publishers and subscribers to communicate independently -> Option A

4. Quick Check:

   Topics support many-to-many communication [OK]

Hint: Topics support many publishers and subscribers [OK]

Common Mistakes:

• Thinking topics allow only one publisher or subscriber
• Believing publishers must know subscribers
• Assuming subscribers can listen to only one topic