Why launch files automate startup in ROS - Test Your Understanding

Practice - 5 Tasks

1fill in blank

easy

Complete the code to start a ROS node using a launch file.

ROS

<launch>
  <node pkg="my_package" type="my_node" name="[1]"/>
</launch>

Drag options to blanks, or click blank then click option'

Anode_name

Bmy_node

Cstart_node

Dlaunch_node

Attempts:

3 left

💡 Hint

Common Mistakes

Using the package or type name instead of the node name.

The name attribute sets the node's name in the launch file.

2fill in blank

medium

Complete the code to include a parameter in the launch file.

ROS

<launch>
  <param name="robot_speed" value="[1]"/>
</launch>

Drag options to blanks, or click blank then click option'

A1.5

Bspeed

Ctrue

Dfast

Attempts:

3 left

💡 Hint

Common Mistakes

Using a string like 'fast' instead of a numeric value.

The value attribute sets the parameter's value, here a number for speed.

3fill in blank

hard

Fix the error in the launch file to correctly start two nodes.

ROS

<launch>
  <node pkg="pkg1" type="node1" name="node1"/>
  <node pkg="pkg2" type="[1]" name="node2"/>
</launch>

Drag options to blanks, or click blank then click option'

Anode1

Bnode

Cnode2

Dnode_type2

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong executable name for the second node.

The type attribute must match the executable name of the second node.

4fill in blank

hard

Fill both blanks to launch a node with a remapped topic.

ROS

<launch>
  <node pkg="my_pkg" type="talker" name="talker_node">
    <remap from="[1]" to="[2]"/>
  </node>
</launch>

Drag options to blanks, or click blank then click option'

A/chatter

B/new_chatter

C/old_topic

D/topic

Attempts:

3 left

💡 Hint

Common Mistakes

Swapping the from and to values.

The from attribute is the original topic, and to is the new topic name.

5fill in blank

hard

Fill all three blanks to launch a node with a parameter and output to screen.

ROS

<launch>
  <node pkg="my_pkg" type="listener" name="listener_node" output="[1]">
    <param name="[2]" value="[3]"/>
  </node>
</launch>

Drag options to blanks, or click blank then click option'

Ascreen

Bverbose

Cdebug_mode

Dtrue

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect output values or parameter names.

output="screen" shows node output in the terminal.
The parameter debug_mode is set to true.

Practice

1. Why do ROS launch files help automate the startup process of a robot system?

easy

A. They automatically fix errors in the robot's hardware.

B. They replace the need for writing any code in ROS.

C. They start multiple nodes and set parameters together with one command.

D. They only work for simulation, not real robots.

Solution

1. Step 1: Understand what launch files do

   Launch files group many commands to start nodes and set parameters in one place.

2. Step 2: Compare options to this function

   Only They start multiple nodes and set parameters together with one command. correctly describes this automation; others are incorrect or unrelated.

3. Final Answer:

   They start multiple nodes and set parameters together with one command. -> Option C

4. Quick Check:

   Launch files automate startup = A [OK]

Hint: Launch files bundle commands to run nodes and set parameters [OK]

Common Mistakes:

• Thinking launch files replace all coding
• Believing launch files fix hardware issues
• Assuming launch files only work in simulation

2. Which of the following is the correct way to include a node in a ROS launch file?

easy

A.

B.

C.

D.

Solution

1. Step 1: Recall ROS launch file syntax for nodes

   The correct tag is <node> with attributes pkg, type, and name.

2. Step 2: Check each option's correctness

   uses correct tags and attributes; others use wrong tags or attribute names.

3. Final Answer:

   <node pkg="turtlesim" type="turtlesim_node" name="sim" /> -> Option A

4. Quick Check:

   Correct node tag and attributes = A [OK]

Hint: Use syntax in launch files [OK]

Common Mistakes:

• Using <launch> instead of <node> for nodes
• Wrong attribute names like package or executable
• Using <start> tag which does not exist

3. Given this launch file snippet:

<launch>
  <node pkg=\"demo_pkg\" type=\"demo_node\" name=\"demo\" />
  <param name=\"speed\" value=\"5\" />
</launch>

What happens when you run this launch file?

medium

A. The demo_node starts with parameter speed set to 5.

B. Only the parameter speed is set; no nodes start.

C. The launch file will cause a syntax error and not run.

D. The demo_node starts but speed parameter remains default.

Solution

1. Step 1: Analyze the launch file content

   It starts demo_node from demo_pkg with name demo and sets parameter speed to 5.

2. Step 2: Understand launch file behavior

   Both node start and parameter setting happen together when launched.

3. Final Answer:

   The demo_node starts with parameter speed set to 5. -> Option A

4. Quick Check:

   Node runs + param set = D [OK]

Hint: Launch files run nodes and set parameters simultaneously [OK]

Common Mistakes:

• Thinking parameters don't apply to nodes
• Assuming syntax error due to param tag
• Believing node starts without parameters set

4. You wrote this launch file but it fails to start nodes:

<launch>
  <node pkg=\"my_pkg\" exec=\"my_node\" name=\"node1\" />
</launch>

What is the error and how to fix it?

medium

A. Node name cannot be 'node1'; use 'node' instead.

B. Attribute 'exec' is wrong; use 'type' instead.

C. Missing closing tag for <launch>.

D. Package name 'my_pkg' is invalid; must be 'pkg'.

Solution

1. Step 1: Identify incorrect attribute in node tag

   The attribute 'exec' is not valid; ROS launch files use 'type' to specify executable.

2. Step 2: Correct the attribute to fix the launch file

   Replace 'exec' with 'type' to properly start the node.

3. Final Answer:

   Attribute 'exec' is wrong; use 'type' instead. -> Option B

4. Quick Check:

   Use 'type' attribute for node executable = C [OK]

Hint: Use 'type' not 'exec' for node executable in launch files [OK]

Common Mistakes:

• Confusing 'exec' with 'type' attribute
• Forgetting to close launch tags
• Changing node names unnecessarily

5. You want to start two nodes and set a shared parameter using one launch file. Which approach best automates this startup?

hard

A. Start each node manually in separate terminals and set parameters individually.

B. Use a script to start nodes but set parameters only after nodes run.

C. Write separate launch files for each node and run them one after another.

D. Create a launch file that includes both nodes and sets the parameter once.

Solution

1. Step 1: Understand launch file purpose

   Launch files automate starting multiple nodes and setting parameters together.

2. Step 2: Evaluate options for automation

   Create a launch file that includes both nodes and sets the parameter once. uses one launch file to start both nodes and set parameter once, saving time and avoiding errors.

3. Step 3: Compare with other options

   Options A, C, and D require manual steps or multiple files, less efficient and error-prone.

4. Final Answer:

   Create a launch file that includes both nodes and sets the parameter once. -> Option D

5. Quick Check:

   One launch file for all nodes and params = B [OK]

Hint: Use one launch file to start all nodes and set shared params [OK]

Common Mistakes:

• Running nodes manually instead of using launch files
• Splitting nodes into multiple launch files unnecessarily
• Setting parameters after nodes start causing delays