Skip to content

Instantly share code, notes, and snippets.

@trainman419
Last active December 24, 2015 10:39
Show Gist options
  • Save trainman419/6785645 to your computer and use it in GitHub Desktop.
Save trainman419/6785645 to your computer and use it in GitHub Desktop.
http://wiki.ros.org/3d_navigation
* Source: svn https://code.ros.org/svn/wg-ros-pkg/branches/trunk_diamondback/sandbox/3d_navigation_icra12/
* Source: svn https://code.ros.org/svn/wg-ros-pkg/branches/trunk_diamondback/sandbox/3d_navigation/
uri: https://code.ros.org/svn/wg-ros-pkg/branches/trunk_diamondback/sandbox/3d_navigation/
uri: https://code.ros.org/svn/wg-ros-pkg/stacks/motion_planning_common/branches/arm_navigation_metrics
http://wiki.ros.org/actionlib_tutorials/Reviews/2009-10-01_User_Test
'''Brian''' - (This is a condensed version of the associated trac ticket [[https://code.ros.org/trac/ros-pkg/ticket/2880|#2880]]
'''Gil''' - (This is a condensed version of the associated Trac ticket [[https://code.ros.org/trac/ros-pkg/ticket/2982|#2982]])
http://wiki.ros.org/actionlib_tutorials/Tutorials/Writing a Callback Based Simple Action Client
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/actionlib_tutorials/simple_action_clients/fibonacci_callback_client.cpp,cplusplus,WRITE,show_uri)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/actionlib_tutorials/simple_action_clients/fibonacci_class_client.cpp,cplusplus,WRITE,show_uri)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/actionlib_tutorials/simple_action_clients/fibonacci_class_client.cpp,cplusplus,BIND)>>
http://wiki.ros.org/angles/Troubleshooting
If you encounter a problem that isn't addressed on this page, please [[https://code.ros.org/trac/ros-pkg/newticket?component=geometry&keywords=angles&owner=tfoote|file a ticket]]
The current list of open issues is available on [[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=new&status=reopened&group=milestone&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&keywords=~angles|trac]]
http://wiki.ros.org/answers.ros.org
Note: there are some known bugs with the email subscriptions at the moment. Please see [[https://code.ros.org/trac/ros/query?status=assigned&status=new&status=reopened&group=component&component=answers.ros.org&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component| open tickets in Trac]] and file new ones if you have a different issue.
http://wiki.ros.org/APIReviewProcess
ros-users@code.ros.org,
http://wiki.ros.org/austinvilla
svn co https://code.ros.org/svn/eros/tags/diamondback eros
http://wiki.ros.org/BestPractices
See something in the list below that you can help with? Write it up, link it here, and let [[https://code.ros.org/mailman/listinfo/ros-users|ros-users]] know about it. If you can only address part of an item on the list, that's fine; sometimes the initial question can be ill-posed or vague.
http://wiki.ros.org/bond_core/ChangeList
* Downloading smclib from code.ros.org
* Downloading smclib from code.ros.org
http://wiki.ros.org/bosch_object_segmentation_gui
uri: 'https://code.ros.org/svn/ros-pkg/stacks/visualization/trunk/rviz'
uri: 'https://code.ros.org/svn/ros-pkg/stacks/common_msgs/trunk/visualization_msgs'
uri: 'https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials'
uri: 'https://code.ros.org/svn/ros-pkg/stacks/visualization/trunk/interactive_markers'
uri: 'https://code.ros.org/svn/ros-pkg/stacks/visualization_common/trunk/ogre_tools'
uri: 'https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_object_manipulation/trunk/'
http://wiki.ros.org/boxturtle/Installation/Ubuntu/Deb
sudo sh -c 'echo "deb http://code.ros.org/packages/ros/ubuntu hardy main" > /etc/apt/sources.list.d/ros-latest.list'
sudo sh -c 'echo "deb http://code.ros.org/packages/ros/ubuntu jaunty main" > /etc/apt/sources.list.d/ros-latest.list'
sudo sh -c 'echo "deb http://code.ros.org/packages/ros/ubuntu karmic main" > /etc/apt/sources.list.d/ros-latest.list'
sudo sh -c 'echo "deb http://code.ros.org/packages/ros/ubuntu lucid main" > /etc/apt/sources.list.d/ros-latest.list'
wget http://code.ros.org/packages/ros.key -O - | sudo apt-key add -
http://wiki.ros.org/bullet/Troubleshooting
If you encounter a problem that isn't addressed on this page, please [[https://code.ros.org/trac/ros-pkg/newticket?component=geometry&keywords=bullet&owner=tfoote|file a ticket]]
The current list of open issues is available on the [[http://code.google.com/p/bullet/issues/list|Bullet issue tracker]] and on [[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=new&status=reopened&group=milestone&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&keywords=~bullet|trac]]
http://wiki.ros.org/calibration
uri: 'https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_common/trunk'
http://wiki.ros.org/camera1394
By default, [[stereo_image_proc]] requires the message timestamps for both images to match exactly, which the `camera1394` driver cannot do. The Diamondback release of `stereo_image_proc` provided a solution for this problem (enhancement [[https://code.ros.org/trac/ros-pkg/ticket/4217|#4217]]).
http://wiki.ros.org/camera1394/Cturtle
Unfortunately, the C-turtle [[stereo_image_proc]] requires message timestamps for both images to match exactly, which the `camera1394` driver does not do. Later releases of `stereo_image_proc` provide a cleaner solution for this problem (enhancement [[https://code.ros.org/trac/ros-pkg/ticket/4217|#4217]]). For C-turtle, the timestamps would need to be matched by an additional node, not provided in that release.
http://wiki.ros.org/camera1394/Cturtle/BoxTurtlePrototype
Check out the Box Turtle version from [[https://code.ros.org/svn/ros-pkg/branches/trunk_boxturtle/stacks/camera_drivers_experimental]]. Always check out that entire stack as it has internal dependencies.
http://wiki.ros.org/camera1394/Diamondback
Unfortunately, [[stereo_image_proc]] requires the message timestamps for both images to match exactly, which the `camera1394` driver cannot do. The Diamondback release of `stereo_image_proc` will probably provide a clean solution for this problem (enhancement [[https://code.ros.org/trac/ros-pkg/ticket/4217|#4217]]). For C-turtle, the timestamps needed to be matched by an additional node, not provided in that release.
http://wiki.ros.org/camera_info_manager/Reviews/2010-05-20_API_Review
* ('''Jack''') The dependency on `yaml_cpp` should not be needed for `latest`, it was needed on Box Turtle to work around a camera_calibration_parser bug [[https://code.ros.org/trac/ros-pkg/ticket/3922|#3922]]. Remove the dependency and the code to catch YAML exceptions, then re-test with `latest`. '''Done''', committed to SVN.
* ('''Blaise''') Should this package be somewhere other than the `camera_drivers` stack? (enhancement [[https://code.ros.org/trac/ros-pkg/ticket/3921|#3921]])
http://wiki.ros.org/cart_pushing/ChangeList
* Move dev branch to kt branch, [[https://code.ros.org/svn/wg-ros-pkg/stacks/cart_pushing/branches/kt]]
http://wiki.ros.org/catkin/migrating_from_rosbuild
rosbuild packages which are released are indexed in the release repo on code.ros.org while catkin packages are indexed in the git rosdistro repo. When you convert a released package from rosbuild to catkin you need to remove the old indexing entries and add them to the new location.
http://wiki.ros.org/catkin/Reviews/2012-08-01_API_Review
Note this benchmark purpose was disturbed by bug https://code.ros.org/trac/ros/ticket/4036.
* A bug in rosmake caused make never to run with multiple jobs https://code.ros.org/trac/ros/ticket/4036
* Catkin does not automatically invoke the reconfiguration step, rosbuild does (https://code.ros.org/trac/ros/ticket/4035)
To create your 3rdparty packages, you would have to use cmake. Most 3rdparty packages with rosbuild traditionally used make, which wasn't a good solution because you couldn't pass in cmake flags to the build that you used for the rest of your packages. You can do this in cmake though, which is what you'd have to do for catkin 3rdparty packages. I used to do this for an embedded opencv rosbuild - see the [[https://code.ros.org/gf/project/eros/scmsvn/?action=browse&path=%2Ftrunk%2Fpackages%2Fother%2Feros_opencv%2Fcmake%2FOpenCvBuild.cmake&view=markup|CMakeLists.txt]] in eros_opencv. It would be simple to build some cmake macros to facilitate that, or as JB mentioned, utilise the cmake external project infrastructure.
http://wiki.ros.org/collider
''NOTE: This package is currently unreleased and contains experimental code. The documentation below describes the current version in the [[https://code.ros.org/svn/wg-ros-pkg/stacks/motion_planning_common/branches/arm_navigation_metrics/collider|arm_navigation_metrics branch]] of motion_planning_common'', ''which might be released in E-turtle.''
http://wiki.ros.org/common/ChangeList/1.0
* genaction.py no longer fails on mac os. [[https://code.ros.org/trac/ros-pkg/ticket/3863 | Trac #3863]]
* [[yaml_cpp]] Updated clean rule to clean intermediate code [[https://code.ros.org/trac/ros-pkg/ticket/3651|ticket:3651]]
* [[pluginlib]] More robust to invalid manifests [[https://code.ros.org/trac/ros-pkg/ticket/3757 | #3757]]
* Simple action client's `spinThread` no longer "busy waits" with 100% CPU. [[https://code.ros.org/trac/ros-pkg/ticket/3685 | #3685]]
http://wiki.ros.org/common/ChangeList/Pre-1.0
* Removed deprecated ros calls to `getSubscriberID()` [[https://code.ros.org/trac/ros-pkg/ticket/3354|#3354]]
* Removing deprecated version of `SimpleActionClient::sendGoal`. This only affects users who register a `doneCallback` when calling `sendGoal` [[https://code.ros.org/trac/ros-pkg/ticket/3027|#3027]]
* removed inconsequential patches and updated manifest for doc review [[https://code.ros.org/trac/ros-pkg/ticket/2789|#2789]]
* Fixed unit-test compile error with gcc 4.4. [[https://code.ros.org/trac/wg-ros-pkg/ticket/2811|#2811]]
* Bugfixes in !ActionClient's waitForServerToStart logic. ros-pkg ticket [[https://code.ros.org/trac/ros-pkg/ticket/2612|#2612]]
* GoalID's are now [node-name]-[count]-[timestamp] instead of just a timestamp. ros-pkg ticket [[https://code.ros.org/trac/ros-pkg/ticket/2771|#2771]]
* namespace no longer must have filter_chain inserted [[https://code.ros.org/trac/ros-pkg/ticket/2618 | #2618]]
http://wiki.ros.org/common_msgs/ChangeList/1.1
* Fixing action definition build dependency race condition. <<Ticket(ros-pkg 4255)>> [[https://code.ros.org/trac/ros-pkg/changeset/30789 | r30789]]
* Added Ubuntu platform tags to manifest [[https://code.ros.org/trac/ros-pkg/changeset/29648 | r29648]]
http://wiki.ros.org/common_msgs/Reviews/2012-06-12_API_Review
https://code.ros.org/svn/ros-pkg/stacks/common_msgs/trunk/shape_msgs
http://wiki.ros.org/common_msgs/Troubleshooting
If you are having trouble with this stack please report the problems into [[https://code.ros.org/trac/ros-pkg/newticket?component=common_msgs|trac]].
http://wiki.ros.org/cturtle
* Add a check for drift at the end of calibration [[https://code.ros.org/trac/wg-ros-pkg/ticket/4093|Ticket 4093]] to detect cases where the IMU was moved while calibrating.
http://wiki.ros.org/cturtle/Installation/Sources
sudo sh -c 'echo "deb http://code.ros.org/packages/ros/ubuntu jaunty main" > /etc/apt/sources.list.d/ros-latest.list'
sudo sh -c 'echo "deb http://code.ros.org/packages/ros/ubuntu karmic main" > /etc/apt/sources.list.d/ros-latest.list'
sudo sh -c 'echo "deb http://code.ros.org/packages/ros/ubuntu lucid main" > /etc/apt/sources.list.d/ros-latest.list'
sudo sh -c 'echo "deb http://code.ros.org/packages/ros/ubuntu maverick main" > /etc/apt/sources.list.d/ros-latest.list'
wget http://code.ros.org/packages/ros.key -O - | sudo apt-key add -
http://wiki.ros.org/cyphy_vis_slam
svn co https://code.ros.org/svn/ros-pkg/stacks/vslam/trunk/g2o ~/ros/g2o
http://wiki.ros.org/de/ROS/StartGuide
* Womöglich wurde das Problem schon auf der [[http://code.ros.org/lurker/list/ros-users.html| Mailingliste]] diskutiert
http://wiki.ros.org/de/Support
Abonniere die [[https://code.ros.org/mailman/listinfo/ros-users | ROS Users Mailing Liste]] um auf dem neuesten Stand über ROS zu sein und durchsuche das [[http://code.ros.org/lurker/list/ros-users.html| ROS Users Archiv]].
2. Suche im [[http://code.ros.org/lurker/list/ros-users.html| Mailarchiv]] und auf [[http://answers.ros.org|ROS Answers]].
http://wiki.ros.org/DevelopersGuide
We support using Git, Mercurial, Subversion and Bazaar for source control. As the ROS community is distributed, you are welcome to host your code anywhere that is publicly accessible (GitHub, Bitbucket, Google Code). The main ROS code base is hosted in [[RecommendedRepositoryUsage/CommonGitHubOrganizations|several organization units]] on [[https://github.com|github.com]] , [[https://code.ros.org|code.ros.org]] and [[http://kforge.ros.org|kforge.ros.org]]. For the recommended repository usage please see [[RecommendedRepositoryUsage]]
For packages hosted on !GitHub this is commonly the issue tracker of the repository. Furthermore there is a legacy [[http://trac.edgewall.org/|Trac]] for issue tracking. There is one Trac for each code.ros.org repository: [[http://code.ros.org/trac/ros|ros]], [[https://code.ros.org/trac/ros-pkg|ros-pkg]] and [[https://code.ros.org/trac/wg-ros-pkg|wg-ros-pkg]].
Large data files should be placed in the 'data' repository, which is is a project on code.ros.org:
http://code.ros.org/gf/project/data
rosbuild_download_test_data(http://code.ros.org/svn/data/robot_pose_ekf/zero_covariance.bag test/zero_covariance.bag 0a51b4f5001f446e8466bf7cc946fb86)
http://wiki.ros.org/diamondback/Installation/Debian
Currently, they is a known issue with locales on Diamondback : https://code.ros.org/trac/ros/ticket/3305
http://wiki.ros.org/diamondback/Planning/Agenda
* https://code.ros.org/trac/ros/wiki/Handoff%20List
* https://code.ros.org/trac/ros-pkg/wiki/Handoff%20List
* https://code.ros.org/trac/wg-ros-pkg/wiki/Handoff%20List
http://wiki.ros.org/DocReviewProcess
ros-users@code.ros.org,
http://wiki.ros.org/DocumentationPolicy/Reviews/2009-10-30_API_Review
* /!\ Develop formal spec of ROS API: https://code.ros.org/trac/ros/ticket/1935
* /!\ Write tool to convert Wiki Node docs to new formal spec, putting the result in the packages in SVN: https://code.ros.org/trac/ros/ticket/1936
* /!\ Write macro to include source files from SVN into Wiki pages (mostly for Tutorial content): https://code.ros.org/trac/ros/ticket/1937
* /!\ Find a way to insert a search box into Doxygen- and epydoc-generated pages: https://code.ros.org/trac/ros/ticket/1938
* /!\ Add support for using symbolic tags to refer to parts of code examples in the wiki, instead of raw line numbers: https://code.ros.org/trac/ros/ticket/1939
http://wiki.ros.org/eigen
Unfortunately, Eigen on Ubuntu does not have a `FindEigen.cmake` file and we do not have that file in a ROS package yet. You need to include it by default in your package (in a ./cmake folder for example). You can get if from here: https://code.ros.org/svn/ros-pkg/stacks/laser_pipeline/trunk/laser_geometry/cmake/FindEigen.cmake
http://wiki.ros.org/eigen_tests
Package URL: [[https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/stacks/point_cloud_perception_experimental/eigen_tests/|https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/stacks/point_cloud_perception_experimental/eigen_tests/]]
http://wiki.ros.org/electric/Installation/Arch
https://code.ros.org/trac/ros/ticket/3700
http://wiki.ros.org/electric/Installation/Debian
Currently, there is a known issue with locales on Electric : https://code.ros.org/trac/ros/ticket/3305
http://wiki.ros.org/electric/Installation/Fedora
svn merge -c 15179 https://code.ros.org/svn/ros/stacks/ros/trunk/tools/rosdep/src/rosdep/installers.py installers.py
svn merge -c 15179 https://code.ros.org/svn/ros/stacks/ros/trunk/tools/rosdep/src/rosdep/redhat.py redhat.py
http://wiki.ros.org/electric/Installation/OSX/Homebrew
In case rosconsole fails to build because of a "g++-4.2 not found" error, use the patch found here: https://code.ros.org/trac/ros/changeset/15411
Installing https://code.ros.org/svn/ros/stacks/ros/tags/ros-1.6.5 to /Users/someuser/ros/ros
Error validating server certificate for 'https://code.ros.org:443':
Visit https://code.ros.org/ in your web browser, pull up the certificate information, and verify the fingerprint in your browser matches the one shown by `rosinstall` (or `svn co`). If it does, simply accept it permanently, by pressing `'p'` and `'enter'`, to solve the problem.
[ros] Installing https://code.ros.org/svn/ros/stacks/ros/tags/ros-1.6.8 (None) to /Users/someuser/ros/ros
svn co https://code.ros.org/svn/ros/stacks/ros/tags/ros-1.6.8 ~/ros/ros
Apply this patch: https://code.ros.org/trac/ros/attachment/ticket/3626/ros_comm-1.6.5-rosconsole_g%2B%2B-4.2.patch
From this ticket: https://code.ros.org/trac/ros/ticket/3626
http://wiki.ros.org/eros/alignment
* Open ticket re two locations where the problem occurs [[https://code.ros.org/trac/ros/ticket/2883|here]].
http://wiki.ros.org/eros/Installation
The simplest way to test drive eros in an existing ros tree is to check it out directly from [[https://code.ros.org/gf/project/eros/scmsvn/?action=AccessInfo|svn]].
svn co https://code.ros.org/svn/eros/tags/diamondback ./eros
* [[https://code.ros.org/gf/project/eros/scmsvn/?action=browse&path=%2F*checkout*%2Ftrunk%2Feros_cturtle.rosinstall|eros_cturtle.rosinstall]]
* [[https://code.ros.org/gf/project/eros/scmsvn/?action=browse&path=%2F*checkout*%2Ftrunk%2Feros_diamondback.rosinstall|eros_diamondback.rosinstall]]
* [[https://code.ros.org/gf/project/eros/scmsvn/?action=browse&path=%2F*checkout*%2Ftrunk%2Feros_trunk.rosinstall|eros_trunk.rosinstall]]
http://wiki.ros.org/eros/Support
* [[https://code.ros.org/mailman/listinfo/ros-users|ros-users]] ([[https://code.ros.org/discuss/ros-users|archives]])
* [[https://code.ros.org/mailman/listinfo/eros-developers|eros-dev]]
* [[https://code.ros.org/mailman/listinfo/eros-users|eros-users]]
http://wiki.ros.org/eros/Team
* [[https://code.ros.org/gf/project/eros/scmsvn/?action=AccessInfo|Yujin Robot]]
If you would like to contribute to eros, either as a user ([[eros|wiki]] or [[https://code.ros.org/gf/project/eros/mailman/|mailing list]] contributions) or developer, feel free to contact DanielStonier at the email address above or via the mailing lists.
http://wiki.ros.org/eros/Troubleshooting
* [[https://code.ros.org/mailman/listinfo/ros-users|ros-users mailing list]] ([[http://code.ros.org/lurker/list/ros-users.html|archive]]) - user contact point for problems.
* [[https://code.ros.org/mailman/listinfo/eros-developers|eros-dev mailing list]] - contact point for live developer discussions.
* [[https://code.ros.org/gf/project/eros/forum/|eros forums]] - working area, jots and most things unofficial.
* [[https://code.ros.org/gf/project/eros/tracker/|issue tracker]] - search/file bugs/todos and feature requests.
http://wiki.ros.org/eros_python_tools/Patches
These patches may from time to time break if bugfixes to the current version change a critical piece of code. When this happens, please submit a bug to eros' [[https://code.ros.org/gf/project/eros/tracker/|issue tracker]].
http://wiki.ros.org/eros_python_tools/UserDefinedModules
Probably the best place to do so is via the eros [[https://code.ros.org/gf/project/eros/tracker/|issue tracker]].
http://wiki.ros.org/ethercat_hardware/Tutorials/GripperAccelerometerController
https://code.ros.org/trac/ros-pkg/ticket/2822
http://wiki.ros.org/ethercat_hardware/Tutorials/UsingForceTorqueSensorWithWG035
- svn: {local-name: pr2_ethercat_drivers, uri: 'https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_ethercat_drivers/branches/ft_electric'}
svn co https://code.ros.org/svn/wg-ros-pkg/pr2_mods/pr2_force_torque_calibration
http://wiki.ros.org/Events/CoTeSys-ROS-School/Day4
1. Make sure that you have roslisp_common trunk checked out. Re-rosinstalling https://svn.code.sf.net/p/tum-ros-pkg/code/rosinstall/fall_school2010.rosinstall should suffice there. Alternatively, check out https://code.ros.org/svn/ros-pkg/stacks/roslisp_common/trunk into your sandbox
http://wiki.ros.org/Events/CoTeSys-ROS-School/SBPL
* [[https://code.ros.org/svn/wg-ros-pkg/stacks/motion_planners/trunk/sbpl/ | SBPL Repo]]
http://wiki.ros.org/Events/CoTeSys-ROS-School/SBPL_Lab
* navigation_experimental: https://code.ros.org/svn/ros-pkg/stacks/navigation_experimental/trunk/
* cart_pushing: https://code.ros.org/svn/wg-ros-pkg/stacks/cart_pushing/trunk
* pr2_arm_motion_planners: https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/stacks/pr2_arm_motion_planners/
* sbpl: https://code.ros.org/svn/wg-ros-pkg/stacks/motion_planners/trunk/sbpl/
* sbpl_lattice_planner: https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/sandbox/sbpl_lattice_planner
https://code.ros.org/svn/ros-pkg/stacks/navigation_experimental/trunk/sbpl_recovery/
http://wiki.ros.org/Events/ICRA2010Tutorial
* If we have time, we may also try out a new face detection node written in Python. Get it [[https://code.ros.org/svn/ros-pkg/stacks/vision_opencv/trunk/opencv_tests/nodes/rosfacedetect.py | here]] ('''Update: This, and a launch file are now included in icra_ros_tutorial. Just ''svn up'' there.''')
http://wiki.ros.org/executive_smach/Roadmap
Some example code can be found in asmach and asmach_tutorials [[https://code.ros.org/svn/ros-pkg/stacks/linux_networking/trunk|here]]. Only a handful of files have been asynchronized so far:
what's going on. See [[https://code.ros.org/svn/ros-pkg/stacks/linux_networking/trunk/multi_interface_roam/src/multi_interface_roam/dhcp.py|this file]] for more details. This code is completely asynchronous (never blocks), but reads pretty similarly to synchronous code.
http://wiki.ros.org/executive_teer/Tutorials/On Termination
This concludes the tutorial series on teer. If you have additional questions feel free to ask them on [[http://answers.ros.org|answers.ros.org]] or if you want to contribute to teer, do not hesitate to contact us or to discuss on the [[https://code.ros.org/mailman/listinfo/ros-users|ROS mailing list]].
http://wiki.ros.org/executive_trex
https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/stacks/executive_trex/
http://wiki.ros.org/filters/Troubleshooting
If you encounter a problem that isn't addressed on this page, please [[https://code.ros.org/trac/ros-pkg/newticket?component=common&keywords=filtersf|file a ticket]]
The current list of open issues is available on [[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=new&status=reopened&group=milestone&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&component=common&keywords=~filters|trac]]
http://wiki.ros.org/fuerte/Installation/Arch
- tar: {local-name: protobuf, uri: 'https://code.ros.org/svn/release/download/stacks/protobuf/protobuf-0.1.0/protobuf-0.1.0.tar.bz2',
''Note: This presently works but you will need to create a patch. See https://code.ros.org/trac/ros-pkg/ticket/5417 for clues'' The following should work:
wget https://code.ros.org/trac/ros-pkg/raw-attachment/ticket/5417/ros.patch
http://wiki.ros.org/fuerte/Installation/Debian
Currently, there is a known issue with Fuerte's svn scripts if you do not have US-english locales : https://code.ros.org/trac/ros/ticket/3305
http://wiki.ros.org/fuerte/Installation/OSX/Homebrew
In case rosconsole fails to build because of a "g++-4.2 not found" error, use the patch found here: https://code.ros.org/trac/ros/changeset/15411
Installing https://code.ros.org/svn/ros/stacks/ros/tags/ros-1.6.5 to /Users/someuser/ros/ros
Error validating server certificate for 'https://code.ros.org:443':
Visit https://code.ros.org/ in your web browser, pull up the certificate information, and verify the fingerprint in your browser matches the one shown by `rosinstall` (or `svn co`). If it does, simply accept it permanently, by pressing `'p'` and `'enter'`, to solve the problem.
[ros] Installing https://code.ros.org/svn/ros/stacks/ros/tags/ros-1.6.8 (None) to /Users/someuser/ros/ros
svn co https://code.ros.org/svn/ros/stacks/ros/tags/ros-1.6.8 ~/ros/ros
Apply this patch: https://code.ros.org/trac/ros/attachment/ticket/3626/ros_comm-1.6.5-rosconsole_g%2B%2B-4.2.patch
From this ticket: https://code.ros.org/trac/ros/ticket/3626
http://wiki.ros.org/fuerte/Migration
}}} [[https://code.ros.org/trac/ros/ticket/3831|(ticketed)]]
* After switching from Electric to Fuerte: tools that are no longer in `$ROS_ROOT/bin` are found in older installations, including `rosdep`. Best to start with a fresh shell. ([[https://code.ros.org/trac/ros/ticket/3832|ticketed]])
http://wiki.ros.org/fuerte/Planning/Drivers
* [[https://code.ros.org/lurker/list/ros-sig-drivers.html|discussion archives]].
* [[https://code.ros.org/mailman/listinfo/ros-sig-drivers|signup]]
http://wiki.ros.org/fuerte/Planning/IPC
* [[https://code.ros.org/lurker/list/ros-sig-ipc.html|discussion archives]].
* [[https://code.ros.org/mailman/listinfo/ros-sig-ipc|signup]]
http://wiki.ros.org/fuerte/Planning/Manipulation
Mailing list: [[https://code.ros.org/mailman/listinfo/ros-sig-manip|https://code.ros.org/mailman/listinfo/ros-sig-manip]]
http://wiki.ros.org/fuerte/Planning/Manipulation/Meetings
* Establishment of Manip-SIG [[https://code.ros.org/mailman/listinfo/ros-sig-manip|mailing list]]
http://wiki.ros.org/fuerte/Planning/Motion Planning
* [[https://code.ros.org/mailman/listinfo/ros-sig-plan|Mailing List]]
http://wiki.ros.org/fuerte/Planning/Multimaster
* [[https://code.ros.org/lurker/list/ros-sig-mm.html|discussion archives]].
* [[https://code.ros.org/mailman/listinfo/ros-sig-mm|signup]]
http://wiki.ros.org/fuerte/Planning/OSX
* https://code.ros.org/trac/ros-pkg/ticket/5240
* https://code.ros.org/trac/ros-pkg/ticket/5241
* https://code.ros.org/trac/ros-pkg/ticket/5242
* https://code.ros.org/trac/ros-pkg/ticket/5243
http://wiki.ros.org/fuerte/Planning/Perception Pipelines
* [[https://code.ros.org/lurker/list/ros-sig-perpip.html|Archives]]
* [[https://code.ros.org/mailman/listinfo/ros-sig-perpip|Signup]]
http://wiki.ros.org/fuerte/Planning/ROS Core/2011-10-19
* underway, starting at [[https://code.ros.org/trac/ros/changeset/15249|r15249]]
http://wiki.ros.org/fuerte/Planning/ROS GUI
Mailinglist: [[mailto:ros-sig-gui@code.ros.org|ros-sig-gui@code.ros.org]] [[https://code.ros.org/lurker/list/ros-sig-gui.html|Archive]]
Bugtracker: [[https://code.ros.org/trac/ros-pkg/query?component=visualization_rosgui|https://code.ros.org/trac/ros-pkg/]] selecting ''visualization_rosgui'' as component
http://wiki.ros.org/fuerte/Planning/rviz/Discussion
In the ticket system, there are [[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=new&status=reopened&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&col=changetime&owner=hersh|a long list of other things which could be done]].
http://wiki.ros.org/fuerte/Planning/Simulation and Control
* [[https://code.ros.org/lurker/list/ros-sig-sim.html|discussion archives]].
* [[https://code.ros.org/mailman/listinfo/ros-sig-sim|signup]]
http://wiki.ros.org/fuerte/Planning/TurtleBot
* [[https://code.ros.org/lurker/list/ros-sig-tbot.html|discussion archives]].
* [[https://code.ros.org/mailman/listinfo/ros-sig-tbot|signup]]
http://wiki.ros.org/geometry_msgs/Reviews/2009-09-30_Doc_Review
* (./) (ticketed into geometry stack https://code.ros.org/trac/ros-pkg/ticket/3008) On several messages, a pointer to good reference on fixed-axis representation would be nice.
http://wiki.ros.org/Get Involved
The ros-users mailing list: ros-users@code.ros.org is the primary mailing list of the community. It is not for specific technical questions but rather bigger picture topics and announcements. [[https://code.ros.org/mailman/listinfo/ros-users| Subscribe here]] [[https://code.ros.org/lurker/list/ros-users.html|View the archives]]
* [[https://code.ros.org/gf/project|code.ros.org]]
http://wiki.ros.org/graph_mapping/Reviews/2010-12-08_API_Review
svn co https://code.ros.org/svn/ros-pkg/stacks/graph_mapping/trunk graph_mapping
http://wiki.ros.org/graspit
svn co https://code.ros.org/svn/wg-ros-pkg/stacks/graspit_simulator/tags/fuerte graspit_simulator
http://wiki.ros.org/Graveyard
svn mv https://code.ros.org/svn/wg-ros-pkg/trunk/foo https://code.ros.org/svn/wg-ros-pkg/graveyard
http://wiki.ros.org/groovy/Installation/Fedora
To fix this issue, see the open ticket and apply the patch found there: https://code.ros.org/trac/ros-pkg/ticket/5507
There is an issue open that contains a patch to fix this: https://code.ros.org/trac/ros-pkg/ticket/5602
http://wiki.ros.org/groovy/Installation/Raspbian/Source
There are build errors in desktop-full (gazebo simulator) at the moment, so the desktop variant is suggested at this time. See: https://code.ros.org/trac/ros-pkg/ticket/5595
http://wiki.ros.org/groovy/Planning/Drivers
* [[https://code.ros.org/lurker/list/ros-sig-drivers.html|discussion archives]].
http://wiki.ros.org/groovy/Planning/Perception Pipelines
* [[https://code.ros.org/lurker/list/ros-sig-perpip.html|Archives]]
http://wiki.ros.org/groovy/Planning/Turtlebot
* [[https://code.ros.org/lurker/list/ros-sig-tbot.html|discussion archives]].
http://wiki.ros.org/gumros/kinect
* [[https://code.ros.org/trac/ros-pkg/ticket/5134|Remove X dependencies from dynamic reconfigure]]
http://wiki.ros.org/gumros/ubuntu
svn co https://code.ros.org/svn/ros/stacks/ros/tags/cturtle /opt/ros/cturtle/ros
http://wiki.ros.org/hierarchical_interactive_planning
- svn: {local-name: electric_sandbox, uri: 'https://code.ros.org/svn/wg-ros-pkg/branches/trunk_electric/electric_sandbox'}
http://wiki.ros.org/household_objects_database/Tutorials/Install the household_objects database on your local database server
[[https://code.ros.org/svn/data/trunk/household_objects/]]
http://wiki.ros.org/husky_navigation
The version of [[gmapping]] in the binary repositories currently has a bug which prevents inverted LIDARs from producing accurate data, even when the transform from /base_link to the LIDAR frame is properly formulated. The scan data will appear properly in rviz, but the map will be incorrect. To correct this, apply the patch found [[https://code.ros.org/trac/ros-pkg/ticket/5250|here]]. Consult [[http://answers.ros.org/question/11952/gmapping-and-inverted-upside-down-laser/|this thread]] for more information.
http://wiki.ros.org/hydro/Planning/nodelets
* A mechanism for better introspection into the communication graph of a single nodelet manager. (closed as wontfix: https://code.ros.org/trac/ros/ticket/3360)
http://wiki.ros.org/image_pipeline/ChangeList/Pre-1.0
* Release to support higher-level stacks that are in stable release process. Repository location moved to https://code.ros.org/svn/ros-pkg/stacks/image_pipeline/
http://wiki.ros.org/image_proc/Reviews/01-04-2010_Doc_Review
* PS: I discovered that image_proc does not warn when the intrinsic camera parameters are wrong. An use case discovered today was ticketed at: https://code.ros.org/trac/ros-pkg/ticket/3502
http://wiki.ros.org/imu_drivers/ChangeList/1.1
* Add check for drift at the end of calibration [[https://code.ros.org/trac/wg-ros-pkg/ticket/4093|Ticket 4093]]
http://wiki.ros.org/imu_drivers/ChangeList/1.2
* Add a check for drift at the end of calibration [[https://code.ros.org/trac/wg-ros-pkg/ticket/4093|Ticket 4093]] to detect cases where the IMU was moved while calibrating.
http://wiki.ros.org/imu_drivers/ChangeList/1.5
* https://code.ros.org/trac/ros-pkg/ticket/5601
* https://code.ros.org/trac/ros-pkg/ticket/5557
* https://code.ros.org/gf/project/ros-pkg/scmsvn/?action=ScmCommitDetail&scm_commit_id=140525
http://wiki.ros.org/Industrial/Tutorials/Create_a_Fast_IK_Solution/Prerequisites
There is a [[https://code.ros.org/trac/ros-pkg/ticket/5586|bug]] in the forward kinematics routine of `arm_kinematics_constraint_aware` that can cause it to crash. This bug can be fixed by applying the patch as follows:
$ sudo wget https://code.ros.org/trac/ros-pkg/raw-attachment/ticket/5586/fk_solver.patch
http://wiki.ros.org/ja/FAQ
* [[http://sourceforge.net/mailarchive/forum.php?forum_name=ros-users|ros-usersのアーカイブ]]を[[http://sourceforge.net/search/?group_id=86028&type_of_search=mlists|Search]]してください.もしそこにあなたの答えがなければ,問題を[[https://code.ros.org/mailman/listinfo/ros-users|ros-users]]にポストしてください.あなたが希望するなら,このメーリングリストは購読することもできます.
毎夜更新される[[http://ros.org/doc/api/|自動的に生成されたROSパッケージのドキュメント]]を参照することもできます.このリストには ros.sf.net とcode.ros.org からのパッケージのみ含まれています.他のリポジトリは現在,ここでリストされていません.
もしあなたが既存のパッケージを改良したら,一番良い方法はパッチをふさわしい開発者に送ることです.ros と code.ros.org のリポジトリの場合は,パッチを適用するためにTracチケットを開いてください.
*https://code.ros.org/trac/ros-pkg
*https://code.ros.org/trac/wg-ros-pkg
よく知られたROSパッケージ・リポジトリは [[Repositories]] のページにリストされています.あなたのリポジトリを作成したら,[[https://code.ros.org/mailman/listinfo/ros-users|ros-users]]にアナウンスを送ってください.そうすれば私たちはあなたのプロジェクトにリンクを張ります.
* [[https://code.ros.org/trac/ros-pkg|ros-pkg Trac]]
* [[https://code.ros.org/trac/ros-pkg|wg-ros-pkg Trac]]
http://wiki.ros.org/ja/kinect
kinectに関する議論については、 ros-kinect@code.ros.org に参加してください。(申し込みについては[[https://code.ros.org/mailman/listinfo/ros-kinect|here]]をクリックしてください).メーリングリストは、 http://kinect-with-ros.976505.n3.nabble.com のNabbleにアーカイブされます。
For discussions regarding 3D processing algorithms and PCL, pcl-users@code.ros.org にご参加ください (詳しくは http://pcl.ros.org をご覧ください). その他のKinectのセンサやPCLに関係しないROSに関する質問をする場合は ros-users@code.ros.org にご参加してください。(詳しくは http://www.ros.org/wiki/Support をご覧ください).
http://wiki.ros.org/ja/openni_kinect
ROSバインディングに関する議論については、 ros-kinect@code.ros.org (参加情報については [[https://code.ros.org/mailman/listinfo/ros-kinect|here]] をクリックしてください). メーリングリストは、公的にNabble: http://kinect-with-ros.976505.n3.nabble.com でアーカイブされています。
3D処理アルゴリズムやPCLに関する議論については、 pcl-users@code.ros.org にご参加ください(さらに詳しくは http://pointclouds.org をクリックしてください).
その他のOpenNIのインターフェースやPCLには奸計のないROSに関する一般的な質問は、 ros-users@code.ros.org にご参加ください。(より詳しくは http://www.ros.org/wiki/Support をご覧ください).
http://wiki.ros.org/ja/Papers
多くのROSユーザーは、https://code.ros.org/svn/wg-ros-pkg/externals/distro/cturtle/all/ のような便利なURLを利用しています。これらのURLは、Subversionの [[http://svnbook.red-bean.com/en/1.0/ch07s03.html|externals(外部参照)]] メカニズムを用いて、複数のリポジトリにリダイレクトしてくれます。便利ではありますが、外部参照メカニズムは、”親”の変更による制約を受けていません。違う言葉でいえば、https://code.ros.org/svn/wg-ros-pkg/externals/distro/cturtle/all/ バージョン番号だけでは、十分ではありません。なぜなら、外部参照されたリポジトリが変わる可能性があるからです。
./unwrap_externals.py https://code.ros.org/svn/wg-ros-pkg/externals/distro/cturtle/all/ > my.rosconfig
http://wiki.ros.org/ja/ROS/Installation/Ubuntu/Deb
sudo sh -c 'echo "deb http://code.ros.org/packages/ros/ubuntu hardy main" > /etc/apt/sources.list.d/ros-latest.list'
sudo sh -c 'echo "deb http://code.ros.org/packages/ros/ubuntu jaunty main" > /etc/apt/sources.list.d/ros-latest.list'
sudo sh -c 'echo "deb http://code.ros.org/packages/ros/ubuntu karmic main" > /etc/apt/sources.list.d/ros-latest.list'
wget http://code.ros.org/packages/ros.key -O - | sudo apt-key add -
http://wiki.ros.org/ja/ROS/StartGuide
最後に,あなたが運に見放されていなければ[[https://code.ros.org/mailman/listinfo/ros-users|ros-usersメーリングリスト(English)]]にメールを送ってください.その際はできるだけ問題の詳細を明確にしてください.
http://wiki.ros.org/ja/ROS/Tutorials/BuildingPackages
$ svn checkout https://code.ros.org/svn/ros-pkg/stacks/joystick_drivers_tutorials/trunk
http://wiki.ros.org/ja/roscpp
## リポジトリ: https://code.ros.org/svn/ros
http://wiki.ros.org/ja/roscpp_tutorials
## リポジトリ: https://code.ros.org/svn/ros
http://wiki.ros.org/ja/rviz
rviz saves its current display configuration to `~/.rviz/` on exit. Even if started with a another display config file via command line parameters, so be sure to regularly [[rviz/UserGuide#Configs|save your favorite configuration]]. ([[https://code.ros.org/trac/ros-pkg/ticket/5366|open ticket]])
http://wiki.ros.org/ja/rviz/Tutorials/Interactive Markers(3a20)Basic Controls
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/basic_controls.cpp,cplusplus,Box,global_lines,show_uri,no_tag_newlines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/basic_controls.cpp,cplusplus,6DOF,global_lines,show_uri,no_tag_newlines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/basic_controls.cpp,cplusplus,RandomDof,global_lines,show_uri,no_tag_newlines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/basic_controls.cpp,cplusplus,ViewFacing,global_lines,show_uri,no_tag_newlines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/basic_controls.cpp,cplusplus,Quadrocopter,global_lines,show_uri,no_tag_newlines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/basic_controls.cpp,cplusplus,ChessPiece,global_lines,show_uri,no_tag_newlines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/basic_controls.cpp,cplusplus,alignMarker,global_lines,show_uri,no_tag_newlines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/basic_controls.cpp,cplusplus,PanTilt,global_lines,show_uri,no_tag_newlines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/basic_controls.cpp,cplusplus,Menu,global_lines,show_uri,no_tag_newlines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/basic_controls.cpp,cplusplus,Button,global_lines,show_uri,no_tag_newlines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/basic_controls.cpp,cplusplus,Moving,global_lines,show_uri,no_tag_newlines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/basic_controls.cpp,cplusplus,vars,global_lines,show_uri,no_tag_newlines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/basic_controls.cpp,cplusplus,main,global_lines,show_uri,no_tag_newlines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/basic_controls.cpp,cplusplus,frameCallback,global_lines,show_uri,no_tag_newlines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/basic_controls.cpp,cplusplus,processFeedback,global_lines,show_uri,no_tag_newlines)>>
http://wiki.ros.org/ja/rviz/Tutorials/Interactive Markers(3a20)Getting Started
Code (C++): https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/simple_marker.cpp
Code (Python) https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/python/simple_marker.py
Code (C++): https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/basic_controls.cpp
Code (Python): https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/python/basic_controls.py
Code (C++): https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/menu.cpp
Code (Python): https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/python/menu.py
Code (C++): https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/pong.cpp
Code (C++): https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/cube.cpp
Code (Python): https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/python/cube.py
http://wiki.ros.org/ja/rviz/Tutorials/Interactive Markers(3a20)Writing a Simple Interactive Marker Server
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/simple_marker.cpp,cplusplus,fullSource,global_lines,show_uri,no_tag_newlines)>>
http://wiki.ros.org/ja/rviz/Tutorials/Markers(3a20)Basic Shapes
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,FULLTEXT,global_lines,show_uri,no_tag_newlines)>>
さて、少しずつコードを読み解いていきましょう。: <<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,INCLUDES,global_lines,no_tag_newlines)>>今までにROSのインクルードを見たことはあるでしょう。他に<<MsgLink(visualization_msgs/Marker)>>からメッセージの定義もインクルードしておきます。
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,INIT,global_lines,no_tag_newlines)>>これもおなじみの行だと思います。ROSを初期化して、`visualization_marker`のtopicに`ros::Publisher`を作成しています。
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,SHAPE_INIT,global_lines,no_tag_newlines)>>ここで、何の形の立体を描画するかを保存しておくint型の変数を用意します。使う予定の4つの立体は、同じようにして<<MsgLink(visualization_msgs/Marker)>>のメッセージを利用するので、異なる立体を表す形のタイプを変えるのみで描画する立体を変えることができます。
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,MARKER_INIT,global_lines,no_tag_newlines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,NS_ID,global_lines,no_tag_newlines)>>名前空間(`ns`)と`id`はこのマーカ特有の名前を作るために使用します。もし、マーカのメッセージが同じ`ns`と`id`で受け取ったなら、新しいマーカは古いものを置き換えます。
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,TYPE,global_lines,no_tag_newlines)>> この`type`の変数は、どのような種類のマーカを送るかを特定するためのものです。利用できる型は<<MsgLink(visualization_msgs/Marker)>>のメッセージの中に列挙されています。ここでは、ループのたびに変わる`shape`変数をセットします。
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,ACTION,global_lines,no_tag_newlines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,POSE,global_lines,no_tag_newlines)>> ここで、マーカのポーズを設定します。<<MsgLink(geometry_msgs/Pose)>>のメッセージは、位置を特定する<<MsgLink(geometry_msgs/Vector3)>>と角度を指定する<<MsgLink(geometry_msgs/Quaternion)>>で構成されます。原点に位置を設定し、基本姿勢に角度を設定しています。(注意`w`のみ1にする).
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,SCALE,global_lines,no_tag_newlines)>> マーカのスケールを設定します。基本立体を1のスケールに指定したときはサイドが1mあることを示します。
2<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,COLOR,global_lines,no_tag_newlines)>> マーカの色を<<MsgLink(std_msgs/ColorRGBA)>>として指定します。どのメンバも、0から1の間の数であるべきで、(`a`)の値が0であるはことは、完全に透明であることを氏名、1で不透明であることを示します。
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,LIFETIME,global_lines,no_tag_newlines)>> `lifetime`の変数は、自動的に削除されるまでマーカがあるべきかを特定します。`ros::Duration()`の値は、いつまでも消えないことを意味します。
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,PUBLISH,global_lines,no_tag_newlines)>>これで、マーカがパブリッシュされました。
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,CYCLE_SHAPES,global_lines,no_tag_newlines)>> このコードは一つのマーカのメッセージをパブリッシュするだけで、すべての4つの形を見ることができるものです。現在の形に基づいて、次の形を何にするかを決定しています。
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,SLEEP_END,global_lines,no_tag_newlines)>>sleepとloop backをします。
http://wiki.ros.org/ja/rviz/Tutorials/Markers(3a20)Points and Lines
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/points_and_lines.cpp,cplusplus,FULLTEXT,global_lines,show_uri)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/points_and_lines.cpp,cplusplus,MARKER_INIT,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/points_and_lines.cpp,cplusplus,ID,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/points_and_lines.cpp,cplusplus,TYPE,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/points_and_lines.cpp,cplusplus,SCALE,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/points_and_lines.cpp,cplusplus,COLOR,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/points_and_lines.cpp,cplusplus,HELIX,global_lines)>>
http://wiki.ros.org/ja/Source code
ROSコードのコアな部分は https://code.ros.org にあるROSプロジェクトにあります。
svn co https://code.ros.org/svn/ros/stacks/ros/tags/latest ros
ROS [[ja/Packages|パッケージ]]は https://code.ros.org にあるros-pkgとwg-ros-pkgプロジェクトにあります。
svn co https://code.ros.org/svn/wg-ros-pkg/externals/distro/cturtle/all/ ros-pkg
svn co https://code.ros.org/svn/ros-pkg/stacks/stack_name/tags/latest stack_name
svn co https://code.ros.org/svn/wg-ros-pkg/stacks/stack_name/tags/latest stack_name
svn co https://code.ros.org/svn/ros-pkg/trunk ros-pkg
svn co https://code.ros.org/svn/wg-ros-pkg/trunk wg-ros-pkg
http://wiki.ros.org/ja/Support
* [[https://code.ros.org/mailman/listinfo/ros-users|ros-users メーリング リスト]]
http://wiki.ros.org/ja/tf/jaTutorials/Writing a tf broadcaster(2028)C(2b2b29)
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus,2,2)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus,9,9)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus,10,12)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus,13,13)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus,14,14)>>
http://wiki.ros.org/ja/tf/Tutorials/Writing a tf broadcaster(2028)C(2b2b29)
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus,2,2)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus,9,9)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus,10,12)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus,13,13)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus,14,14)>>
http://wiki.ros.org/ja/WikiMacros
https://code.ros.org/lurker/thread/20110131.134604.f6e00a71.en.html
https://code.ros.org/lurker/message/20110131.134604.f6e00a71.en.html
http://wiki.ros.org/joint_trajectory_replay
svn co https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/stacks/dance_demo/
http://wiki.ros.org/joy/Tutorials/WritingTeleopNode
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/joystick_drivers_tutorials/trunk/turtle_teleop/launch/turtle_joy.launch,xml,FULL,show_uri)>>
http://wiki.ros.org/joystick_drivers/Tutorials/TeleopNode
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/joystick_drivers_tutorials/trunk/turtle_teleop/src/teleop_turtle_joy.cpp,cplusplus,FULL,show_uri)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/joystick_drivers_tutorials/trunk/turtle_teleop/src/teleop_turtle_joy.cpp,cplusplus,INCLUDE,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/joystick_drivers_tutorials/trunk/turtle_teleop/src/teleop_turtle_joy.cpp,cplusplus,CLASSDEF,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/joystick_drivers_tutorials/trunk/turtle_teleop/src/teleop_turtle_joy.cpp,cplusplus,PARAMS,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/joystick_drivers_tutorials/trunk/turtle_teleop/src/teleop_turtle_joy.cpp,cplusplus,PUB,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/joystick_drivers_tutorials/trunk/turtle_teleop/src/teleop_turtle_joy.cpp,cplusplus,SUB,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/joystick_drivers_tutorials/trunk/turtle_teleop/src/teleop_turtle_joy.cpp,cplusplus,CALLBACK,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/joystick_drivers_tutorials/trunk/turtle_teleop/src/teleop_turtle_joy.cpp,cplusplus,MAIN,global_lines)>>
http://wiki.ros.org/kdl_parser/Troubleshooting
If you encounter a problem that isn't addressed on this page, please [[https://code.ros.org/trac/ros-pkg/newticket?component=robot_model&keywords=kdl_parser&owner=meeussen|file a ticket]]
The current list of open issues is available on [[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=new&status=reopened&group=milestone&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&keywords=~kdl_parser|trac]]
http://wiki.ros.org/kinect
For Kinect related discussions, please join us at ros-kinect@code.ros.org (click [[https://code.ros.org/mailman/listinfo/ros-kinect|here]] for subscription information). The mailing list is publicly archived on Nabble:
For discussions regarding 3D processing algorithms and PCL, please join us at pcl-users@code.ros.org (see http://pcl.ros.org for more information). For other general purpose ROS related questions that do not concern the Kinect sensor or PCL, please join us at ros-users@code.ros.org (see http://www.ros.org/wiki/Support for more information).
http://wiki.ros.org/kinect_node
You can download the pre-recorded bag file of the video shown below from [[https://code.ros.org/svn/data/trunk/ccny/|here]]. This can be viewed in [[rviz]].
http://wiki.ros.org/ko/cturtle/Installation/Ubuntu
sudo sh -c 'echo "deb http://code.ros.org/packages/ros/ubuntu jaunty main" > /etc/apt/sources.list.d/ros-latest.list'
sudo sh -c 'echo "deb http://code.ros.org/packages/ros/ubuntu karmic main" > /etc/apt/sources.list.d/ros-latest.list'
sudo sh -c 'echo "deb http://code.ros.org/packages/ros/ubuntu lucid main" > /etc/apt/sources.list.d/ros-latest.list'
sudo sh -c 'echo "deb http://code.ros.org/packages/ros/ubuntu maverick main" > /etc/apt/sources.list.d/ros-latest.list'
wget http://code.ros.org/packages/ros.key -O - | sudo apt-key add -
http://wiki.ros.org/ko/ROS/StartGuide
해결책을 찾지 못하셨다면 다음으로 [[https://code.ros.org/discuss/ros-users/|메일링 리스트 저장소]]를 검색해 보세요.
http://wiki.ros.org/laser_assembler/Reviews/2009-09-18 API Review
* Ticketed [[https://code.ros.org/trac/ros-pkg/ticket/2870|ros-pkg #2870]]
http://wiki.ros.org/laser_assembler/Reviews/2009-9-29_Doc_Review
* [Vijay] ''Good idea, but definitely punting this for later''. [[https://code.ros.org/trac/wg-ros-pkg/ticket/2815|#2815]]
http://wiki.ros.org/laser_assembler/Troubleshooting
If you encounter a problem that isn't addressed on this page, please [[https://code.ros.org/trac/ros-pkg/newticket?component=laser_pipeline&keywords=laser_assembler&owner=vpradeep|file a ticket]]
The current list of open issues is available on [[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=new&status=reopened&group=milestone&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&keywords=~laser_assembler|trac]]
http://wiki.ros.org/laser_drivers/ChangeList/1.6
* Now supports connect_delay parameter for Pioneer models. [[https://code.ros.org/trac/ros-pkg/ticket/4138|#4138]] [[https://code.ros.org/trac/ros-pkg/ticket/4797|#4797]] [[https://code.ros.org/trac/ros-pkg/ticket/5358|#5358]]
* Added support for changing measurement units. [[https://code.ros.org/trac/ros-pkg/ticket/4931|#4931]]
http://wiki.ros.org/laser_filters/Troubleshooting
If you encounter a problem that isn't addressed on this page, please [[https://code.ros.org/trac/ros-pkg/newticket?component=laser_pipeline&keywords=laser_filters&owner=tfoote|file a ticket]]
The current list of open issues is available on [[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=new&status=reopened&group=milestone&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&keywords=~laser_filters|trac]]
http://wiki.ros.org/laser_geometry
At the moment there is not a Python implementation, however, one is planned for future release ([[https://code.ros.org/trac/ros-pkg/ticket/2867|ticket]]).
http://wiki.ros.org/laser_geometry/Troubleshooting
If you encounter a problem that isn't addressed on this page, please [[https://code.ros.org/trac/ros-pkg/newticket?component=laser_pipeline&keywords=laser_geometry&owner=tfoote|file a ticket]]
The current list of open issues is available on [[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=new&status=reopened&group=milestone&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&keywords=~laser_geometry|trac]]
http://wiki.ros.org/laser_pipeline/ChangeList/1.4
* Added Eigen export flags (https://code.ros.org/trac/ros-pkg/ticket/5566)
http://wiki.ros.org/laser_pipeline/ChangeList/Pre-1.0
* Adding support for inverted mode to laser projection [[https://code.ros.org/trac/ros-pkg/ticket/3041|3041]]
http://wiki.ros.org/laser_pipeline/Troubleshooting
If you encounter a problem that isn't addressed on this page, please [[https://code.ros.org/trac/ros-pkg/newticket?component=laser_pipeline&owner=leibs|file a ticket]]
The current list of open issues is available on [[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=new&status=reopened&component=laser_pipeline|trac]]
http://wiki.ros.org/libdc1394v2
svn co https://code.ros.org/svn/ros-pkg/branches/trunk_boxturtle/stacks/camera_drivers_experimental
http://wiki.ros.org/Mailing Lists
Please subscribe to the [[https://code.ros.org/mailman/listinfo/ros-users |ros-users mailing list]] to stay on top of the latest ROS news as well as post questions to the community for help.
[[https://code.ros.org/discuss/ros-users/|ros-users Archive]]
If all the above steps failed, the best thing to do is post to the [[https://code.ros.org/mailman/listinfo/ros-users|mailing list]].
http://wiki.ros.org/MaintenanceGuide
* If the current maintainer cannot be reached, send an email to ros-release@code.ros.org
* Contact the ros-release@code.ros.org mailing list, and ask for help.
http://wiki.ros.org/Metrics
We're collectively learning what to measure and how. Please provide feedback! Add your suggestions on how to improve these reports below, or post them to [[https://code.ros.org/mailman/listinfo/ros-users|ros-users@]].
http://wiki.ros.org/MikroKopter/Tutorials/shared_control
then the [[https://code.ros.org/trac/ros/ticket/2883|patch code]] for the ROS serialisation is required.
http://wiki.ros.org/Mirrors
There's a lot of room for improvement in the way that mirrors are managed; see [[https://code.ros.org/trac/ros/ticket/3281|this ticket]] for open feature requests.
http://wiki.ros.org/mit-ros-pkg/KinectDemos/Eigen3Install
Due to [[http://code.ros.org/lurker/message/20110207.205813.3fed060a.en.html|Eigen Unmangling]], a tag of the MIT Kinect demos has been made.
http://wiki.ros.org/mit-ros-pkg/KinectDemos/electric
1. Replace "https://code.ros.org/svn/wg-ros-pkg/stacks/motion_planning_common/tags/unstable/" in the rosinstall file with "https://code.ros.org/svn/wg-ros-pkg/stacks/motion_planning_common/trunk/".
http://wiki.ros.org/mk
svn checkouts are both slow and more prone to downtime. A hybrid approach using the tarball for distribution, and a fancy makefile can be done with a script like the [[bullet]] package https://code.ros.org/svn/ros-pkg/stacks/geometry/tags/geometry-1.0.0/bullet/Makefile.bullet This uses the svn_checkout script to build the tarball when developing, but most users simply use the tarball.
http://wiki.ros.org/motion_planning_common/ChangeList
* Incorporated this patch: [[https://code.ros.org/trac/ros-pkg/ticket/4741|4741]]
http://wiki.ros.org/move_base/Reviews/2009-09-23_API_Review
* Ultimately a pluggable recovery behavior would be valuable, I have opened a ticket against this with more detail: https://code.ros.org/trac/ros-pkg/ticket/2883
* Adding a boolean parameter to disable spinning in the recovery behavior would be a useful stopgap measure: https://code.ros.org/trac/ros-pkg/ticket/2882
http://wiki.ros.org/nav_msgs/Reviews/2009-09-30_Doc_Review
Brian: https://code.ros.org/trac/ros-pkg/ticket/2997
http://wiki.ros.org/netft_ethercat_hardware/Tutorials/UsingNetFTPluginWithPR2EtherCAT
- svn: {local-name: netft, uri: 'https://code.ros.org/svn/wg-ros-pkg/stacks/netft/trunk'}
- svn: {local-name: pr2_ethercat_drivers, uri: 'https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_ethercat_drivers/trunk'}
- svn: {local-name: pr2_mechanism, uri: 'https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_mechanism/trunk'}
- svn: {local-name: pr2_etherCAT, uri: 'https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_robot/trunk/pr2_etherCAT'}
- svn: {local-name: pr2_controllers, uri: 'https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_controllers/trunk'}
URL: https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_ethercat_drivers/trunk
http://wiki.ros.org/nodelet/Roadmap
* document/make it easy to change the number of threads used (on the fly?). Right now we have "num_worker_threads" as a parameter. (ref [[https://code.ros.org/trac/ros-pkg/ticket/4603]])
http://wiki.ros.org/object_recognition_experimental
uri: https://code.ros.org/svn/wg-ros-pkg/trunk/stacks/object_recognition_experimental
uri: https://code.ros.org/svn/ros-pkg/stacks/perception_pcl/tags/unstable
http://wiki.ros.org/objects_of_daily_use_finder
svn co https://code.ros.org/svn/ros-pkg/stacks/vslam/trunk vslam
http://wiki.ros.org/ompl_ros_interface/Tutorials/Before you begin planning(3a20)Setting up the Prerequisites
The full description for the PR2 robot can be found in [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_arm_navigation/trunk/pr2_arm_navigation_config/config/planning_groups.yaml|pr2_arm_navigation_config/config/planning_groups.yaml]].
The full multi-dof joint description for the PR2 robot can be found in [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_arm_navigation/trunk/pr2_arm_navigation_config/config/multi_dof_joints.yaml|pr2_arm_navigation_config/config/multi_dof_joints.yaml]]. It shows how a multi-dof joint is specified as a ''floating'' joint connecting the ''base_footprint'' link of the PR2 to the ''odom_combined'' frame.
The default collision operations for the PR2 robot can be found in [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_arm_navigation/trunk/pr2_arm_navigation_config/config/collision_checks_both_arms.yaml|pr2_arm_navigation_config/config/collision_checks_both_arms.yaml]].
http://wiki.ros.org/openni_kinect
For ROS bindings related discussions, please join us at ros-kinect@code.ros.org (click [[https://code.ros.org/mailman/listinfo/ros-kinect|here]] for subscription information). The mailing list is publicly archived on Nabble: http://kinect-with-ros.976505.n3.nabble.com
For discussions regarding 3D processing algorithms and PCL, please join us at pcl-users@code.ros.org (see http://pointclouds.org for more information).
For other general purpose ROS related questions that do not concern the OpenNI interface or PCL, please join us at ros-users@code.ros.org (see http://www.ros.org/wiki/Support for more information).
http://wiki.ros.org/openni_pcl
uri: https://code.ros.org/svn/ros-pkg/stacks/perception_pcl/tags/unstable
uri: https://code.ros.org/svn/ros-pkg/stacks/perception_pcl_addons/tags/unstable
http://wiki.ros.org/Papers
Many ROS users rely on convenience URLs such as https://code.ros.org/svn/wg-ros-pkg/externals/distro/cturtle/all/. These URLs use Subversion's [[http://svnbook.red-bean.com/en/1.0/ch07s03.html|externals]] mechanism to redirect to multiple repositories. While convenient, the externals mechanism is not constrained by the revision of the "parent." In other words, it's not sufficient to record the version of https://code.ros.org/svn/wg-ros-pkg/externals/distro/cturtle/all/, because the repositories pointed to by that external can change.
./unwrap_externals.py https://code.ros.org/svn/wg-ros-pkg/externals/distro/cturtle/all/ > my.rosconfig
http://wiki.ros.org/Papers/ICRA2011_Takayama_Marder-Eppstein_Harris_Beer
svn co https://code.ros.org/svn/ros-pkg/stacks/navigation_experimental/tags/navigation_experimental-0.1.2/
svn co https://code.ros.org/svn/ros-pkg/stacks/navigation/tags/navigation-1.2.2
http://wiki.ros.org/PatrickBouffard
[[https://code.ros.org/trac/ros/query?status=assigned&status=closed&status=new&status=reopened&reporter=bouffard&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&col=resolution&col=time&col=changetime|ros]]
[[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=closed&status=new&status=reopened&reporter=bouffard&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&col=resolution&col=time&col=changetime|ros-pkg]]
[[https://code.ros.org/trac/wg-ros-pkg/query?status=assigned&status=closed&status=new&status=reopened&reporter=bouffard&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&col=resolution&col=time&col=changetime|wg-ros-pkg]]
http://wiki.ros.org/pcl/Roadmap
Following a discussion thread on pcl-users@code.ros.org ([[http://point-cloud-library-pcl-mailing-list.967500.n3.nabble.com/pre-review-td1858850.html|see here]]), we propose the following development model for PCL.
http://wiki.ros.org/phidgets
svn co https://code.ros.org/svn/ros-pkg/stacks/sound_drivers/trunk/sound_play
http://wiki.ros.org/physics_ode/ChangeList/1.0
* Added missing md5sum file per ticket [[https://code.ros.org/trac/ros-pkg/ticket/3759|#3759]]
* Per ticket [[https://code.ros.org/trac/ros-pkg/ticket/3759|#3759]], check md5sum and pull tar ball from wg server
* fix ticket [[https://code.ros.org/trac/ros-pkg/ticket/3365|#3365]] in r26101.
http://wiki.ros.org/place_recognition
https://code.ros.org/svn/wg-ros-pkg/graveyard/
http://wiki.ros.org/platform_group
* plans for code.ros.org to be mostly shut down in the future
http://wiki.ros.org/pluginlib/Reviews/2009-09-23 Usage Review
* Stu's ticket should be addressed, but is not needed for the release. [[https://code.ros.org/trac/ros-pkg/ticket/2822| #2822]]
http://wiki.ros.org/pluginlib/Troubleshooting
If you encounter a problem that isn't addressed on this page, please [[https://code.ros.org/trac/ros-pkg/newticket?component=common&keywords=pluginlib|file a ticket]]
The current list of open issues is available on [[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=new&status=reopened&group=milestone&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&component=common&keywords=~pluginlib|trac]]
http://wiki.ros.org/point_cloud_perception/Reviews/5-13-2011_Doc_Review
* svn link broken on https://code.ros.org/svn/ros-pkg/stacks/perception_pcl/trunk/pcl, http://pcl.ros.org/authors broken too
http://wiki.ros.org/polled_camera/Reviews
Blaise and I agreed on the service/topic structure following discussions at [[https://code.ros.org/trac/ros-pkg/ticket/3180|ticked #3180]].
http://wiki.ros.org/pr2_2dnav_gazebo/Tutorials/Simulating the 2dnav Stack
svn co https://code.ros.org/svn/wg-ros-pkg/stacks/wg_robots_gazebo/trunk/pr2_2dnav_gazebo/
http://wiki.ros.org/pr2_apps/ChangeList/0.2
* Arm controllers stopped on startup, and come back up on exit. [[https://code.ros.org/trac/wg-ros-pkg/ticket/3295 | #3295]] [[https://code.ros.org/trac/wg-ros-pkg/ticket/3664 | #3664]]
http://wiki.ros.org/pr2_calibration/ChangeList/pre-1.0
* Wide stereo settling criteria is now a little more lenient for capturing large checkerboards [[https://code.ros.org/trac/wg-ros-pkg/changeset/44928 | r44928]]
* Updated checkerboard spacing for 4x5 checkerboards. The 4x5 checkerboards shipped with the PR2 (Part 68-03823) are not exactly 0.025m spacing. [[https://code.ros.org/trac/wg-ros-pkg/changeset/44766 | r44766]]
http://wiki.ros.org/pr2_calibration/Troubleshooting
If you encounter a problem that isn't addressed on this page, please [[https://code.ros.org/trac/wg-ros-pkg/newticket?component=pr2_calibration&owner=vpradeep|file a ticket]]
http://wiki.ros.org/pr2_calibration/Tutorials/Calibrating a new sensor to the PR2
Any new sensor pipeline should be added to [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/cturtle/pr2_calibration_launch/capture_data/all_pipelines.launch | pr2_calibration_launch/capture_data/all_pipelines.launch]].
The standard pipeline is defined in [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/cturtle/pr2_calibration_launch/capture_data/monocam_pipeline.launch | pr2_calibration_launch/capture_data/monocam_pipeline.launch]]
The pipelines for the PR2's stereocameras simply constructs 4 instances of `monocam_pipeline.launch`. See [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/cturtle/pr2_calibration_launch/capture_data/double_stereo_pipeline.launch | double_stereo_pipeline.launch]]
You now need to tell the executive about the new sensor. This is done by adding it to one of the sensor configuration files. If this is a camera, you should add a camera to [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/cturtle/pr2_calibration_launch/capture_data/hardware_config/cam_config.yaml | cam_config.yaml]]. The format is described in [[pr2_calibration_executive]]
You now need to update some subset of the samples to include the new camera. The samples are defined in [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/cturtle/pr2_calibration_launch/capture_data/samples_pr2_beta | pr2_calibration_launch/capture_data/samples_pr2_beta]]
The estimator uses a yaml representation of the robot that mirrors the URDF. (Yes, this file is extremely redundant to the URDF, and hopefully it will be removed if/when we do a major iteration on the calibration stack). For the PR2, this file is [[ https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/boxturtle/pr2_calibration_launch/estimate_params/config_pr2_beta/system.yaml | pr2_calibration_launch/estimate_params/config_pr2_beta/system.yaml]].
We currently run a test to make sure that the yaml robot definition matches the actual URDF. This test available at [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/cturtle/pr2_calibration_estimation/test/test_pr2_fk.launch | pr2_calibration_estimation/test/test_pr2_fk.launch]]. Since inconsistencies between the yaml and URDF could lead to strange calibration results, you should probably copy and modify this test to make sure your added frames also match your URDF.
You added the additional frames, but you now have to tell the estimator how the new sensors attach to the new frames. [[ https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/boxturtle/pr2_calibration_launch/estimate_params/config_pr2_beta/sensors.yaml | pr2_calibration_launch/estimate_params/config_pr2_beta/sensors.yaml ]].
The main config for the multistep optimization is defined in [[ https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/trunk/pr2_calibration_launch/estimate_params/head_then_arms_params.launch | pr2_calibration_launch/estimate_params/head_then_arms_params.launch]]. Here, for each step, a yaml file is loaded into `free_params`. Each `free_params` yaml file defines which parameters are free during that optimization step. You must add your fields for any robot primitives you've added, along with fields for the sensor itself.
These files are defined for the pr2 as [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/boxturtle/pr2_calibration_launch/estimate_params/config_pr2_beta | pr2_calibration_launch/estimate_params/config_pr2_beta/free_*.yaml]]
[[https://code.ros.org/trac/wg-ros-pkg/changeset?new=44942%40stacks%2Fpr2_calibration%2Ftrunk&old=44767%40stacks%2Fpr2_calibration%2Ftrunk | pr2_calibration diff]]
## * [[https://code.ros.org/trac/wg-ros-pkg/changeset/44891 | r44891]], [[https://code.ros.org/trac/wg-ros-pkg/changeset/44923 | r44923]]
## * [[https://code.ros.org/trac/wg-ros-pkg/changeset/44918 | r44918]]
## * [[https://code.ros.org/trac/wg-ros-pkg/changeset/44935 | r44935]], [[https://code.ros.org/trac/wg-ros-pkg/changeset/44919 | r44919]], [[https://code.ros.org/trac/wg-ros-pkg/changeset/44942 | r44942]]
## * [[https://code.ros.org/trac/wg-ros-pkg/changeset/44929 | r44929]]
http://wiki.ros.org/pr2_calibration/Tutorials/Using PR2 Auto Calibration
rosinstall ~/ros_auto_cal /opt/ros/cturtle ~/pr2_calibration https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/branches/auto_calibrate/pr2_auto_calibration.rosinstall
http://wiki.ros.org/pr2_calibration_estimation
The main goal of the pr2_calibration_estimation package is to provide a reconfigurable nonlinear optimizer for estimating calibration parameters for some defined robot. For the PR2, the estimator is launched using [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/trunk/pr2_calibration_launch/estimate_params/estimate_pr2_beta.launch | pr2_calibration_launch/estimate_params/config_pr2_beta/estimate_pr2_beta.launch]]. This launch file loads the estimation configuration onto the parameter server and then launches the estimator (multistep_cov_estimator.py).
The estimator looks for it's configuration in the `/calibration_config` namespace. The PR2's configuration is stored in [[ https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/trunk/pr2_calibration_launch/estimate_params/head_then_arms_params.launch | pr2_calibration_launch/estimate_params/head_then_arms_params.launch]]
The calibration estimator relies on a yaml file that stores the configuration of the robot's various kinematic and sensor primitives that we may want to estimate. For the PR2, this file is [[ https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/boxturtle/pr2_calibration_launch/estimate_params/config_pr2_beta/system.yaml | pr2_calibration_launch/estimate_params/config_pr2_beta/system.yaml]]. The currently support primitives are dh_chains, tilting_lasers, transforms, and rectified cameras. Although not necessarily a "robot primitive", checkerboard intrinsics are also defined in this file.
A DH Chain primitive is used to represent a kinematic linkage using [[http://en.wikipedia.org/wiki/Denavit-Hartenberg_Parameters | Denavit-Hartenberg parameters]]. Each DH Chain primitive must be included as a dictionary element under the `dh_chains` section of the config file. The parameters defined below are used in [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/boxturtle/pr2_calibration_estimation/src/pr2_calibration_estimation/dh_chain.py | pr2_calibration_estimation/dh_chain.py]]
The sensors used in the PR2 estimation are defined at [[ https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/boxturtle/pr2_calibration_launch/estimate_params/config_pr2_beta/sensors.yaml | pr2_calibration_launch/estimate_params/config_pr2_beta/sensors.yaml ]]. This is a yaml file broken down by sensor type. For each sensor type, there is a list of sensors.
For each estimation step, we need to specify which parameters we want to estimate. This is done using a yaml file that looks extremely to the primitives definition file, except that instead of having values for all the parameters, it is filled with `0`s and `1`s. All parameters with `1`s will be estimated. These are defined for the pr2 as [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/boxturtle/pr2_calibration_launch/estimate_params/config_pr2_beta | pr2_calibration_launch/estimate_params/config_pr2_beta/free_*.yaml]].
http://wiki.ros.org/pr2_calibration_executive
This page is definitely not a full explanation of how to use this package, but rather a tool to help get started in exploring this package. If you're interested in understanding how calibration data is gathered for the pr2, you can trace through [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/cturtle/pr2_calibration_launch/capture_data/capture_data.launch | capture_data.launch]]
Each file contains the configuration for each sensor, along with commands to send to controllers. We consider each file to be a sample. For the PR2, we have many samples for the left and right arm, whereas we have only one sample in the 'far' directory. This is because for far data, we don't have to keep commanding the arms, so we keep the system in this far sample's configuration until the user says they've collected enough data. You will definitely have to modify pr2_exec.py to suit your data collection needs. For the PR2, this directory, is [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/boxturtle/pr2_calibration_launch/capture_data/samples_pr2_beta/ | pr2_calibration_launch/capture_data/samples_pr2_beta]]
The cameras on the PR2 are defined in file [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/boxturtle/pr2_calibration_launch/capture_data/hardware_config/cam_config.yaml | cam_config.yaml]]
The chains on the PR2 are defined in [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/boxturtle/pr2_calibration_launch/capture_data/hardware_config/chain_config.yaml | chain_config.yaml]]
Each controller definition corresponds to a controller accepts <<MsgLink(trajectory_msgs/JointTrajectory)>> messages. For the PR2, we rely on the [[robot_mechanism_controllers/JointSplineTrajectoryController | JointSplineTrajectoryController]]: One for the head and one for each arm. The controller defintions are defined in [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/cturtle/pr2_calibration_launch/capture_data/hardware_config/controller_config.yaml | controller_config.yaml]].
The samples used to capture data on the PR2 are in [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_calibration/tags/cturtle/pr2_calibration_launch/capture_data/samples_pr2_beta | pr2_calibration_launch/capture_data/samples_pr2_beta]].
http://wiki.ros.org/pr2_common/ChangeList/1.0
* Removed visual/inertial/collision elements for gripper_tool_frame <<Ticket(ros-pkg,3408)>>, [[https://code.ros.org/trac/wg-ros-pkg/changeset/34760|34760]]
* corresponding to ticke[[https://code.ros.org/trac/wg-ros-pkg/ticket/3763|3763]] flipping gripper by 180 degrees for betas as they are mounted opposite of alphas.
http://wiki.ros.org/pr2_common/ChangeList/Pre-1.0
* r28582 makes separate xacro:macro for upper_arm_roll assembly in pr2_description. This allows it to be tested separately, and is used in production. [[https://code.ros.org/trac/wg-ros-pkg/ticket/3438|#3438]]
* `base_footprint` link added to pr2_base macro in pr2_description. [[https://code.ros.org/trac/wg-ros-pkg/ticket/3428|#3428]]
* [[https://code.ros.org/trac/wg-ros-pkg/ticket/3337|#3337]]. Changes checked on robot and sim.
* added rising and falling calibration positions per [[https://code.ros.org/trac/ros-pkg/ticket/3141|#3141]]
http://wiki.ros.org/pr2_controller_interface/Troubleshooting
If you encounter a problem that isn't addressed on this page, please [[https://code.ros.org/trac/ros-pkg/newticket?component=pr2_mechanism&keywords=pr2_controller_interface&owner=meeussen|file a ticket]]
The current list of open issues is available on [[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=new&status=reopened&group=milestone&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&keywords=~pr2_controller_interface|trac]]
http://wiki.ros.org/pr2_doors/ChangeList/0.2
* add workaround for [[https://code.ros.org/trac/wg-ros-pkg/ticket/3954|ticket #3954]]
http://wiki.ros.org/pr2_drinks
svn co https://code.ros.org/svn/wg-ros-pkg/trunk/rosinstall_files/cturtle
http://wiki.ros.org/pr2_etherCAT/Tutorials/Running
svn co https://code.ros.org/svn/pr2debs/trunk/packages/pr2/pr2-grant
http://wiki.ros.org/pr2_ethercat_drivers/Reviews/01-13-2010_Doc_Review
the current issues are documented in trac under this ticket [[https://code.ros.org/trac/wg-ros-pkg/ticket/3407|#3407]]
http://wiki.ros.org/pr2_gazebo_plugins/Reviews/2009-12-08 API Review
* gazebo_ros_stereo.cpp is deprecated, and will be removed [[https://code.ros.org/trac/wg-ros-pkg/ticket/3136|#3136]].
http://wiki.ros.org/pr2_gripper_action/Reviews/2010-01-13_Doc_Review
(./) Ticketed: https://code.ros.org/trac/wg-ros-pkg/ticket/3672
http://wiki.ros.org/pr2_gripper_sensor_action
##https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_object_manipulation/trunk/manipulation/.
http://wiki.ros.org/pr2_head_action/Reviews/2010-01-13_Doc_Review
(./) Ticketed: https://code.ros.org/trac/wg-ros-pkg/ticket/3673
(./) Ticketed: https://code.ros.org/trac/wg-ros-pkg/ticket/3672
http://wiki.ros.org/pr2_interactive_manipulation/electric
*Source: svn https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_object_manipulation/branches/0.5-branch/applications/pr2_interactive_manipulation
http://wiki.ros.org/pr2_interactive_manipulation/fuerte
*Source: svn https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_object_manipulation/branches/0.5-branch/applications/pr2_interactive_manipulation
http://wiki.ros.org/pr2_mechanism/ChangeList/pre-1.0
* per ticket [[https://code.ros.org/trac/wg-ros-pkg/ticket/2949]], gripper now reports gap size < 0. It however, restricts Jacobians to use encoder values >= 0 for velocity and effort calculations.
http://wiki.ros.org/pr2_mechanism/Roadmap
[[https://code.ros.org/svn/wg-ros-pkg/trunk/sandbox/rt_scheduler/include/rt_scheduler/api_v2.h]]
[[https://code.ros.org/svn/wg-ros-pkg/trunk/sandbox/rt_scheduler/src/api_v2_example.cpp]]
Check [[https://code.ros.org/trac/wg-ros-pkg/wiki/coq/mechanism|trac]] for outstanding issues and roadmap.
http://wiki.ros.org/pr2_mechanism/Troubleshooting
If you encounter a problem that isn't addressed on this page, please [[https://code.ros.org/trac/ros-pkg/newticket?component=pr2_mechanism&owner=meeussen|file a ticket]]
The current list of open issues is available on [[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=new&status=reopened&component=pr2_mechanism|trac]]
http://wiki.ros.org/pr2_mechanism/Tutorials/Writing a realtime Cartesian controller
https://code.ros.org/trac/ros-pkg/ticket/2822
http://wiki.ros.org/pr2_mechanism/Tutorials/Writing a realtime joint controller
https://code.ros.org/trac/ros-pkg/ticket/2822
http://wiki.ros.org/pr2_mechanism_controllers/Reviews/2010-01-14_Doc_Review
the current issues are documented in trac under this ticket [[https://code.ros.org/trac/wg-ros-pkg/ticket/3574|#3574]]
http://wiki.ros.org/pr2_power_drivers/ChangeList
* Fix incorrect logical operation that could cause batteries to falsely read charging ([[https://code.ros.org/trac/wg-ros-pkg/changeset/44561|r44561]]).
* Added ability to control the fan speed ([[https://code.ros.org/trac/wg-ros-pkg/changeset/30092|r30092]])
* Fixed: ignoring observations when the batteries were fully charged (<<Ticket(wg-ros-pkg 3729)>>, [[https://code.ros.org/trac/wg-ros-pkg/changeset/30072|r30072]])
* Fixed: not setting permissions when creating log file (<<Ticket(wg-ros-pkg 3713)>>, [[https://code.ros.org/trac/wg-ros-pkg/changeset/29971|r29971]])
http://wiki.ros.org/pr2_power_drivers/Roadmap
* Improve power level reporting (https://code.ros.org/trac/wg-ros-pkg/ticket/2991)
http://wiki.ros.org/pr2_remote_teleop/Tutorials/remote operation of a pr2
ssh prm "rosinstall ~/remote_operations /opt/ros/diamondback https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/sandbox/pr2_remote_teleop/remote_teleop_robot.rosinstall && source ~/remote_operations/setup.bash && rosmake --rosdep-install --rosdep-yes ros_applications continuous_ops pr2_web_apps pr2_remote_teleop pr2_gripper_grasp_adjust image_rotate voice_chat"
rosinstall ~/remote_operations /opt/ros/diamondback https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/sandbox/pr2_remote_teleop/remote_teleop_pilot.rosinstall && source ~/remote_operations/setup.bash && rosmake --rosdep-install --rosdep-yes ros_applications continuous_ops pr2_remote_teleop pr2_gripper_grasp_adjust image_rotate rviz voice_chat &&roscd pr2_remote_teleop/install && sudo ./install.sh
http://wiki.ros.org/pr2_simulator/ChangeList/1.0
* bug fix [[https://code.ros.org/trac/wg-ros-pkg/ticket/3744|#3744]]
* new stereo parameters for new stereo_image_proc [[https://code.ros.org/trac/wg-ros-pkg/ticket/3512|#3512]]
http://wiki.ros.org/pr2_simulator/ChangeList/Pre-1.0
* update prosilica API per ticket [[https://code.ros.org/trac/wg-ros-pkg/ticket/3134|#3134]]
* renamed `gazebo_ros_ocean_battery.cpp` to `gazebo_ros_power_monitor.cpp` for the plugin reproduces [[power_monitor]] functionalities. [[https://code.ros.org/trac/wg-ros-pkg/ticket/3135|API review]]
* updates for base and odometry controller configurations [[https://code.ros.org/trac/wg-ros-pkg/ticket/3463|3463]].
http://wiki.ros.org/pr2_simulator/Tutorials/BuildingAMapInSimulation
svn co https://code.ros.org/svn/wg-ros-pkg/stacks/wg_robots_gazebo/trunk/pr2_build_map_gazebo_demo/
http://wiki.ros.org/pr2_simulator/Tutorials/PR2OpenDoor/cturtle
svn co https://code.ros.org/svn/wg-ros-pkg/stacks/wg_robots_gazebo/trunk/pr2_doors_gazebo_demo/
svn co https://code.ros.org/svn/ros/stacks/ros_experimental/trunk ros_experimental
http://wiki.ros.org/pr2_simulator/Tutorials/PR2PluggingIn
svn co https://code.ros.org/svn/wg-ros-pkg/stacks/wg_robots_gazebo/trunk wg_robots_gazebo
http://wiki.ros.org/pr2_simulator/Tutorials/RunningSimulatorWithGDB/diamondback
Add '''launch-prefix="$(find gazebo_worlds)/scripts/gdbrun"''' to the gazebo node in the launch script. For reference, take a look at [[https://code.ros.org/svn/ros-pkg/stacks/simulator_gazebo/trunk/gazebo_worlds/launch/debug.launch|debug.launch]].
http://wiki.ros.org/pr2_teleop_booth
Svn co https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/sandbox/pr2_teleop_booth ~/pr2_teleop_booth
http://wiki.ros.org/pr2_teleop_general/Reviews
uri: https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_apps/trunk
http://wiki.ros.org/Projects/Building Manager/multimaster
This node needs to be configurable with a set of topics and services and should keep them completely sync'd between two masters. We can likely base this off of [[https://code.ros.org/svn/ros/stacks/multimaster_experimental/trunk/rosproxy/nodes/master_sync.py|the existing master_sync.py]]. This probably just needs some work on configurabiilty and robustness.
http://wiki.ros.org/ps3joy
Because this package can be used independently of ROS by people wishing to use a PS3 joystick in linux, I am providing a [[https://code.ros.org/gf/project/ros-pkg/scmsvn/?action=browse&path=%2F%2Acheckout%2A%2Fstacks%2Fjoystick_drivers%2Ftags%2Flatest%2Fps3joy%2Fps3joy.py|direct link]] to the driver here. In order to run this python file, you will have to have the following system dependencies installed: python, bluez, python-bluez, joystick, libusb-dev. Please report any problems you have with this driver to blaise@willowgarage.com .
http://wiki.ros.org/ps3joy/Reviews/2011-07-05 ps3joy_msg_Proposal_API_Review_API_Review
*('''Melonee''') implemented in trunk [[https://code.ros.org/gf/project/ros-pkg/scmsvn/?action=ScmCommitDetail&scm_commit_id=114715|r37418]] and example documentation on the ps3joy main page
http://wiki.ros.org/ps3joy/Tutorials/WritingTeleopNode
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/joystick_drivers_tutorials/trunk/turtle_teleop/launch/turtle_ps3joy.launch,xml,FULL,show_uri)>>
http://wiki.ros.org/RecommendedRepositoryUsage
* '''Poor Speed and Uptime''' - ROS has gone through many VCS hosting services, both external (SourceForge) and internal (code.ros.org, kforge.ros.org) and they have all had severe drawbacks. The main problem behind all these systems was that they were slow and clunky with frequent service outages.
* '''Maintenance Overhead''' - As code.ros.org and kforge.ros.org were maintained by the core ROS team, it provided significant maintenance overhead.
* '''Very fast''' - Unlike its predecessors such as SourceForge, code.ros.org, and kforge.ros.org, !GitHub is blazing fast
http://wiki.ros.org/regression_tests
* '''Which repositories can I test?''' For non-catkin stacks, you can only test the development branch that is listed in the [[https://code.ros.org/svn/release/trunk/distros/groovy.rosdistro |non-catkin rosdistro file]]. For Catkinized repositories, you can test the development branch when your repository is listed in the [[https://raw.github.com/ros/rosdistro/master/releases/groovy-devel.yaml|devel file]], and you can test the release branch/tag when your repository is listed in the [[https://raw.github.com/ros/rosdistro/master/releases/groovy.yaml|rosdistro file]].
http://wiki.ros.org/release
Please see this [[https://code.ros.org/lurker/message/20110207.202716.0ea9ac11.en.html|mailing list thread]] for more details.
Please sign up for the (low-volume) [[https://code.ros.org/mailman/listinfo/ros-release|ros-release]] mailing list to receive status updates on releases.
http://wiki.ros.org/release/Releasing/fuerte
2. `CMakeLists.txt`: Make sure your stack (i) has a `CMakeLists.txt` and (ii) it has the correct version number. The version number in your `CMakeLists.txt` is indicated in the line `rosbuild_make_distribution(<versionNum>)`. Note that the `roscreate_pkg` command does not include such a line in the `CMakeLists.txt` it creates. You need to add it. You can choose the version number yourself. Version numbers less then 1 indicate that your stack is not yet stable, and that subsequent versions will not necessarily be backward compatible. [[https://code.ros.org/svn/ros/stacks/ros/tags/ros-1.4.0/CMakeLists.txt|Example stack CMakeLists.txt file]].
http://wiki.ros.org/release/Setup/Machine
1. Request to join the [[https://code.google.com/p/ros-dry-releases/|ros-dry-releases]] project by sending an email to ros-release@code.ros.org with your Googlecode login.
- svn: {local-name: release, uri: 'https://code.ros.org/svn/release/trunk'}
http://wiki.ros.org/release/Setup/Repository
svn: {dev: 'https://code.ros.org/svn/ros-pkg/stacks/$STACK_NAME/trunk', distro-tag: 'https://code.ros.org/svn/ros-pkg/stacks/$STACK_NAME/tags/$RELEASE_NAME',
release-tag: 'https://code.ros.org/svn/ros-pkg/stacks/$STACK_NAME/tags/$STACK_NAME-$STACK_VERSION'}
svn: {dev: 'https://code.ros.org/svn/wg-ros-pkg/stacks/$STACK_NAME/trunk', distro-tag: 'https://code.ros.org/svn/wg-ros-pkg/stacks/$STACK_NAME/tags/$RELEASE_NAME',
release-tag: 'https://code.ros.org/svn/wg-ros-pkg/stacks/$STACK_NAME/tags/$STACK_NAME-$STACK_VERSION'}
http://wiki.ros.org/release/Setup/Stack
dev: 'https://code.ros.org/svn/wg-ros-pkg/stacks/$STACK_NAME/branches/cturtle_branch'
distro-tag: 'https://code.ros.org/svn/wg-ros-pkg/stacks/$STACK_NAME/tags/$RELEASE_NAME'
release-tag: 'https://code.ros.org/svn/wg-ros-pkg/stacks/$STACK_NAME/tags/$STACK_NAME-$STACK_VERSION'
http://wiki.ros.org/Repositories
http://code.ros.org/gf/projects/ros/
http://code.ros.org/gf/projects/ros-pkg/
'''[[https://code.ros.org/gf/project/ros-pkg/scmsvn/?action=AccessInfo|Source Code]]'''
http://code.ros.org/gf/projects/wg-ros-pkg/
'''[[https://code.ros.org/gf/project/wg-ros-pkg/scmsvn/?action=AccessInfo|Source Code]]'''
http://wiki.ros.org/resource_retriever/Troubleshooting
If you encounter a problem that isn't addressed on this page, please [[https://code.ros.org/trac/ros-pkg/newticket?component=robot_model&keywords=resource_retriever&owner=jfaust|file a ticket]]
The current list of open issues is available on [[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=new&status=reopened&group=milestone&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&keywords=~resource_retriever|trac]]
http://wiki.ros.org/rgbdslam_electric
svn co https://code.ros.org/svn/ros-pkg/stacks/vslam/trunk/g2o ~/ros/g2o
http://wiki.ros.org/rgbdslam_electric/evaluation
svn co https://code.ros.org/svn/ros-pkg/stacks/vslam/trunk/g2o ~/ros/g2o
svn co https://code.ros.org/svn/wg-ros-pkg/stacks/motion_planning_common/trunk ~/ros/motion_planning_common
http://wiki.ros.org/robot_model/ChangeList/1.0
* [[https://code.ros.org/trac/ros-pkg/changeset/27959|replace atof with boost::lexical_cast]]
http://wiki.ros.org/robot_model/ChangeList/1.1
* [[https://code.ros.org/trac/ros-pkg/changeset/27960|adding assimp]]
http://wiki.ros.org/robot_model/Troubleshooting
If you encounter a problem that isn't addressed on this page, please [[https://code.ros.org/trac/ros-pkg/newticket?component=robot_model&owner=meeussen|file a ticket]]
The current list of open issues is available on [[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=new&status=reopened&component=robot_model|trac]]
http://wiki.ros.org/ros-pkg
* https://code.ros.org/gf/project/ros-pkg/
http://wiki.ros.org/ROS/ChangeList/1.0
* Fixed log directory permissions [[https://code.ros.org/trac/ros/ticket/2367|2367]]
http://wiki.ros.org/ROS/ChangeList/1.1
* Fixed crash when connecting to nodes whose hostnames could not be resolved [[https://code.ros.org/gf/project/ros/scmsvn/?action=browse&path=%2Fstacks%2Fros%2Ftrunk%2Fcore%2Froscpp%2Fsrc%2Flibros%2Fsubscription.cpp&r1=9935&r2=9990|r9990]]
* [[gtest]] Upgraded to version 1.4 [[https://code.ros.org/trac/ros/ticket/2412|#2412]]
* [[rosdep]] OS detection base classes added and asserted. [[https://code.ros.org/trac/ros/ticket/2358 | 2358]]
http://wiki.ros.org/ROS/ChangeList/Pre-1.0
svn co https://code.ros.org/svn/ros/stacks/ros_experimental/trunk ~/ros/ros_experimental
http://wiki.ros.org/ROS/OSX/Tutorials/Setting up an XCode Project
Where PROJECT_NAME is the name of the xcode project you just created. This will create the additional files necessary for ROS to recognize it as a package and it will allow your xcode project to be built when rosmake is called. '''This feature will be part of ROS 1.3+, but if you want to get your hands on it early checkout [[https://code.ros.org/trac/ros/ticket/2945 | this patch]]. Otherwise you can still create your packages manually.'''
http://wiki.ros.org/ROS/Patterns/Conventions
* To check whether a name is taken, consult http://www.ros.org/browse. If you'd like your repository included in that list, send mail to the [[https://code.ros.org/mailman/listinfo/ros-users|ros-users]] mailing list.
http://wiki.ros.org/ROS/StartGuide
If you can't find a solution to your problem, then try searching [[http://answers.ros.org]] or the [[http://code.ros.org/lurker/list/ros-users.html| archived mailing list]]. Ask a question on [[http://answers.ros.org/ask]]
http://wiki.ros.org/ROSARIA/Tutorials/How to use ROSARIA
Joystick driver:: (svn)) https://code.ros.org/svn/ros-pkg/stacks/joystick_drivers/trunk/joy
control_toolbox:: https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_controllers/branches/pr2_controllers-1.4/control_toolbox
http://wiki.ros.org/ROSARIA/Tutorials/iPhone Teleop with ROSARIA/iPhone Teleop With ROSARIA
uri: https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/sandbox/teleop_base
uri: https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_controllers/branches/pr2_controllers-1.4/control_toolbox
uri: https://code.ros.org/svn/ros-pkg/stacks/joystick_drivers/trunk/joy
http://wiki.ros.org/rosbuild/CMakeLists
rosbuild_download_data(https://code.ros.org/svn/data/!svn/bc/6/trunk/willow_maps/willow-2010-02-18-0.025.pgm willow-2010-02-18-0.025.pgm b9c44f1d528c1ebd6a3f5b6720a5b8df)
http://wiki.ros.org/ros_comm/Roadmap
* Remote-launch [[roswtf]]. For inspiration, see closed ticket https://code.ros.org/trac/ros/ticket/1130
http://wiki.ros.org/ros_comm/Roadmap/2010-12-15 ros_comm 1.5 planning meeting
This brainstorming document contains much more than is achievable with our limited developer resources. We encourage developers to interested in getting involved to express interest on `ros-developers`, as well as look at the [[https://code.ros.org/trac/ros/wiki/Handoff%20List|handoff list]].
http://wiki.ros.org/roscpp/Reviews/2010-01-29 API Review
* (code) [[https://code.ros.org/svn/ros/stacks/ros/branches/cpp_message_overhaul]]
http://wiki.ros.org/rosdeb/DevelopersGuide
svn export https://code.ros.org/svn/release/download/stacks/laser_pipeline/laser_pipeline-1.2.0/
wget https://code.ros.org/svn/release/download/stacks/laser_pipeline/laser_pipeline-1.2.0/laser_pipeline-1.2.0.tar.bz2
wget https://code.ros.org/svn/release/download/stacks/laser_pipeline/laser_pipeline-1.2.0/ros-diamondback-laser-pipeline_1.2.0-0~lucid.tar.gz
http://wiki.ros.org/rosdoc_rosorg
* https://code.ros.org/svn/release/trunk
based on rospkg.distro.load_distro(), which in turn reads files from code.ros.org/svn/release..../<distro>.rosdistro
writes into rosinstall <out-file> (default repos.rosinstall), based on rospkg.distro and https://code.ros.org/svn/ros/stacks/rosorg/trunk/rosdoc_rosorg/repos.list
http://wiki.ros.org/ros_experimental
https://code.ros.org/svn/ros/stacks/ros_experimental/tags/boxturtle
https://code.ros.org/svn/ros/stacks/ros_experimental/trunk
http://wiki.ros.org/rosh/Reviews/2010-10 Bagy Ros-Developers_API_Review
https://code.ros.org/lurker/thread/20101025.210235.972a7414.en.html
http://wiki.ros.org/rosinstall/OldVersion
uri: https://code.ros.org/svn/ros/stacks/ros/tags/boxturtle
uri: https://code.ros.org/svn/wg-ros-pkg/externals/distro/boxturtle/all/
http://wiki.ros.org/rosinstall/Reviews/2010-04-12_API_Review
- svn: {local-name: ros, uri: 'https://code.ros.org/svn/ros/stacks/ros/branches/ros-1.0'}
- svn: {local-name: ros_tutorials, uri: 'https://code.ros.org/svn/ros/stacks/ros_tutorials/trunk'}
- svn: {local-name: ros_release, uri: 'https://code.ros.org/svn/ros/stacks/ros_release/trunk'}
http://wiki.ros.org/rosinstall/Troubleshooting
uri: 'https://code.ros.org/svn/ros/stacks/ros/tags/cturtle'
http://wiki.ros.org/rosinstall_generator
It always returns information about ''released'' packages - either to the gbp repositories for wet packages or to the tarball of dry stacks from the [[https://code.ros.org/svn/release/download/stacks/|SVN release repository]].
http://wiki.ros.org/roslisp/Reviews/2010-07-16 API Review
* ... this is now ticketed at https://code.ros.org/trac/ros/ticket/2897
* [Bhaskara] No; I'll add that. https://code.ros.org/trac/ros/ticket/2898
* I created a ticket to keep track of this at https://code.ros.org/trac/ros/ticket/2896
* [Bhaskara] Sure, I can add that. https://code.ros.org/trac/ros/ticket/2899.
http://wiki.ros.org/roslisp/Tutorials/BasicUsage
<<GetTaggedCode(https://code.ros.org/svn/ros/stacks/roslisp_support/trunk/roslisp_tutorials/src/talker.lisp,scheme,wikiTalker,show_uri)>>
http://wiki.ros.org/roslisp_tutorials
svn co https://code.ros.org/svn/ros/stacks/roslisp_support/trunk/roslisp_tutorials
http://wiki.ros.org/roslocate
uri: https://code.ros.org/svn/ros/stacks/ros_comm/trunk/clients/rospy
http://wiki.ros.org/ros_release/ChangeList
* [[rosdistro]]: added `distro_uri()` function to begin reducing spread of code.ros.org URL
http://wiki.ros.org/rossql
<<GetCode(https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/sandbox/rossql_examples/example1.py,#!python,35,100)>>
http://wiki.ros.org/rostopic/Reviews/2009-11 Doc Review_Doc_Review
* kwc: ticketed https://code.ros.org/trac/ros/ticket/1961
http://wiki.ros.org/rqt
* [[http://groups.google.com/group/ros-sig-rqt|rqt SIG e-mailing list]] (superseding old [[https://code.ros.org/mailman/listinfo/ros-sig-gui|rqt (aka ROS GUI) list]])
* [[https://code.ros.org/gf/project/ros/mailman/?action=ListThreads&mailman_id=8&_forum_action=ForumMessageBrowse&thread_id=44126|(Probably) the very first public discussion among community (Oct 2010)]]
http://wiki.ros.org/rviz/PluginAPI
I've created a [[https://code.ros.org/trac/ros-pkg/ticket/4930|ticket]] containing a [[https://code.ros.org/trac/ros-pkg/attachment/ticket/4930/rviz_use_ros_coordinate_convention.patch|patch]] for the current rviz trunk.
http://wiki.ros.org/rviz/Troubleshooting
[[https://code.ros.org/trac/ros-pkg/ticket/4830#comment:16|this bug report]].
[[https://code.ros.org/trac/ros-pkg/ticket/4830| For more detail, see this ticket]]
http://wiki.ros.org/rviz/Tutorials/Interactive Markers(3a20)Getting Started
Code (C++): https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/simple_marker.cpp
Code (Python) https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/python/simple_marker.py
Code (C++): https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/basic_controls.cpp
Code (Python): https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/python/basic_controls.py
Code (C++): https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/menu.cpp
Code (Python): https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/python/menu.py
Code (C++): https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/pong.cpp
Code (C++): https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/cube.cpp
Code (Python): https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/python/cube.py
http://wiki.ros.org/rviz/Tutorials/Interactive Markers(3a20)Writing a Simple Interactive Marker Server
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/interactive_marker_tutorials/src/simple_marker.cpp,cplusplus,fullSource,global_lines,show_uri,no_tag_newlines)>>
http://wiki.ros.org/rviz/Tutorials/Markers(3a20)Basic Shapes
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,FULLTEXT,global_lines,show_uri,no_tag_newlines)>>
Ok, let's break down the code piece by piece: <<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,INCLUDES,global_lines,no_tag_newlines)>> You should have seen the `ROS` include by now. We also include the <<MsgLink(visualization_msgs/Marker)>> message definition.
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,INIT,global_lines,no_tag_newlines)>> This should look familiar. We initialize ROS, and create a `ros::Publisher` on the `visualization_marker` topic.
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,SHAPE_INIT,global_lines,no_tag_newlines)>> Here we create an integer to keep track of what shape we're going to publish. The four types we'll be using here all use the <<MsgLink(visualization_msgs/Marker)>> message in the same way, so we can simply switch out the shape type to demonstrate the four different shapes.
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,MARKER_INIT,global_lines,no_tag_newlines)>> This begins the meat of the program. First we create a <<MsgLink(visualization_msgs/Marker)>>, and begin filling it out. The `header` here is a <<MsgLink(roslib/Header)>>, which should be familiar if you've done the [[tf]] [[tf/Tutorials|tutorials]]. We set the `frame_id` member to `/my_frame` as an example. In a running system this should be the frame relative to which you want the marker's pose to be interpreted.
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,NS_ID,global_lines,no_tag_newlines)>> The namespace (`ns`) and `id` are used to create a unique name for this marker. If a marker message is received with the same `ns` and `id`, the new marker will replace the old one.
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,TYPE,global_lines,no_tag_newlines)>> This `type` field is what specifies the kind of marker we're sending. The available types are enumerated in the <<MsgLink(visualization_msgs/Marker)>> message. Here we set the type to our `shape` variable, which will change every time through the loop.
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,ACTION,global_lines,no_tag_newlines)>> The `action` field is what specifies what to do with the marker. The options are `visualization_msgs::Marker::ADD` and `visualization_msgs::Marker::DELETE`. `ADD` is something of a misnomer, it really means "create or modify".
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,POSE,global_lines,no_tag_newlines)>> Here we set the pose of the marker. The <<MsgLink(geometry_msgs/Pose)>> message consists of a <<MsgLink(geometry_msgs/Vector3)>> to specify the position and a <<MsgLink(geometry_msgs/Quaternion)>> to specify the orientation. Here we set the position to the origin, and the orientation to the identity orientation (note the 1.0 for `w`).
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,SCALE,global_lines,no_tag_newlines)>> Now we specify the scale of the marker. For the basic shapes, a scale of 1 in all directions means 1 meter on a side.
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,COLOR,global_lines,no_tag_newlines)>> The color of the marker is specified as a <<MsgLink(std_msgs/ColorRGBA)>>. Each member should be between 0 and 1. An alpha (`a`) value of 0 means completely transparent (invisible), and 1 is completely opaque.
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,LIFETIME,global_lines,no_tag_newlines)>> The `lifetime` field specifies how long this marker should stick around before being automatically deleted. A value of `ros::Duration()` means never to auto-delete.
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,PUBLISH,global_lines,no_tag_newlines)>> Now we publish the marker.
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,CYCLE_SHAPES,global_lines,no_tag_newlines)>> This code lets us show all four shapes while just publishing the one marker message. Based on the current shape, we set what the next shape to publish will be.
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/basic_shapes.cpp,cplusplus,SLEEP_END,global_lines,no_tag_newlines)>> Sleep and loop back to the top.
http://wiki.ros.org/rviz/Tutorials/Markers(3a20)Points and Lines
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/points_and_lines.cpp,cplusplus,FULLTEXT,global_lines,show_uri)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/points_and_lines.cpp,cplusplus,MARKER_INIT,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/points_and_lines.cpp,cplusplus,ID,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/points_and_lines.cpp,cplusplus,TYPE,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/points_and_lines.cpp,cplusplus,SCALE,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/points_and_lines.cpp,cplusplus,COLOR,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/visualization_tutorials/trunk/visualization_marker_tutorials/src/points_and_lines.cpp,cplusplus,HELIX,global_lines)>>
http://wiki.ros.org/rviz/UserGuide
rviz is setup so that new displays can be added through plugins. In fact, even the built-in displays are loaded through the "default" plugin. The end result for you, the user, is that there is a way to load/unload plugins from the UI. (Note that as of [[http://code.ros.org/lurker/message/20120814.213049.12b192ce.en.html|this commit]], all plugins are loaded automatically - there is no more UI.) If you select the '''Plugins->Manage...''' menu item, it will pop up a dialog letting you manage loading/unloading plugins:
http://wiki.ros.org/rviz_imu_plugin
The package has been [[https://code.ros.org/trac/ros-pkg/ticket/5476 | ticketed]] for inclusion in ROS.
http://wiki.ros.org/sensor_msgs/Reviews/2009-09-30_Doc_Review
* (./) !JointState needs to have comments https://code.ros.org/trac/ros-pkg/ticket/3006
http://wiki.ros.org/sensor_msgs/Reviews/2010-10-04_Ranger_Proposal_API_Review
The review period is now over. See https://code.ros.org/trac/ros-pkg/ticket/4488 for the ticket and final version of the message.
http://wiki.ros.org/sensor_msgs/Reviews/2011-12-25_NavSatTime_Proposal_API_Review
* ('''Chad''') I'm not currently getting notifications for edits of this page. Is this true for everyone subscribed? I'm likely going to extend this review until past the new year, possibly up until the freeze. There is currently a [[https://code.ros.org/trac/ros/ticket/3788|ticket filed]] about the email notification issue.
* Message was approved by final email vote. See [[https://code.ros.org/trac/ros-pkg/ticket/5355|this ticket]] for status.
http://wiki.ros.org/sensor_msgs/Reviews/Python PointCloud2 _API_Review
https://code.ros.org/trac/ros-pkg/attachment/ticket/4440/point_cloud.py
http://wiki.ros.org/Sensors/3D Sensors
. [[https://code.ros.org/mailman/listinfo/ros-kinect|ros-kinect]]
http://wiki.ros.org/Sensors/Cameras
There has recently been [[https://code.ros.org/lurker/message/20110217.092543.3767aee5.en.html|interest]] in developing a single standard USB camera driver for the eturtle release of ROS. Parameter standardization may also be a worthwhile effort at some level.
http://wiki.ros.org/sig/Drivers
* [[https://code.ros.org/lurker/list/ros-sig-drivers.html|discussion archives]].
http://wiki.ros.org/sig/Parameters
https://code.ros.org/lurker/thread/20130423.132934.4f273607.en.html
http://wiki.ros.org/sig/roslaunch
* Similar: Support custom meta-tag to roslaunch file (https://code.ros.org/trac/ros/ticket/3515), (https://groups.google.com/forum/?fromgroups=#!topic/ros-sig-roslaunch/A1INolWm0Z4)
http://wiki.ros.org/simulator_gazebo/ChangeList/1.0
* [[https://code.ros.org/trac/ros-pkg/ticket/3830|#3830 - case sensitive STL extension detection.]]
* [[https://code.ros.org/trac/ros-pkg/ticket/3767|ODE joint limtits fix]]
* [[https://code.ros.org/trac/ros-pkg/ticket/3781|fix rpath setting for gazebo binary]]
* [[https://code.ros.org/trac/ros-pkg/ticket/3742|imu plugin fix]]
* [[https://code.ros.org/trac/ros-pkg/ticket/3743|p3d plugin fix]]
* [[https://code.ros.org/trac/ros-pkg/ticket/3649|patch to explicit link gazebo_server against freeimage libraries]]
* generate tmp mesh in `/tmp/gazebo-[userid]-mesh` directory per ticket [[https://code.ros.org/trac/ros-pkg/ticket/3610|#3610]]
http://wiki.ros.org/simulator_gazebo/ChangeList/1.1
* gazebo_ros_p3d warns and returns if body specified do not exist [[https://code.ros.org/trac/ros-pkg/ticket/3423|3423]].
http://wiki.ros.org/simulator_gazebo/ChangeList/1.7
* support switching old gazebo pre 1.0 release to sdf 1.3 or sdf 1.2 in urdf gazebo extensions. Please update your models. For example, see changes in [[https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_common/trunk/pr2_description|pr2_description]].
http://wiki.ros.org/simulator_gazebo/ChangeList/Pre-1.0
* fix manifest.xml export flag ([[https://code.ros.org/trac/ros-pkg/ticket/3484|#3484]])
* doc review update ([[https://code.ros.org/trac/ros-pkg/ticket/3457|#3457]])
* bug fix for `gazebo_pug_world_state.cpp` plugin: ticket [[https://code.ros.org/trac/ros-pkg/ticket/3424|#3424]].
* added ability to load visual mesh from `*.stl` specified in URDF. [[pr2_ogre]] is no longer needed. (addresses [[https://code.ros.org/trac/wg-ros-pkg/ticket/2973|ticket #2973]]).
* fix parallel build error due to dependency bug [[https://code.ros.org/trac/ros-pkg/ticket/3349|#3349]]
* player CMake variable fix [[https://code.ros.org/trac/ros-pkg/ticket/3290]]
* fix bug [[https://code.ros.org/trac/ros-pkg/ticket/3275]]
* fix bug [[https://code.ros.org/trac/ros-pkg/ticket/3251]]
* fix bug [[https://code.ros.org/trac/ros-pkg/ticket/3222|#3222]]
* fix bug [[https://code.ros.org/trac/ros-pkg/ticket/3223|#3223]]
http://wiki.ros.org/simulator_gazebo/Roadmap
* Write more tutorials and documentation. Consider move gazebo to code.ros.org
http://wiki.ros.org/simulator_gazebo/SystemRequirements
* [[https://code.ros.org/trac/ros-pkg/ticket/3352|X_CreateGC:BadDrawable (#3352)]]
http://wiki.ros.org/simulator_gazebo/Troubleshooting
* If the error appears to be ROS related (i.e. [[gazebo|Gazebo ROS API]], [[gazebo_plugins]], [[https://code.ros.org/svn/ros-pkg/stacks/simulator_gazebo/trunk/gazebo/src/|gazebo plugins for ROS]]), please login to your profile on [[https://code.ros.org/trac/ros-pkg/|ros-pkg trac]] and [[https://code.ros.org/trac/ros-pkg/newticket|file a new ticket]].
* If the error appears to be PR2 related (i.e. related to [[pr2_gazebo_plugins|PR2 Gazebo plugins]], [[pr2_gazebo|PR2 simulation]]), please login to your profile on [[https://code.ros.org/trac/wg-ros-pkg/|wg-ros-pkg trac]] and [[https://code.ros.org/trac/wg-ros-pkg/newticket|file a new ticket]].
* See [[https://code.ros.org/svn/ros-pkg/stacks/simulator_gazebo/trunk/gazebo_worlds/launch/debug.launch|this example launch file for starting gazebo with gdb]].
http://wiki.ros.org/simulator_gazebo/Tutorials/SpawningObjectInSimulation
Several sample objects are provided in [[https://code.ros.org/svn/ros-pkg/stacks/simulator_gazebo/trunk/gazebo_worlds/objects|gazebo_worlds/objects]]. For example, you can spawn a desk by typing
Taking a brief look at [[https://code.ros.org/svn/ros-pkg/stacks/simulator_gazebo/trunk/gazebo_worlds/launch/table.launch|table.launch]]:
http://wiki.ros.org/simulator_stage/Reviews/2011-1 Diamondback Doc_Doc_Review
* Still a problem: ticketed: https://code.ros.org/trac/ros/ticket/3272
http://wiki.ros.org/single_joint_position_action/Reviews/2010-01-13_Doc_Review
(./) Ticketed: https://code.ros.org/trac/wg-ros-pkg/ticket/3673
(./) Ticketed: https://code.ros.org/trac/wg-ros-pkg/ticket/3672
http://wiki.ros.org/slam_gmapping/Roadmap
* Incorporate pending patch for efficient offline mapping: https://code.ros.org/trac/ros-pkg/ticket/1551
http://wiki.ros.org/smach/Tutorials/Concurrent States
<<GetCode(https://code.ros.org/svn/ros-pkg/stacks/executive_smach_tutorials/trunk/smach_tutorials/examples/concurrence2.py,#!python)>>
http://wiki.ros.org/smach/Tutorials/Create a hierarchical state machine
<<GetCode(https://code.ros.org/svn/ros-pkg/stacks/executive_smach_tutorials/trunk/smach_tutorials/examples/state_machine_nesting2.py,#!python)>>
http://wiki.ros.org/smach/Tutorials/Getting Started
<<GetCode(https://code.ros.org/svn/ros-pkg/stacks/executive_smach_tutorials/trunk/smach_tutorials/examples/state_machine_simple.py,#!python)>>
http://wiki.ros.org/smach/Tutorials/Iterator container
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/executive_smach_tutorials/trunk/smach_tutorials/examples/iterator_tutorial.py,python,FULLTEXT,show_uri,no_tag_newlines,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/executive_smach_tutorials/trunk/smach_tutorials/examples/iterator_tutorial.py,python,ITERATOR,no_tag_newlines,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/executive_smach_tutorials/trunk/smach_tutorials/examples/iterator_tutorial.py,python,CONTAINER,no_tag_newlines,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/executive_smach_tutorials/trunk/smach_tutorials/examples/iterator_tutorial.py,python,ADDCONTAINER,no_tag_newlines,global_lines)>>
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/executive_smach_tutorials/trunk/smach_tutorials/examples/iterator_tutorial.py,python,ADDITERATOR,no_tag_newlines,global_lines)>>
http://wiki.ros.org/smach/Tutorials/Nesting State Machines
<<GetCode(https://code.ros.org/svn/ros-pkg/stacks/executive_smach_tutorials/trunk/smach_tutorials/examples/state_machine_nesting2.py,#!python)>>
http://wiki.ros.org/smach/Tutorials/Simple Action State
<<GetCode(https://code.ros.org/svn/ros-pkg/stacks/executive_smach_tutorials/trunk/smach_tutorials/examples/actionlib2.py,#!python)>>
http://wiki.ros.org/smach/Tutorials/Simple State Machine
<<GetCode(https://code.ros.org/svn/ros-pkg/stacks/executive_smach_tutorials/trunk/smach_tutorials/examples/state_machine2.py,#!python)>>
http://wiki.ros.org/smach/Tutorials/User Data
<<GetCode(https://code.ros.org/svn/ros-pkg/stacks/executive_smach_tutorials/trunk/smach_tutorials/examples/user_data2.py,#!python)>>
http://wiki.ros.org/smach/Tutorials/User Data Passing
<<GetCode(https://code.ros.org/svn/ros-pkg/stacks/executive_smach_tutorials/trunk/smach_tutorials/examples/user_data2.py,#!python)>>
http://wiki.ros.org/Source code
Core ROS code is hosted in the ROS project at https://code.ros.org
svn co https://code.ros.org/svn/ros/stacks/ros/tags/distro_name ros
ROS [[Packages|packages]] are hosted in the ros-pkg and wg-ros-pkg projects at https://code.ros.org
svn co https://code.ros.org/svn/wg-ros-pkg/externals/distro/distro_name/all distro-all
svn co https://code.ros.org/svn/ros-pkg/stacks/stack_name/tags/distro_name stack_name
svn co https://code.ros.org/svn/wg-ros-pkg/stacks/stack_name/tags/distro_name stack_name
svn co https://code.ros.org/svn/ros-pkg/trunk ros-pkg
svn co https://code.ros.org/svn/wg-ros-pkg/trunk wg-ros-pkg
http://wiki.ros.org/spacenav_node/Tutorials/WritingTeleopNode
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/joystick_drivers_tutorials/trunk/turtle_teleop/launch/turtle_spacenav.launch,xml,FULL,show_uri)>>
http://wiki.ros.org/sr_hand_ethercat
uri: https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/sandbox/shadow_robot_ethercat
uri: https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_mechanism/trunk
http://wiki.ros.org/sr_hand_ethercat/Tutorials/RunningShadowHandOnDesk
uri: https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_ethercat_drivers/trunk
uri: https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_robot/trunk/pr2_etherCAT
uri: https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/sandbox/shadow_robot_ethercat
uri: https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_mechanism/trunk
http://wiki.ros.org/StackReleaseProcess
wget https://code.ros.org/svn/ros/stacks/ros/trunk/core/rosbuild/bin/create_release.py -O $ROS_ROOT/create_release.py
http://wiki.ros.org/stage/Tutorials/SimulatingOneRobot
svn co https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/sandbox/teleop_base teleop_base
http://wiki.ros.org/starmac-ros-pkg/Roadmap
* My sense is that if any GUIs are to be developed for starmac-ros-pkg specifically, they should be discrete, modular components. Probably using QT, especially given the [[https://code.ros.org/lurker/message/20101026.212039.e866e943.en.html|impending move]] to QT for the ROS GUI tools. In an ideal world, one would have the choice of a bunch of custom widgets to put together with stock ones in QT Designer to make a GUI that's right for one's specific project.
http://wiki.ros.org/StuartGlaser/HowtoTeleopCockpit
##svn co https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_cockpit/tags/unstable pr2_cockpit
http://wiki.ros.org/StuartGlaser/RobotGains
These gains were being used by plugging in and the manipulation demos. Wim made these the default gains in [[https://code.ros.org/trac/wg-ros-pkg/ticket/4243|April 2010]].
http://wiki.ros.org/StuartGlaser/RunningBeltCompensation
svn co https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_mechanism/branches/beltcomp_cturtle pr2_mechanism
svn co https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_common/branches/beltcomp pr2_common
svn co https://code.ros.org/svn/wg-ros-pkg/stacks/pr2_robot/branches/beltcomp pr2_robot
http://wiki.ros.org/Support
To stay on top of the latest ROS news, subscribe to the [[https://code.ros.org/mailman/listinfo/ros-users |ros-users mailing list]] mailing list, and feel free to have a look at the [[http://code.ros.org/lurker/list/ros-users.html|ros-users archive]].
2. Next, check the [[http://code.ros.org/lurker/list/ros-users.html|ros-users mailing list archive]] and [[http://answers.ros.org|ROS Answers]] to see if someone else has asked your question or reported your issue.
http://wiki.ros.org/SVNUsrtoGitHubEmailMap
This page is for mapping code.ros.org SVN usernames to !GitHub emails.
== code.ros.org username map ==
This is specific to code.ros.org usernames. kforge.ros.org usernames may be different
http://wiki.ros.org/swissranger_camera/Tutorials/Download and install swissranger_camera
svn co https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/camera_drivers_experimental
http://wiki.ros.org/tf2/Tutorials/Writing a tf2 broadcaster(2028)C(2b2b29)
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf2/src/turtle_tf2_broadcaster.cpp,#!cplusplus)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf2/src/turtle_tf2_broadcaster.cpp,#!cplusplus,2,2)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf2/src/turtle_tf2_broadcaster.cpp,#!cplusplus,9,9)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf2/src/turtle_tf2_broadcaster.cpp,#!cplusplus,10,12)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf2/src/turtle_tf2_broadcaster.cpp,#!cplusplus,14,14)>>
http://wiki.ros.org/tf/Tutorials/Writing a tf broadcaster(2028)C(2b2b29)
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus,2,2)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus,9,9)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus,10,12)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus,13,13)>>
<<GetCode(https://code.ros.org/svn/ros-pkg/branches/trunk_cturtle/stacks/ros_pkg_tutorials/turtle_tf/src/turtle_tf_broadcaster.cpp,#!cplusplus,14,14)>>
http://wiki.ros.org/tf_conversions/Troubleshooting
If you encounter a problem that isn't addressed on this page, please [[https://code.ros.org/trac/ros-pkg/newticket?component=geometry&keywords=tf_conversions&owner=tfoote|file a ticket]]
The current list of open issues is available on [[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=new&status=reopened&group=milestone&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&keywords=~tf_conversions|trac]]
http://wiki.ros.org/tod_stub
rosinstall ~/tod_stub_dev https://code.ros.org/svn/wg-ros-pkg/branches/trunk_diamondback/stacks/object_recognition/tod_stub/tod_stub.install
http://wiki.ros.org/trajectory_msgs/Reviews/Cartesian Trajectories_API_Review_2013_06_05
https://code.ros.org/lurker/thread/20130605.194058.361c6da3.en.html
http://wiki.ros.org/trex
https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/stacks/executive_trex/
http://wiki.ros.org/trex/Tutorials/CreateProject
* [[http://code.ros.org/svn/wg-ros-pkg/trunk/stacks/trex/trex_core/trex_create_template/CMakeLists.txt|CMakeLists.txt]] - A cmake file expected by ROS that will declare binaries required for ''trexrun'' and ''trexparse''.
* [[http://code.ros.org/svn/wg-ros-pkg/trunk/stacks/trex/trex_core/trex_create_template/src/trex_create_template_components.cpp|demo_components.cpp]] - A placeholder for any custom components you might wish to integrate in order to extend the capabilities of the executive
* [[http://code.ros.org/svn/wg-ros-pkg/trunk/stacks/trex/trex_core/trex_create_template/src/temp_init_gen_demo.cpp|temp_init_gen_demo.cpp]]- A generated file providing a definition for a standard initialization package provided for all trex application packages.
* [[http://code.ros.org/svn/wg-ros-pkg/trunk/stacks/trex/trex_core/trex_create_template/src/temp_reg_gen.cpp|temp_reg_gen.cpp]] - A generated registration file providing a registration function used in all trex application packages.
* nddl - A directory for NDDL model files. This directory includes a strawman model ([[https://code.ros.org/svn/wg-ros-pkg/trunk/stacks/trex/trex_core/trex_create_template/nddl/demo.nddl|demo.nddl]]) to get you started:
* [[https://code.ros.org/svn/wg-ros-pkg/trunk/stacks/trex/trex_core/trex_create_template/cfg/demo.cfg|demo.cfg]] which provides a 2-reactor configuration.
* [[https://code.ros.org/svn/wg-ros-pkg/trunk/stacks/trex/trex_core/trex_create_template/cfg/debug.cfg|debug.cfg]] which is used to set debug logging levels for T-REX.
* [[http://code.ros.org/svn/wg-ros-pkg/trunk/stacks/trex/trex_core/trex_create_template/test/trex_config.launch|trex_config.launch]] - A ROS launch file used to set T-REX parameters. These will be used when running the executive.
* [[http://code.ros.org/svn/wg-ros-pkg/trunk/stacks/trex/trex_core/trex_create_template/test/demo/demo.client.nddl|demo/demo.client.nddl]] - The input nddl file for the *client* reactor of the *demo* agent.
* [[http://code.ros.org/svn/wg-ros-pkg/trunk/stacks/trex/trex_core/trex_create_template/test/demo/demo.server.nddl|demo/demo.server.nddl]] - The input nddl file for the *server* reactor of the *demo* agent.
* [[http://code.ros.org/svn/wg-ros-pkg/trunk/stacks/trex/trex_core/trex_create_template/test/demo/demo.test|demo/demo.test]] - A roslaunch file suitable for launching a roscore with required parameters and for use with rostest.
* [[http://code.ros.org/svn/wg-ros-pkg/trunk/stacks/trex/trex_core/trex_create_template/test/demo/demo.valid|demo/demo.valid]] - An event log populated with expected output as timeline changes are requested and as they are expected to occur. This is used as part of the regression testing framework.
http://wiki.ros.org/trex/Tutorials/Getting started
svn co https://code.ros.org/svn/wg-ros-pkg/branches/trunk_cturtle/stacks/executive_trex \
http://wiki.ros.org/trex/Tutorials/Visualize prior execution
Observe that the tick value becomes 0.0. Both the client and server reactors have a single *hello* timeline. The color of the timeline is determined by the color of the reactor that _owns_ that timeline. Clearly, the server reactor owns this timeline as is consistent with the nddl input shown [[http://code.ros.org/svn/wg-ros-pkg/trunk/stacks/trex/trex_core/trex_create_template/test/demo/demo.server.nddl|earlier]]. The earliest end time is shown for the initial value (it is 1 in this case).
http://wiki.ros.org/urdf/Reviews/2009-12-08 API_Review
* implement urdf checks, ticket [[https://code.ros.org/trac/ros-pkg/ticket/3261|#3261]]
* special cases, ticket [[https://code.ros.org/trac/ros-pkg/ticket/3355|#3355]]
http://wiki.ros.org/urdf/Reviews/2010-12-08 API_Review
* [[https://code.ros.org/trac/ros-pkg/search?q=urdf-2.0|trac tickets for urdf-2.0]]
* [[https://code.ros.org/trac/ros-pkg/ticket/4345|#4345: defect: support trimesh primitive in urdf (new)]]
* [[https://code.ros.org/trac/ros-pkg/ticket/4263|#4263: enhancement: urdf: graph support (new)]]
* [[https://code.ros.org/trac/ros-pkg/ticket/4262|#4262: enhancement: urdf: support multiple inertials / collisions / visuals per link (new)]]
* [[https://code.ros.org/trac/ros-pkg/ticket/3466|#3466: defect: urdf::JointDynamics -- discuss necessary parameters (e.g. efficiency) and ... (new)]]
* support for more than 2 types of meshes (visual, self-collision, environment-collision), [[https://code.ros.org/trac/ros-pkg/ticket/4270|#4270: enhancement: Support for multiple "visuals" fields in URDF for a single link (new)]]
* [[https://code.ros.org/trac/ros-pkg/ticket/4611|Support for a sensor block for calibration.]]
* [[https://code.ros.org/trac/ros-pkg/ticket/4345|#4345: defect: support trimesh primitive in urdf (new)]]
* [[https://code.ros.org/trac/ros-pkg/ticket/4263|#4263: enhancement: urdf: graph support (new)]]
* [[https://code.ros.org/trac/ros-pkg/ticket/4262|#4262: enhancement: urdf: support multiple inertials / collisions / visuals per link (new)]]
* [[https://code.ros.org/trac/ros-pkg/ticket/3466|#3466: defect: urdf::JointDynamics -- discuss necessary parameters (e.g. efficiency) and ... (new)]]
* [[https://code.ros.org/trac/ros-pkg/ticket/4611|#4611: discuss with Vijay about the need for sensor information, possibly support as another extension outside of URDF]].
http://wiki.ros.org/urdf/Reviews/2010-12-09 API_Review
1. Decide what additional sensor information is needed for calibration per tikcet [[https://code.ros.org/trac/ros-pkg/ticket/4611|#4611]]. Below are tags proposed on the [[http://openrave.programmingvision.com/index.php/Started:COLLADA|OpenRave COLLADA]] page.
1. Decide what additional sensor information is needed for calibration per tikcet [[https://code.ros.org/trac/ros-pkg/ticket/4611|#4611]]. Below are tags proposed on the [[http://openrave.programmingvision.com/index.php/Started:COLLADA|OpenRave COLLADA]] page.
http://wiki.ros.org/urdf/Reviews/2012-06-12 API_Review
Full mail for the mailing-list available here: http://code.ros.org/lurker/message/20120613.100210.df16f027.en.html
http://wiki.ros.org/urdf/Troubleshooting
If you encounter a problem that isn't addressed on this page, please [[https://code.ros.org/trac/ros-pkg/newticket?component=robot_model&keywords=urdf&owner=meeussen|file a ticket]]
The current list of open issues is available on [[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=new&status=reopened&group=milestone&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component&keywords=~urdf|trac]]
http://wiki.ros.org/urdf/XML/sensor
. Image format of the camera. Can be any of the strings defined in [[https://code.ros.org/trac/ros-pkg/browser/stacks/common_msgs/trunk/sensor_msgs/include/sensor_msgs/image_encodings.h|image_encodings.h insdie sensor_msgs]].
http://wiki.ros.org/vfh_recognition
svn co https://code.ros.org/svn/wg-ros-pkg/stacks/tabletop_object_perception/trunk/vfh_recognition
svn co https://code.ros.org/svn/wg-ros-pkg/stacks/tabletop_object_perception/trunk/vfh_recognizer_fs
svn co https://code.ros.org/svn/wg-ros-pkg/stacks/tabletop_object_perception/trunk/vfh_recognizer_fs_test
http://wiki.ros.org/vision_opencv/ChangeList/1.8
* fix private initialized() https://code.ros.org/trac/ros-pkg/ticket/5570
* fix the from YUV422 conversion and add tests for the C++ API https://code.ros.org/trac/ros-pkg/ticket/5548
* added missing TYPE_* conversions from https://code.ros.org/trac/ros-pkg/ticket/5556
http://wiki.ros.org/vision_opencv/ChangeList/1.9
* fix the from YUV422 conversion and add tests for the C++ API https://code.ros.org/trac/ros-pkg/ticket/5548
http://wiki.ros.org/visualization_experimental
Use trac to [[https://code.ros.org/trac/ros-pkg/newticket?component=visualization&type=defect&keywords=qt|report bugs]] or [[https://code.ros.org/trac/ros-pkg/newticket?component=visualization&type=enhancement&keywords=qt|request features]]. [ [[https://code.ros.org/trac/ros-pkg/query?status=assigned&status=new&status=reopened&component=visualization&keywords=~qt|View active tickets]] ]
http://wiki.ros.org/vslam
$ svn co https://code.ros.org/svn/ros-pkg/stacks/vslam/trunk VSLAMDIR
http://wiki.ros.org/wg-ros-pkg
* https://code.ros.org/gf/project/wg-ros-pkg/
http://wiki.ros.org/wg_robots_gazebo
/!\ Note that wg_robots_gazebo has been moved to [[http://code.ros.org/svn/wg-ros-pkg/stacks/wg_robots_gazebo/trunk]], below is the [[rosinstall]] line to use:
- svn: {local-name: stacks/wg_robots_gazebo, uri: 'https://code.ros.org/svn/wg-ros-pkg/stacks/wg_robots_gazebo/trunk'}
http://wiki.ros.org/wgtest_data_analysis
Open a ticket [[https://code.ros.org/trac/wg-ros-pkg/newticket?component=hardware+test|here]].
http://wiki.ros.org/wifi_comm/Tutorials/Download and install wifi_comm
svn co https://code.ros.org/svn/ros/stacks/multimaster_experimental/trunk multimaster_experimental
http://wiki.ros.org/wiimote/Tutorials/WritingTeleopNode
<<GetTaggedCode(https://code.ros.org/svn/ros-pkg/stacks/joystick_drivers_tutorials/trunk/turtle_teleop/launch/turtle_wii.launch,xml,FULL,show_uri)>>
http://wiki.ros.org/WikiMacros
https://code.ros.org/lurker/thread/20110131.134604.f6e00a71.en.html
https://code.ros.org/lurker/message/20110131.134604.f6e00a71.en.html
http://wiki.ros.org/win-ros-pkg/Team
* [[https://code.ros.org/gf/project/eros/scmsvn/?action=AccessInfo|Yujin Robot]]
If you would like to contribute to eros, either as a user ([[eros|wiki]] or [[https://code.ros.org/gf/project/eros/mailman/|mailing list]] contributions) or developer, feel free to contact DanielStonier at the email address above or via the mailing lists.
http://wiki.ros.org/win_ros/patch
> svn co https://code.ros.org/svn/ros/stacks/ros_comm/trunk ./ros_comm
> svn co https://code.ros.org/svn/ros/stacks/ros_comm/trunk ./ros_comm
http://wiki.ros.org/win_ros/Troubleshooting/Actionlib Hangs
See [[https://code.ros.org/trac/ros-pkg/ticket/5500|#5500]] for more details.
http://wiki.ros.org/WorkOnTrunkStack
svn co https://code.ros.org/svn/ros-pkg/stacks/mystack/trunk ~/ros/mystack
http://wiki.ros.org/xacro/Reviews/2009-09-23 API Review
* undefined parameters should error out hard. [[https://code.ros.org/trac/ros-pkg/ticket/1176|#1176]]
* Add recursive variable substitution [[https://code.ros.org/trac/ros-pkg/ticket/1497|#1497]]. Consider postponing until after 1.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment