[my_start_training_deepq_version.launch] is neither a launch file in package [my_moving_cube_pkg] nor is [my_moving_cube_pkg] a launch file name The traceback for the exception was written to the log file
My launch file is the same as in the notebook.
I attach ss.
make sure you build the workspace and source the setup file. Otherwise ROS doesn’t know those names;
roscd; cd …
catkin_make
source ~/catkin_ws/devel/setup.bash
WARNING: make sure to create new packages by calling catkin_create_pkg and not just creating a new folder and copying the files from a different package. The package.xml and CMakeLists.txt have the package name defined on top. THIS is where the package is defined, not the folder name. Make sure it is defined correctly here.
I carry out these commands, according to the course (pictured), but the problem remains. My package contains these files. I created it using the catkin_create_pkg command.
Can you do roscd to the package my_moving_cube_pkg? Is the my_start_training_deepq_version.launch in the launch folder?
And as @ simon.steinmann91 said, please check you compiled and sourced.
I have same problem here. The reason is after source python3 setup file, “source ~/.catkin_ws_python3/devel/setup.bash”, the roslaunch cannot find the package. But if does not source the setup file, it will have problem to import tf package. The package run successfully under python2 environment. I also tired to do “catkin_make” under python3 env and source setup file, but it does not work.
So to make this work you have to remove the existing builds of the catkin_ws and compilethem again and then source. We cant source directly because then the catkin_ws_python3 WONT be in the path nad then we will have issues with tf2 not being compiled for Python3… Long story short, you have to do this and it should launch:
This is the right answer. We need to remove the devel and build directory before catkin_make. After re-compile at Python3 env, it works. And we can replace “timestep_limit” with “max_episode_steps”, it can launch successfully.
Are you compiling indicating the specific location of the Python3 executable? catkin_make -DPYTHON_EXECUTABLE:FILEPATH=/home/user/python3_ws/py3env/bin/python
Thank you Ricardo, by specifying the version of python I solved my problem.
Actually using your command " catkin_make -DPYTHON_EXECUTABLE:FILEPATH=/home/user/python3_ws/py3env/bin/python" I got the following error “CMake Error at /usr/share/cmake-3.5/Modules/FindPackageHandleStandardArgs.cmake:148 (message):
Could NOT find PythonInterp: Found unsuitable version “1.4”, but required
is at least “2” (found /home/user/python3_ws/py3env/bin/python)”
Instead using this catkin command I was able to compile successfully
“catkin build -DCATKIN_ENABLE_TESTING=0 -DCMAKE_BUILD_TYPE=Release -DPYTHON_VERSION=3.5”