Error while launching demo.launch in custom moveit config

I have generated a moveit configuration from a custom URDF using the MoveIt Setup assistant and this tutorial(http://wiki.ros.org/Industrial/Tutorials/Create_a_MoveIt_Pkg_for_an_Industrial_Robot).
I have been able to generate all the files in the config and launch folders as well. But, the problem occurs when I try to launch the demo.launch file using roslaunch.

Since this is a custom URDF, there's no package name, hence I simply use this command to launch the file

Comments

Thats the problem, I havent generated a package. Its only a folder where the moveit setup assistant exported the config files. Although the folder does have a CMakeLists and a package.xml file. How do i convert this file structure to a Ros "package"? cant I directly run a launch file?

> roslaunch manip_moveit_config demo.launch
[demo.launch] is neither a launch file in package [manip_moveit_config] nor is [manip_moveit_config] a launch file name
The traceback for the exception was written to the log file

Hm. The MSA should have generated a complete ROS package for you. If that was not the case, then it'd be nice if you could report that at ros-planning/moveit/issues.

Also before running the launch file, I had to ensure roscore is running(I'd got stuck once, because it wasn't running)

If you use roslaunch to start a launch file, starting roscore should be done automatically. Again, if that is not the case for you, that would seem to be a problem, and it'd be appreciated if you could report that.

Comments

By custom urdf, I mean I have a urdf file which I imported to the MSA(It didnt need any package name). Now the MSA generates a set of files into a configured folder with the CMakelists and package files I used the folder name manip_moveit_config. Should I make a workspace with these files in /src?

Yes, give this a try for sure. When gvdhoorn says custom URDFs should be stored in a ROS package, he is correct. This is because demo.launch looks for URDF in a launch file from another ROS package. You will either have to replace this with correct location or make a package for it (very easy).

Yes, putting the generated folder into a package file structure (as mentioned here ) works. Also before running the launch file, I had to ensure roscore is running(I'd got stuck once, because it wasn't running)
Thanks!

Hm. The MSA should have generated a complete ROS package for you. If that was not the case, then it'd be nice if you could report that at ros-planning/moveit/issues.
MSA generates a package,I meant that I needed to move that folder to ./src/ in my workspace and run catkin_make to make it work