catkin workspace creation in ROS - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the command to create a new catkin workspace directory named 'my_ws'.

ROS

mkdir -p ~/[1]/src

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

Aworkspace

Bcatkin_ws

Cmy_ws

Dros_ws

Attempts:

3 left

💡 Hint

Common Mistakes

Forgetting to create the 'src' folder inside the workspace

Using a wrong folder name that doesn't match the workspace name

The command mkdir -p ~/my_ws/src creates the workspace folder my_ws with a src subfolder, which is required for a catkin workspace.

2fill in blank

medium

Complete the command to initialize the catkin workspace inside the 'src' folder.

ROS

cd ~/my_ws/src && [1]

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

Acatkin_make

Bcatkin_init_workspace

Ccatkin_create_pkg

Dcatkin_build

Attempts:

3 left

💡 Hint

Common Mistakes

Using catkin_make before initializing the workspace

Confusing catkin_create_pkg with workspace initialization

The command catkin_init_workspace initializes the workspace by creating necessary files inside the src folder.

3fill in blank

hard

Fix the error in the command to build the catkin workspace from the root folder.

ROS

cd ~/my_ws && [1]

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

Acatkin_init_workspace

Bcatkin_create_pkg

Ccatkin_build

Dcatkin_make

Attempts:

3 left

💡 Hint

Common Mistakes

Trying to build before initializing the workspace

Using catkin_create_pkg to build instead of create packages

The correct command to build the workspace from its root folder is catkin_make. It compiles all packages inside the workspace.

4fill in blank

hard

Fill both blanks to source the setup file and verify the ROS environment variables.

ROS

source ~/my_ws/devel/[1] && echo $[2]

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

Asetup.bash

BROS_PACKAGE_PATH

Csetup.sh

DROS_MASTER_URI

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong setup file like setup.sh

Checking an unrelated environment variable

Sourcing setup.bash sets up the environment for the workspace. Checking ROS_PACKAGE_PATH confirms the workspace packages are recognized.

5fill in blank

hard

Fill all three blanks to create a new package named 'robot_control' with dependencies on 'rospy' and 'std_msgs'.

ROS

cd ~/my_ws/src && catkin_create_pkg [1] [2] [3]

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

Arobot_control

Brospy

Cstd_msgs

Droscpp

Attempts:

3 left

💡 Hint

Common Mistakes

Using the wrong package name

Including dependencies not needed or misspelled

Mixing C++ and Python dependencies incorrectly

The command creates a package named robot_control depending on rospy and std_msgs. These dependencies are required for Python ROS nodes and standard messages.

Practice

1. What is the purpose of creating a catkin workspace in ROS?

easy

A. To organize and build your ROS packages in one place

B. To install ROS system-wide dependencies

C. To run ROS nodes without any packages

D. To update the ROS core automatically

Solution

1. Step 1: Understand what a catkin workspace is

   A catkin workspace is a folder where you keep your ROS packages organized and build them together.

2. Step 2: Identify the purpose of the workspace

   It helps you manage your own ROS projects, not system-wide installations or running nodes without packages.

3. Final Answer:

   To organize and build your ROS packages in one place -> Option A

4. Quick Check:

   Workspace = Organize & build packages [OK]

Hint: Workspace holds your ROS projects and builds them [OK]

Common Mistakes:

• Confusing workspace with system installation
• Thinking workspace runs nodes alone
• Assuming workspace updates ROS core

2. Which command correctly creates the source folder inside a catkin workspace named catkin_ws in your home directory?

easy

A. catkin_make ~/catkin_ws/src

B. mkdir ~/catkin_ws/src

C. mkdir -p ~/catkin_ws/src

D. source ~/catkin_ws/src

Solution

1. Step 1: Understand the folder creation command

   The mkdir -p command creates the full directory path, including parent folders if missing.

2. Step 2: Identify the correct command for creating src inside catkin_ws

   mkdir -p ~/catkin_ws/src uses mkdir -p ~/catkin_ws/src, which creates both catkin_ws and src if needed.

3. Final Answer:

   mkdir -p ~/catkin_ws/src -> Option C

4. Quick Check:

   Use mkdir -p for nested folders [OK]

Hint: Use mkdir -p to create nested folders at once [OK]

Common Mistakes:

• Using mkdir without -p and missing parent folder
• Confusing catkin_make with mkdir
• Trying to source a folder instead of creating it

3. After creating your catkin workspace folder and src directory, what is the output of running catkin_make inside ~/catkin_ws?

medium

A. Error: src folder missing

B. Build successful with devel and build folders created

C. No output, command ignored

D. Workspace deleted

Solution

1. Step 1: Understand what catkin_make does

   It builds the packages inside the src folder and creates devel and build folders for development and build files.

2. Step 2: Predict output after running catkin_make in a valid workspace

   Since src exists, it will build successfully and create those folders.

3. Final Answer:

   Build successful with devel and build folders created -> Option B

4. Quick Check:

   catkin_make builds workspace and creates folders [OK]

Hint: catkin_make builds and creates devel/build folders [OK]

Common Mistakes:

• Expecting error if src exists
• Thinking catkin_make deletes workspace
• Assuming no output or ignored command

4. You created a catkin workspace but forgot to source the setup file. What problem will you face?

medium

A. catkin_make will fail with syntax errors

B. The workspace will delete itself automatically

C. Your system will crash

D. ROS commands and packages from your workspace won't be recognized

Solution

1. Step 1: Understand the role of sourcing the setup file

   Sourcing devel/setup.bash sets environment variables so ROS can find your workspace packages.

2. Step 2: Identify the effect of not sourcing

   Without sourcing, ROS commands won't find your workspace packages, so they won't be recognized.

3. Final Answer:

   ROS commands and packages from your workspace won't be recognized -> Option D

4. Quick Check:

   Source setup file to use workspace [OK]

Hint: Always source setup.bash to use your workspace [OK]

Common Mistakes:

• Thinking workspace deletes itself
• Expecting catkin_make syntax errors
• Assuming system crashes

5. You want to create a new catkin workspace named my_ws in your home directory and build it. Which sequence of commands is correct?

hard

A. mkdir -p ~/my_ws/src && cd ~/my_ws && catkin_make && source devel/setup.bash

B. cd ~/my_ws && mkdir src && catkin_make && source ~/my_ws/devel/setup.bash

C. mkdir ~/my_ws && catkin_make ~/my_ws/src && source ~/my_ws/setup.bash

D. mkdir -p ~/my_ws/src && catkin_make src && source ~/my_ws/devel/setup.bash

Solution

1. Step 1: Create workspace and src folder correctly

   Use mkdir -p ~/my_ws/src to create both folders at once.

2. Step 2: Navigate to workspace and build

   Change directory to ~/my_ws and run catkin_make to build the workspace.

3. Step 3: Source the setup file

   Source devel/setup.bash inside the workspace to use the built packages.

4. Final Answer:

   mkdir -p ~/my_ws/src && cd ~/my_ws && catkin_make && source devel/setup.bash -> Option A

5. Quick Check:

   Create src, build, source setup.bash [OK]

Hint: Create src, cd workspace, catkin_make, then source setup.bash [OK]

Common Mistakes:

• Running catkin_make outside workspace folder
• Not sourcing the correct setup file
• Using wrong paths in commands