moving launch files for processing nodelets to a driver independent package #59
Comments
|
Very cool. I just ran openni_launch and it worked great. We probably want some way for users to find the new launchfiles. For instance, if they used openni_launch/kinect_frames.launch on groovy in one of their own launchfiles, then their launchfiles wouldn't work anymore. Maybe dummy launchfiles in openni_launch and freenect_launch which just launch a node that says "this launchfile has moved to rgbd_launch"? |
|
Hm, sounds like too much extra work to me. I would just intentionally break anyone's launch files and leave a text file there containing a comment about the new location. Roslaunch's error message (can't find file) gives a good idea about what's going on. Additionally, I'd like to propose renaming of launch files, which are not used directly, from .launch to *.xml []. In that way those files won't show up in roslaunch's auto-completion. Also, it gives the user an hint that those files are not intended to be used by them directly. [*] Actually, it would be better to put an underscore (or similar) as suffix to those "include" launch files, but that hasn't been implemented yet (ros/ros_comm#254). |
|
An underscore sounds like a good idea to let people know the launchfiles are private. If we just have a text file to let people know that the old launchfiles have moved, won't they have to dig around for it? They'll call roslaunch with their custom launchfile that uses some launchfile in openni_launch, for instance, and it will fail. Then, if it was me, I'd do |
|
What about we rename them to: Adding an explicit text file should do the trick, I think. Just to be clear, your idea is much nicer - I'm just too lazy to implement it. :-) |
|
All these suggestions sound great. I'll write a small node that displays a I have some other work to do today and tomorrow. I'll work on this sometime Do you think we still have time to release these changes into Hydro? On Thu, Aug 1, 2013 at 7:23 PM, Marcus Liebhardt
|
|
With the node that displays the fatal message, I'm ok with releasing this On Thu, Aug 1, 2013 at 5:27 PM, Piyush Khandelwal
|
|
@jonbinney @bit-pirate @vrabaud I've updated all 3 packages based on the current discussion. Try merging/updating from the original rosinstall file again and let me know. I will start an issue in rgbd_launch regarding launch file cleanup, but I would like to tackle migration before we try that out. |
|
Hey folks! I have released a new version of freenect_launch and rgbd_launch that solves #5, #6 and #7. If you can test the system release of freenect_launch (v0.3.0) and let me know if these problems have been solved, I will push the same changes to openni_launch. |
|
Here is a small update on the launch includes naming: ros/ros_comm#254 |
|
@piyushk Could you please name the remaining things you like us to test? |
|
@bit-pirate I have opened up #8 rgbd_launch is now available as a deb package. Can you verify that the pull request works for you, and that it solves #6 and #7? Thanks! |
|
@piyushk I have tested your PR and I can confirm that it fixes #6 and #7. |
|
I'll go ahead and merge ros-drivers/openni_launch#8 (i don't have an asus right now to test, but sounds like you guys have covered that). I'll do a release shortly. |
|
Just released openni_launch into hydro: ros/rosdistro#1857 |
Tuesday Jul 30, 2013 at 16:36 GMT
Originally opened as ros-drivers/openni_launch#5
@jonbinney @bit-pirate
I have moved launch files to a separate rgbd_launch package. You can use this rosinstall file to test the new organization.
If things look alright to you, I will first release rgbd_launch, and then submit a pull request for openni_launch and freenect_launch once rgbd_launch makes it to shadow-fixed.
Additionally, there are a number of examples in freenect_launch that you can test out. See the documentation for reference: http://ros.org/wiki/freenect_launch
The text was updated successfully, but these errors were encountered: