Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Launch File Issue #29

Closed
mmohmpat opened this issue Jun 12, 2019 · 2 comments
Closed

Launch File Issue #29

mmohmpat opened this issue Jun 12, 2019 · 2 comments

Comments

@mmohmpat
Copy link

Hello,

I am having trouble launching ROS with the associated launch file using the following command,
roslaunch orb_slam_2_ros orb_slam2_r200_mono.launch

This produces the following error,
RLException: [orb_slam2_r200_mono.launch] is neither a launch file in package [orb_slam_2_ros] nor is [orb_slam_2_ros] a launch file name The traceback for the exception was written to the log file
I have tried following the readme and have executed the following,
source devel/setup.bash

I have also tried following the advice given by http://answers.ros.org/question/143496/roslaunch-is-neither-a-launch-file-in-package-nor-is-a-launch-file-name/. The rospack find orb_slam_2_ros command returned that the package was not found. Giving the absolute path for the commands tried did not yield different results.

(I am using ROS Melodic.)

Any help or advice would be greatly appreciated.

Thanks

@lennarthaller
Copy link
Collaborator

This doesnt seem to be an issue with the launch file but with your setup. Given that you compiled this package without errors and ran source devel/setup.bash in your catkin workspace you should be able to launch it.

@sidml
Copy link

sidml commented Dec 5, 2019

This error happens when you built the new workspace with catkin build and the other workspace was built using catkin_make.

I solved this by making the workspace using catkin_make.

This question is relevant. https://answers.ros.org/question/205976/sourcing-from-multiple-workspaces/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants