January 16, 2018
Self-Driving Development Platform Hacking Based On ROS-For Engineers and Hackers

@PIX_Moving wrote:

Theme
Open Source Self-Driving Development Platform Hacking

Key Words
FIVE Days/ TEN Engineers/ TWO Groups/TWO-mile Park Road Test/TWO Self-driving Vehicles

What’s In There:

  • Move-it Hackathon is a five-day hands-on workshop during which ten talented engineers (divided into two groups) worldwide collaborate with each other to build an affordable (within $10K excluding various sensors) drive-by-wire development platform for self-driving.

  • On the last day, there will be a small and fun race between the two groups. The whole hackathon process and outputs will be open to the public in various ways.

  • Meanwhile, the most special and unique experiences are created for global engineers: collaborative development, fabrication workshop, social parties, keynote speech, mentor communication and local exploration etc… You are bound to get inspired.

What To Hack

  • Hacking of car control, both lateral and longitudinal controls, to achieve drive-by-wire

  • Self-driving setup and test of 1/16 scale car powered by Raspberry Pi

  • Installation and test run of self-driving software Autoware on full-sized car

Where
C-Zone Hackspace, Guiyang, Guizhou, China

When
March 9th to March 13th 2018 (Five days)

The ultimate goal of Move-It Hackathon is to co-create an open, democratized, affordable and reliable by-wire control development platform for self-driving. More details can be found here

We’ll make full arrangement for the development components & accessories stuff, also free accommodation & foods, and reimbursement for transportation. Check Move-it FAQ here https://www.pixmoving.com/move-it

Surprise and prize for Move-it Hackathon participants!
Contact: Email to nancy@pixmoving.com or call at 0086.18111991219 for any questions or concerns

Apply Move-it Hackathon here

Posts: 3

Participants: 2

Read full topic

by @PIX_Moving Nancy Lee on January 16, 2018 10:58 AM

January 15, 2018
Spatio-Temporal Voxel Layer [Experimental]

@smac wrote:

Hi!

I’m the maintainer and a senior robotics engineer at Simbe Robotics working on a new package I’ve dubbed the Spatio-Temporal voxel layer. The goal of this package is to be a 1:1 replacement for the voxel layer improving on raytracing, marking, and efficient searching the configuration space. It also includes work for decaying voxel values over time and infrastructure to do rudimentary dynamic obstacle tracking.

I am hoping to get some community contributions, bug reports, and features. It’s important to get community buy-in in the development process. It is a highly experimental project in its infancy, the wiki page in the repository posted below contains descriptions of features in development and installation instructions to get involved.

Please feel free to reach out to me at stevenmacenski [at] gmail [dot] com if you or your company are especially interested in it or assisting in development or feature requests and you want to touch base about how to get involved.

Thanks!

Posts: 1

Participants: 1

Read full topic

by @smac Steve M on January 15, 2018 10:15 PM

January 14, 2018
Problems with OpenCR 1.0

@Bbybo93 wrote:

Hey all,

My final year project requires a robot that is capable of SLAM and autonomous navigation, Turtlebot 3 was perfect for it!

Fast forward, I have assembled the Turtlebot 3 but I am unable to ‘move’ it by pressing the SW1 and SW2 on OpenCR.

Also, now that the assembly is done. Do I need to use Arduino IDE to configure OpenCR first, before proceeding to setting up ROS-Master & Slave?

Posts: 2

Participants: 2

Read full topic

by @Bbybo93 Bobby Lim on January 14, 2018 08:22 PM

January 11, 2018
Webinar | How to create your Robotics MOOC based on ROS?

@YUHONG_LIN wrote:

Dear Roboticists,

The webinar about How to create your Robotics MOOC based on ROS will be held on January 16, 2018 from 6 p.m - 7 p.m CET.

Attendance is free.
To assist us in planning, please pre-register here to confirm your participation: http://www.theconstructsim.com/webinar-how-to-create-your-robotics-mooc-based-on-ros-2/

DESCRIPTION

A completely practical webinar to show you how to create a Robotics MOOC based on ROS using free tools.

In this one-hour webinar we will show you how to build your robotics MOOC, from the creation of the syllabus of your course, to the robotics simulations to use for practicing, going through testing in real time the code the students should build along the course. We will also show you how you can publish that course and earn some money.

  • All the attendants will do the procedure live, at the same time with the speaker! The speaker will guide you step by step. Be ready to do some work - No installation of anything required. Any type of computer will work.

  • All the attendants will receive a pdf document with all the steps described during the webinar (only for attendants).

  • Presentation will be 40 minutes plus 20 minutes questions.

WHO SHOULD ATTEND?

People who want to create their own MOOC ROS course in an effective way, and to make ROS learning engaging and fun, ensuring that the ROS learners get the best possible results.

SPEAKER

RICARDO TÉLLEZ, Ph.D. (https://www.linkedin.com/in/ricardotellez/4)

= Pre-registration =
To assist us in planning, pre-registration is required.
Pre-registration website: http://www.theconstructsim.com/webinar-how-to-create-your-robotics-mooc-based-on-ros-2/

= More Information =
You can contact us with questions and doubts here: info@theconstructsim.com

Posts: 1

Participants: 1

Read full topic

by @YUHONG_LIN on January 11, 2018 05:42 PM

January 10, 2018
New Packages for Kinetic 2018-01-09

@tfoote wrote:

We’re happy to announce 22 new packages and 175 updated packages. This includes the restoration of the regressed costmap packages from the last sync.

Thank you to all the maintainers and contributors who have helped make this possible.

Package Updates for kinetic

Added Packages [22]:

  • ros-kinetic-bus-server: 0.1.1-0
  • ros-kinetic-care-o-bot: 0.6.6-0
  • ros-kinetic-care-o-bot-desktop: 0.6.6-0
  • ros-kinetic-care-o-bot-robot: 0.6.6-0
  • ros-kinetic-care-o-bot-simulation: 0.6.6-0
  • ros-kinetic-cob-manipulation: 0.7.1-0
  • ros-kinetic-cob-pick-place-action: 0.7.1-0
  • ros-kinetic-cost-map: 0.3.3-0
  • ros-kinetic-cost-map-core: 0.3.3-0
  • ros-kinetic-cost-map-cv: 0.3.3-0
  • ros-kinetic-cost-map-demos: 0.3.3-0
  • ros-kinetic-cost-map-ros: 0.3.3-0
  • ros-kinetic-cost-map-visualisations: 0.3.3-0
  • ros-kinetic-darknet-ros-msgs: 1.1.2-0
  • ros-kinetic-loki-base-node: 0.2.1-0
  • ros-kinetic-loki-bringup: 0.0.1-0
  • ros-kinetic-loki-demos: 0.0.1-0
  • ros-kinetic-loki-description: 0.0.1-0
  • ros-kinetic-loki-nav: 0.0.1-0
  • ros-kinetic-loki-robot: 0.0.1-0
  • ros-kinetic-loki-teleop: 0.0.1-0
  • ros-kinetic-pcdfilter-pa: 1.2.0-0

Updated Packages [175]:

  • ros-kinetic-baldor: 0.1.1-0 -> 0.1.2-0
  • ros-kinetic-cob-3d-mapping-msgs: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-android: 0.1.3-0 -> 0.1.4-0
  • ros-kinetic-cob-android-msgs: 0.1.3-0 -> 0.1.4-0
  • ros-kinetic-cob-android-resource-server: 0.1.3-0 -> 0.1.4-0
  • ros-kinetic-cob-android-script-server: 0.1.3-0 -> 0.1.4-0
  • ros-kinetic-cob-android-settings: 0.1.3-0 -> 0.1.4-0
  • ros-kinetic-cob-base-drive-chain: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-base-velocity-smoother: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-bms-driver: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-bringup: 0.6.7-1 -> 0.6.8-0
  • ros-kinetic-cob-bringup-sim: 0.6.8-0 -> 0.6.9-0
  • ros-kinetic-cob-calibration-data: 0.6.7-0 -> 0.6.8-0
  • ros-kinetic-cob-cam3d-throttle: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-camera-sensors: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-canopen-motor: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-cartesian-controller: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-collision-monitor: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-collision-velocity-filter: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-command-gui: 0.6.6-0 -> 0.6.7-0
  • ros-kinetic-cob-command-tools: 0.6.6-0 -> 0.6.7-0
  • ros-kinetic-cob-common: 0.6.7-0 -> 0.6.8-0
  • ros-kinetic-cob-control: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-control-mode-adapter: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-control-msgs: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-dashboard: 0.6.6-0 -> 0.6.7-0
  • ros-kinetic-cob-default-env-config: 0.6.5-0 -> 0.6.6-0
  • ros-kinetic-cob-default-robot-behavior: 0.6.7-1 -> 0.6.8-0
  • ros-kinetic-cob-default-robot-config: 0.6.7-1 -> 0.6.8-0
  • ros-kinetic-cob-description: 0.6.7-0 -> 0.6.8-0
  • ros-kinetic-cob-docker-control: 0.6.6-0 -> 0.6.7-0
  • ros-kinetic-cob-driver: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-elmo-homing: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-environments: 0.6.5-0 -> 0.6.6-0
  • ros-kinetic-cob-extern: 0.6.11-0 -> 0.6.12-0
  • ros-kinetic-cob-footprint-observer: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-frame-tracker: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-gazebo: 0.6.8-0 -> 0.6.9-0
  • ros-kinetic-cob-gazebo-objects: 0.6.8-0 -> 0.6.9-0
  • ros-kinetic-cob-gazebo-plugins: 0.7.1-0 -> 0.7.2-0
  • ros-kinetic-cob-gazebo-ros-control: 0.7.1-0 -> 0.7.2-0
  • ros-kinetic-cob-gazebo-worlds: 0.6.8-0 -> 0.6.9-0
  • ros-kinetic-cob-generic-can: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-grasp-generation: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-hand: 0.6.2-0 -> 0.6.3-0
  • ros-kinetic-cob-hand-bridge: 0.6.2-0 -> 0.6.3-0
  • ros-kinetic-cob-hardware-config: 0.6.7-1 -> 0.6.8-0
  • ros-kinetic-cob-helper-tools: 0.6.6-0 -> 0.6.7-0
  • ros-kinetic-cob-image-flip: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-interactive-teleop: 0.6.6-0 -> 0.6.7-0
  • ros-kinetic-cob-light: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-linear-nav: 0.6.5-0 -> 0.6.6-0
  • ros-kinetic-cob-lookat-action: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-map-accessibility-analysis: 0.6.5-0 -> 0.6.6-0
  • ros-kinetic-cob-mapping-slam: 0.6.5-0 -> 0.6.6-0
  • ros-kinetic-cob-mimic: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-model-identifier: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-monitoring: 0.6.6-0 -> 0.6.7-0
  • ros-kinetic-cob-moveit-bringup: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-moveit-config: 0.6.7-1 -> 0.6.8-0
  • ros-kinetic-cob-moveit-interface: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-msgs: 0.6.7-0 -> 0.6.8-0
  • ros-kinetic-cob-navigation: 0.6.5-0 -> 0.6.6-0
  • ros-kinetic-cob-navigation-config: 0.6.5-0 -> 0.6.6-0
  • ros-kinetic-cob-navigation-global: 0.6.5-0 -> 0.6.6-0
  • ros-kinetic-cob-navigation-local: 0.6.5-0 -> 0.6.6-0
  • ros-kinetic-cob-navigation-slam: 0.6.5-0 -> 0.6.6-0
  • ros-kinetic-cob-object-detection-msgs: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-object-detection-visualizer: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-obstacle-distance: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-obstacle-distance-moveit: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-omni-drive-controller: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-perception-common: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-perception-msgs: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-phidget-em-state: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-phidget-power-state: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-phidgets: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-reflector-referencing: 0.6.6-0 -> 0.6.7-0
  • ros-kinetic-cob-relayboard: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-robots: 0.6.7-1 -> 0.6.8-0
  • ros-kinetic-cob-safety-controller: 0.6.6-0 -> 0.6.7-0
  • ros-kinetic-cob-scan-unifier: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-script-server: 0.6.6-0 -> 0.6.7-0
  • ros-kinetic-cob-sick-lms1xx: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-sick-s300: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-simulation: 0.6.8-0 -> 0.6.9-0
  • ros-kinetic-cob-sound: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-srvs: 0.6.7-0 -> 0.6.8-0
  • ros-kinetic-cob-substitute: 0.6.6-0 -> 0.6.7-0
  • ros-kinetic-cob-supported-robots: 0.6.7-0 -> 0.6.8-0
  • ros-kinetic-cob-teleop: 0.6.6-0 -> 0.6.7-0
  • ros-kinetic-cob-trajectory-controller: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-twist-controller: 0.7.0-0 -> 0.7.1-0
  • ros-kinetic-cob-undercarriage-ctrl: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-utilities: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-vision-utils: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cob-voltage-control: 0.6.10-0 -> 0.6.11-0
  • ros-kinetic-cost-map-msgs: 0.3.2-0 -> 0.3.3-0
  • ros-kinetic-dynamic-tf-publisher: 2.2.5-0 -> 2.2.6-0
  • ros-kinetic-generic-throttle: 0.6.6-0 -> 0.6.7-0
  • ros-kinetic-geometry2: 0.5.16-0 -> 0.5.17-0
  • ros-kinetic-image-view2: 2.2.5-0 -> 2.2.6-0
  • ros-kinetic-interactive-marker-tutorials: 0.10.1-0 -> 0.10.2-0
  • ros-kinetic-jsk-common: 2.2.5-0 -> 2.2.6-0
  • ros-kinetic-jsk-data: 2.2.5-0 -> 2.2.6-0
  • ros-kinetic-jsk-network-tools: 2.2.5-0 -> 2.2.6-0
  • ros-kinetic-jsk-tilt-laser: 2.2.5-0 -> 2.2.6-0
  • ros-kinetic-jsk-tools: 2.2.5-0 -> 2.2.6-0
  • ros-kinetic-jsk-topic-tools: 2.2.5-0 -> 2.2.6-0
  • ros-kinetic-kobuki: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-kobuki-auto-docking: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-kobuki-bumper2pc: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-kobuki-capabilities: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-kobuki-controller-tutorial: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-kobuki-description: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-kobuki-keyop: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-kobuki-node: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-kobuki-random-walker: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-kobuki-rapps: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-kobuki-safety-controller: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-kobuki-testsuite: 0.7.4-0 -> 0.7.5-0
  • ros-kinetic-libconcorde-tsp-solver: 0.6.11-0 -> 0.6.12-0
  • ros-kinetic-libdlib: 0.6.11-0 -> 0.6.12-0
  • ros-kinetic-libntcan: 0.6.11-0 -> 0.6.12-0
  • ros-kinetic-libpcan: 0.6.11-0 -> 0.6.12-0
  • ros-kinetic-libphidgets: 0.6.11-0 -> 0.6.12-0
  • ros-kinetic-libqsopt: 0.6.11-0 -> 0.6.12-0
  • ros-kinetic-librviz-tutorial: 0.10.1-0 -> 0.10.2-0
  • ros-kinetic-mavlink: 2017.12.12-0 -> 2018.1.1-0
  • ros-kinetic-moveit-visual-tools: 3.3.0-0 -> 3.4.0-0
  • ros-kinetic-multi-map-server: 2.2.5-0 -> 2.2.6-0
  • ros-kinetic-opengm: 0.6.11-0 -> 0.6.12-0
  • ros-kinetic-pose-cov-ops: 0.1.7-0 -> 0.2.0-0
  • ros-kinetic-raw-description: 0.6.7-0 -> 0.6.8-0
  • ros-kinetic-robot-localization: 2.4.0-0 -> 2.4.2-0
  • ros-kinetic-rviz: 1.12.14-0 -> 1.12.15-0
  • ros-kinetic-rviz-plugin-tutorials: 0.10.1-0 -> 0.10.2-0
  • ros-kinetic-rviz-python-tutorial: 0.10.1-0 -> 0.10.2-0
  • ros-kinetic-schunk-description: 0.6.9-0 -> 0.6.10-0
  • ros-kinetic-schunk-libm5api: 0.6.9-0 -> 0.6.10-0
  • ros-kinetic-schunk-modular-robotics: 0.6.9-0 -> 0.6.10-0
  • ros-kinetic-schunk-powercube-chain: 0.6.9-0 -> 0.6.10-0
  • ros-kinetic-schunk-sdh: 0.6.9-0 -> 0.6.10-0
  • ros-kinetic-schunk-simulated-tactile-sensors: 0.6.9-0 -> 0.6.10-0
  • ros-kinetic-service-tools: 0.6.6-0 -> 0.6.7-0
  • ros-kinetic-tf2: 0.5.16-0 -> 0.5.17-0
  • ros-kinetic-tf2-bullet: 0.5.16-0 -> 0.5.17-0
  • ros-kinetic-tf2-eigen: 0.5.16-0 -> 0.5.17-0
  • ros-kinetic-tf2-geometry-msgs: 0.5.16-0 -> 0.5.17-0
  • ros-kinetic-tf2-kdl: 0.5.16-0 -> 0.5.17-0
  • ros-kinetic-tf2-msgs: 0.5.16-0 -> 0.5.17-0
  • ros-kinetic-tf2-py: 0.5.16-0 -> 0.5.17-0
  • ros-kinetic-tf2-ros: 0.5.16-0 -> 0.5.17-0
  • ros-kinetic-tf2-sensor-msgs: 0.5.16-0 -> 0.5.17-0
  • ros-kinetic-tf2-tools: 0.5.16-0 -> 0.5.17-0
  • ros-kinetic-universal-robot: 1.2.0-0 -> 1.2.1-0
  • ros-kinetic-ur-bringup: 1.2.0-0 -> 1.2.1-0
  • ros-kinetic-ur-description: 1.2.0-0 -> 1.2.1-0
  • ros-kinetic-ur-driver: 1.2.0-0 -> 1.2.1-0
  • ros-kinetic-ur-gazebo: 1.2.0-0 -> 1.2.1-0
  • ros-kinetic-ur-kinematics: 1.2.0-0 -> 1.2.1-0
  • ros-kinetic-ur-msgs: 1.2.0-0 -> 1.2.1-0
  • ros-kinetic-ur10-moveit-config: 1.2.0-0 -> 1.2.1-0
  • ros-kinetic-ur3-moveit-config: 1.2.0-0 -> 1.2.1-0
  • ros-kinetic-ur5-moveit-config: 1.2.0-0 -> 1.2.1-0
  • ros-kinetic-virtual-force-publisher: 2.2.5-0 -> 2.2.6-0
  • ros-kinetic-visualization-marker-tutorials: 0.10.1-0 -> 0.10.2-0
  • ros-kinetic-visualization-tutorials: 0.10.1-0 -> 0.10.2-0
  • ros-kinetic-xpp: 1.0.3-0 -> 1.0.4-0
  • ros-kinetic-xpp-examples: 1.0.3-0 -> 1.0.4-0
  • ros-kinetic-xpp-hyq: 1.0.3-0 -> 1.0.4-0
  • ros-kinetic-xpp-msgs: 1.0.3-0 -> 1.0.4-0
  • ros-kinetic-xpp-quadrotor: 1.0.3-0 -> 1.0.4-0
  • ros-kinetic-xpp-states: 1.0.3-0 -> 1.0.4-0
  • ros-kinetic-xpp-vis: 1.0.3-0 -> 1.0.4-0

Removed Packages [2]:

  • ros-kinetic-cob-head-axis
  • ros-kinetic-cob-undercarriage-ctrl-node

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

  • Alexander Bubeck
  • Alexander W. Winkler
  • Benjamin Maidel
  • Bruno Brito
  • D. Hood
  • Daniel Stonier
  • Dave Coleman
  • Felipe Garcia Lopez
  • Felix Messmer
  • Felix Zeltner
  • Felx Messmer
  • Florian Weisshardt
  • Francisco Suarez-Ruiz
  • Jannik Abbenseth
  • Jorge Santos Simon
  • Jose-Luis Blanco-Claraco
  • Joshua Hampp
  • Kei Okada
  • Koji Terada
  • Marcus Liebhardt
  • Marko Bjelonic
  • Matthias Gruhler
  • Peter Weissig
  • Richard Bormann
  • Rohan Agrawal
  • Ryohei Ueda
  • Tom Moore
  • Tully Foote
  • Vincent Rabaud
  • Vladimir Ermakov
  • Wayne Gramlich
  • William Woodall
  • YoheiKakiuchi
  • Younghun Ju

Posts: 9

Participants: 6

Read full topic

by @tfoote Tully Foote on January 10, 2018 03:16 AM

New Packages for Lunar 2018-01-09

@marguedas wrote:

We’re happy to announce the availability of 9 new packages and 83 updated packages for ROS Lunar.
As always thank you to all the maintainers who are making these releases as well as all the contributors who have helped contribute to these releases. Full details are below.

Package Updates for lunar

Added Packages [9]:

  • ros-lunar-pcdfilter-pa: 1.2.0-0
  • ros-lunar-pcdfilter-pa-dbgsym: 1.2.0-0
  • ros-lunar-trac-ik: 1.4.8-0
  • ros-lunar-trac-ik-examples: 1.4.8-0
  • ros-lunar-trac-ik-examples-dbgsym: 1.4.8-0
  • ros-lunar-trac-ik-kinematics-plugin: 1.4.8-0
  • ros-lunar-trac-ik-kinematics-plugin-dbgsym: 1.4.8-0
  • ros-lunar-trac-ik-lib: 1.4.8-0
  • ros-lunar-trac-ik-lib-dbgsym: 1.4.8-0

Updated Packages [83]:

  • ros-lunar-geometry2: 0.5.16-0 -> 0.5.17-0
  • ros-lunar-interactive-marker-tutorials: 0.10.1-0 -> 0.10.2-0
  • ros-lunar-interactive-marker-tutorials-dbgsym: 0.10.1-0 -> 0.10.2-0
  • ros-lunar-librviz-tutorial: 0.10.1-0 -> 0.10.2-0
  • ros-lunar-librviz-tutorial-dbgsym: 0.10.1-0 -> 0.10.2-0
  • ros-lunar-mavlink: 2017.12.12-0 -> 2018.1.1-0
  • ros-lunar-moveit: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-commander: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-controller-manager-example: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-controller-manager-example-dbgsym: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-core: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-core-dbgsym: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-fake-controller-manager: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-fake-controller-manager-dbgsym: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-kinematics: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-kinematics-dbgsym: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-planners: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-planners-ompl: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-planners-ompl-dbgsym: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-plugins: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-benchmarks: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-benchmarks-dbgsym: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-control-interface: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-control-interface-dbgsym: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-manipulation: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-manipulation-dbgsym: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-move-group: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-move-group-dbgsym: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-perception: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-perception-dbgsym: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-planning: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-planning-dbgsym: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-planning-interface: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-planning-interface-dbgsym: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-robot-interaction: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-robot-interaction-dbgsym: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-visualization: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-visualization-dbgsym: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-warehouse: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-ros-warehouse-dbgsym: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-runtime: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-setup-assistant: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-setup-assistant-dbgsym: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-simple-controller-manager: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-moveit-simple-controller-manager-dbgsym: 0.9.10-0 -> 0.9.11-0
  • ros-lunar-robot-localization: 2.5.0-0 -> 2.5.1-1
  • ros-lunar-robot-localization-dbgsym: 2.5.0-0 -> 2.5.1-1
  • ros-lunar-rviz: 1.12.14-0 -> 1.12.15-0
  • ros-lunar-rviz-dbgsym: 1.12.14-0 -> 1.12.15-0
  • ros-lunar-rviz-plugin-tutorials: 0.10.1-0 -> 0.10.2-0
  • ros-lunar-rviz-plugin-tutorials-dbgsym: 0.10.1-0 -> 0.10.2-0
  • ros-lunar-rviz-python-tutorial: 0.10.1-0 -> 0.10.2-0
  • ros-lunar-tf2: 0.5.16-0 -> 0.5.17-0
  • ros-lunar-tf2-bullet: 0.5.16-0 -> 0.5.17-0
  • ros-lunar-tf2-dbgsym: 0.5.16-0 -> 0.5.17-0
  • ros-lunar-tf2-eigen: 0.5.16-0 -> 0.5.17-0
  • ros-lunar-tf2-geometry-msgs: 0.5.16-0 -> 0.5.17-0
  • ros-lunar-tf2-kdl: 0.5.16-0 -> 0.5.17-0
  • ros-lunar-tf2-msgs: 0.5.16-0 -> 0.5.17-0
  • ros-lunar-tf2-py: 0.5.16-0 -> 0.5.17-0
  • ros-lunar-tf2-py-dbgsym: 0.5.16-0 -> 0.5.17-0
  • ros-lunar-tf2-ros: 0.5.16-0 -> 0.5.17-0
  • ros-lunar-tf2-ros-dbgsym: 0.5.16-0 -> 0.5.17-0
  • ros-lunar-tf2-sensor-msgs: 0.5.16-0 -> 0.5.17-0
  • ros-lunar-tf2-tools: 0.5.16-0 -> 0.5.17-0
  • ros-lunar-visp: 3.0.1-4 -> 3.1.0-2
  • ros-lunar-visp-dbgsym: 3.0.1-4 -> 3.1.0-2
  • ros-lunar-visualization-marker-tutorials: 0.10.1-0 -> 0.10.2-0
  • ros-lunar-visualization-marker-tutorials-dbgsym: 0.10.1-0 -> 0.10.2-0
  • ros-lunar-visualization-tutorials: 0.10.1-0 -> 0.10.2-0
  • ros-lunar-xpp: 1.0.3-0 -> 1.0.4-0
  • ros-lunar-xpp-examples: 1.0.3-0 -> 1.0.4-0
  • ros-lunar-xpp-examples-dbgsym: 1.0.3-0 -> 1.0.4-0
  • ros-lunar-xpp-hyq: 1.0.3-0 -> 1.0.4-0
  • ros-lunar-xpp-hyq-dbgsym: 1.0.3-0 -> 1.0.4-0
  • ros-lunar-xpp-msgs: 1.0.3-0 -> 1.0.4-0
  • ros-lunar-xpp-quadrotor: 1.0.3-0 -> 1.0.4-0
  • ros-lunar-xpp-quadrotor-dbgsym: 1.0.3-0 -> 1.0.4-0
  • ros-lunar-xpp-states: 1.0.3-0 -> 1.0.4-0
  • ros-lunar-xpp-states-dbgsym: 1.0.3-0 -> 1.0.4-0
  • ros-lunar-xpp-vis: 1.0.3-0 -> 1.0.4-0
  • ros-lunar-xpp-vis-dbgsym: 1.0.3-0 -> 1.0.4-0

Removed Packages [0]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

  • Alexander W. Winkler
  • D. Hood
  • Dave Coleman
  • Fabien Spindler
  • Isaac I. Y. Saito
  • Jon Binney
  • Koji Terada
  • Mathias Lüdtke
  • Michael Ferguson
  • Michael Görner
  • Patrick Beeson
  • Peter Weissig
  • Tom Moore
  • Tully Foote
  • Vincent Rabaud
  • Vladimir Ermakov
  • William Woodall

Posts: 1

Participants: 1

Read full topic

by @marguedas Mikael Arguedas on January 10, 2018 12:10 AM

January 09, 2018
New Packages for Indigo 2018-01-09

@tfoote wrote:

We’re happy to anounce 6 new packages and 168 updated packages for Indigo.

Thanks as always to all the contributors and maintainers. The list of releases and maintainers is below.

Package Updates for indigo

Added Packages [6]:

  • ros-indigo-cost-map: 0.3.3-0
  • ros-indigo-cost-map-core: 0.3.3-0
  • ros-indigo-cost-map-cv: 0.3.3-0
  • ros-indigo-cost-map-demos: 0.3.3-0
  • ros-indigo-cost-map-ros: 0.3.3-0
  • ros-indigo-cost-map-visualisations: 0.3.3-0

Updated Packages [168]:

  • ros-indigo-baldor: 0.1.1-0 -> 0.1.2-0
  • ros-indigo-care-o-bot: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-care-o-bot-desktop: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-care-o-bot-robot: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-care-o-bot-simulation: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-3d-mapping-msgs: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-android: 0.1.3-0 -> 0.1.4-0
  • ros-indigo-cob-android-msgs: 0.1.3-0 -> 0.1.4-0
  • ros-indigo-cob-android-resource-server: 0.1.3-0 -> 0.1.4-0
  • ros-indigo-cob-android-script-server: 0.1.3-0 -> 0.1.4-0
  • ros-indigo-cob-android-settings: 0.1.3-0 -> 0.1.4-0
  • ros-indigo-cob-base-drive-chain: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-base-velocity-smoother: 0.6.15-0 -> 0.6.16-0
  • ros-indigo-cob-bms-driver: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-bringup: 0.6.7-1 -> 0.6.8-0
  • ros-indigo-cob-bringup-sim: 0.6.8-0 -> 0.6.9-0
  • ros-indigo-cob-calibration-data: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-cob-cam3d-throttle: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-camera-sensors: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-canopen-motor: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-cartesian-controller: 0.6.15-0 -> 0.6.16-0
  • ros-indigo-cob-collision-monitor: 0.6.5-1 -> 0.6.6-1
  • ros-indigo-cob-collision-velocity-filter: 0.6.15-0 -> 0.6.16-0
  • ros-indigo-cob-command-gui: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-cob-command-tools: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-cob-common: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-cob-control: 0.6.15-0 -> 0.6.16-0
  • ros-indigo-cob-control-mode-adapter: 0.6.15-0 -> 0.6.16-0
  • ros-indigo-cob-control-msgs: 0.6.15-0 -> 0.6.16-0
  • ros-indigo-cob-dashboard: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-cob-default-env-config: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-default-robot-behavior: 0.6.7-1 -> 0.6.8-0
  • ros-indigo-cob-default-robot-config: 0.6.7-1 -> 0.6.8-0
  • ros-indigo-cob-description: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-cob-docker-control: 0.6.6-0 -> 0.6.7-1
  • ros-indigo-cob-driver: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-elmo-homing: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-environments: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-extern: 0.6.11-0 -> 0.6.12-0
  • ros-indigo-cob-footprint-observer: 0.6.15-0 -> 0.6.16-0
  • ros-indigo-cob-frame-tracker: 0.6.15-0 -> 0.6.16-0
  • ros-indigo-cob-gazebo: 0.6.8-0 -> 0.6.9-0
  • ros-indigo-cob-gazebo-objects: 0.6.8-0 -> 0.6.9-0
  • ros-indigo-cob-gazebo-plugins: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-cob-gazebo-ros-control: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-cob-gazebo-worlds: 0.6.8-0 -> 0.6.9-0
  • ros-indigo-cob-generic-can: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-grasp-generation: 0.6.5-1 -> 0.6.6-1
  • ros-indigo-cob-hand: 0.6.2-0 -> 0.6.3-0
  • ros-indigo-cob-hand-bridge: 0.6.2-0 -> 0.6.3-0
  • ros-indigo-cob-hardware-config: 0.6.7-1 -> 0.6.8-0
  • ros-indigo-cob-helper-tools: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-cob-image-flip: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-interactive-teleop: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-cob-kinematics: 0.6.5-1 -> 0.6.6-1
  • ros-indigo-cob-light: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-linear-nav: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-lookat-action: 0.6.5-1 -> 0.6.6-1
  • ros-indigo-cob-manipulation: 0.6.5-1 -> 0.6.6-1
  • ros-indigo-cob-map-accessibility-analysis: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-mapping-slam: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-mimic: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-model-identifier: 0.6.15-0 -> 0.6.16-0
  • ros-indigo-cob-monitoring: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-cob-moveit-bringup: 0.6.5-1 -> 0.6.6-1
  • ros-indigo-cob-moveit-config: 0.6.7-1 -> 0.6.8-0
  • ros-indigo-cob-moveit-interface: 0.6.5-1 -> 0.6.6-1
  • ros-indigo-cob-msgs: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-cob-navigation: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-navigation-config: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-navigation-global: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-navigation-local: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-navigation-slam: 0.6.5-0 -> 0.6.6-0
  • ros-indigo-cob-object-detection-msgs: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-object-detection-visualizer: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-obstacle-distance: 0.6.15-0 -> 0.6.16-0
  • ros-indigo-cob-obstacle-distance-moveit: 0.6.5-1 -> 0.6.6-1
  • ros-indigo-cob-omni-drive-controller: 0.6.15-0 -> 0.6.16-0
  • ros-indigo-cob-perception-common: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-perception-msgs: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-phidget-em-state: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-phidget-power-state: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-phidgets: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-pick-place-action: 0.6.5-1 -> 0.6.6-1
  • ros-indigo-cob-reflector-referencing: 0.6.6-0 -> 0.6.7-1
  • ros-indigo-cob-relayboard: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-robots: 0.6.7-1 -> 0.6.8-0
  • ros-indigo-cob-safety-controller: 0.6.6-0 -> 0.6.7-1
  • ros-indigo-cob-scan-unifier: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-script-server: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-cob-sick-lms1xx: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-sick-s300: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-simulation: 0.6.8-0 -> 0.6.9-0
  • ros-indigo-cob-sound: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-srvs: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-cob-substitute: 0.6.6-0 -> 0.6.7-1
  • ros-indigo-cob-supported-robots: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-cob-teleop: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-cob-trajectory-controller: 0.6.15-0 -> 0.6.16-0
  • ros-indigo-cob-twist-controller: 0.6.15-0 -> 0.6.16-0
  • ros-indigo-cob-undercarriage-ctrl: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-utilities: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-vision-utils: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cob-voltage-control: 0.6.10-0 -> 0.6.11-0
  • ros-indigo-cost-map-msgs: 0.3.2-0 -> 0.3.3-0
  • ros-indigo-dynamic-tf-publisher: 2.2.5-0 -> 2.2.6-0
  • ros-indigo-gazebo-grasp-plugin: 1.0.1-0 -> 1.0.2-0
  • ros-indigo-gazebo-state-plugins: 1.0.1-0 -> 1.0.2-0
  • ros-indigo-gazebo-test-tools: 1.0.1-0 -> 1.0.2-0
  • ros-indigo-gazebo-world-plugin-loader: 1.0.1-0 -> 1.0.2-0
  • ros-indigo-generic-throttle: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-grasp-planning-graspit: 1.1.2-0 -> 1.2.0-0
  • ros-indigo-grasp-planning-graspit-msgs: 1.1.2-0 -> 1.2.0-0
  • ros-indigo-grasp-planning-graspit-ros: 1.1.2-0 -> 1.2.0-0
  • ros-indigo-graspit-tools: 1.1.2-0 -> 1.2.0-0
  • ros-indigo-image-view2: 2.2.5-0 -> 2.2.6-0
  • ros-indigo-jaco-graspit-sample: 1.1.2-0 -> 1.2.0-0
  • ros-indigo-jsk-common: 2.2.5-0 -> 2.2.6-0
  • ros-indigo-jsk-data: 2.2.5-0 -> 2.2.6-0
  • ros-indigo-jsk-network-tools: 2.2.5-0 -> 2.2.6-0
  • ros-indigo-jsk-tilt-laser: 2.2.5-0 -> 2.2.6-0
  • ros-indigo-jsk-tools: 2.2.5-0 -> 2.2.6-0
  • ros-indigo-jsk-topic-tools: 2.2.5-0 -> 2.2.6-0
  • ros-indigo-libconcorde-tsp-solver: 0.6.11-0 -> 0.6.12-0
  • ros-indigo-libdlib: 0.6.11-0 -> 0.6.12-0
  • ros-indigo-libntcan: 0.6.11-0 -> 0.6.12-0
  • ros-indigo-libpcan: 0.6.11-0 -> 0.6.12-0
  • ros-indigo-libphidgets: 0.6.11-0 -> 0.6.12-0
  • ros-indigo-libqsopt: 0.6.11-0 -> 0.6.12-0
  • ros-indigo-moveit-controller-multidof: 1.0.0-0 -> 1.0.1-0
  • ros-indigo-moveit-object-handling: 1.0.0-0 -> 1.0.1-0
  • ros-indigo-moveit-planning-helper: 1.0.0-0 -> 1.0.1-0
  • ros-indigo-multi-map-server: 2.2.5-0 -> 2.2.6-0
  • ros-indigo-opengm: 0.6.11-0 -> 0.6.12-0
  • ros-indigo-pcdfilter-pa: 1.1.0-0 -> 1.2.0-0
  • ros-indigo-raw-description: 0.6.7-0 -> 0.6.8-0
  • ros-indigo-schunk-description: 0.6.9-0 -> 0.6.10-0
  • ros-indigo-schunk-libm5api: 0.6.9-0 -> 0.6.10-0
  • ros-indigo-schunk-modular-robotics: 0.6.9-0 -> 0.6.10-0
  • ros-indigo-schunk-powercube-chain: 0.6.9-0 -> 0.6.10-0
  • ros-indigo-schunk-sdh: 0.6.9-0 -> 0.6.10-0
  • ros-indigo-schunk-simulated-tactile-sensors: 0.6.9-0 -> 0.6.10-0
  • ros-indigo-service-tools: 0.6.6-0 -> 0.6.7-0
  • ros-indigo-universal-robot: 1.1.10-1 -> 1.1.11-0
  • ros-indigo-ur-bringup: 1.1.10-1 -> 1.1.11-0
  • ros-indigo-ur-description: 1.1.10-1 -> 1.1.11-0
  • ros-indigo-ur-driver: 1.1.10-1 -> 1.1.11-0
  • ros-indigo-ur-gazebo: 1.1.10-1 -> 1.1.11-0
  • ros-indigo-ur-kinematics: 1.1.10-1 -> 1.1.11-0
  • ros-indigo-ur-msgs: 1.1.10-1 -> 1.1.11-0
  • ros-indigo-ur10-moveit-config: 1.1.10-1 -> 1.1.11-0
  • ros-indigo-ur3-moveit-config: 1.1.10-1 -> 1.1.11-0
  • ros-indigo-ur5-moveit-config: 1.1.10-1 -> 1.1.11-0
  • ros-indigo-urdf-processing-tools: 1.0.1-0 -> 1.0.2-0
  • ros-indigo-urdf-transform: 1.0.1-0 -> 1.0.2-0
  • ros-indigo-urdf-traverser: 1.0.1-0 -> 1.0.2-0
  • ros-indigo-urdf-viewer: 1.0.1-0 -> 1.0.2-0
  • ros-indigo-urdf2graspit: 1.1.2-0 -> 1.2.0-0
  • ros-indigo-urdf2inventor: 1.0.1-0 -> 1.0.2-0
  • ros-indigo-virtual-force-publisher: 2.2.5-0 -> 2.2.6-0
  • ros-indigo-visp: 3.0.1-1 -> 3.1.0-2
  • ros-indigo-xpp: 1.0.3-0 -> 1.0.4-0
  • ros-indigo-xpp-examples: 1.0.3-0 -> 1.0.4-0
  • ros-indigo-xpp-hyq: 1.0.3-0 -> 1.0.4-0
  • ros-indigo-xpp-msgs: 1.0.3-0 -> 1.0.4-0
  • ros-indigo-xpp-quadrotor: 1.0.3-0 -> 1.0.4-0
  • ros-indigo-xpp-states: 1.0.3-0 -> 1.0.4-0
  • ros-indigo-xpp-vis: 1.0.3-0 -> 1.0.4-0

Removed Packages [2]:

  • ros-indigo-cob-head-axis
  • ros-indigo-cob-undercarriage-ctrl-node

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

  • Alexander Bubeck
  • Alexander W. Winkler
  • Benjamin Maidel
  • Bruno Brito
  • Daniel Stonier
  • Fabien Spindler
  • Felipe Garcia Lopez
  • Felix Messmer
  • Felix Zeltner
  • Felx Messmer
  • Florian Weisshardt
  • Francisco Suarez-Ruiz
  • Jannik Abbenseth
  • Jennifer Buehler
  • Joshua Hampp
  • Kei Okada
  • Matthias Gruhler
  • Peter Weissig
  • Richard Bormann
  • Ryohei Ueda
  • YoheiKakiuchi

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on January 09, 2018 10:52 PM

January 08, 2018
Announcing ROS#

This is a guest blog post by Martin Bischoff on behalf of his employer Siemens AG. Thanks to Martin for the update, and to Siemens for its generous support to the ROS-Industrial Consortium!


We are happy to announce that we published ROS# on github.com/siemens/ros-sharp!

RosSharpLogo.png  

...is a set of software libraries and tools in C# for communicating with ROS from .NET applications, in particular Unity.

ROS# consists of:

  • RosBridgeClient, a .NET API to ROS using rosbridge_suite on the ROS side.
  • UrdfImporter, a URDF file parser for .NET applications.
  • RosSharp.unitypackage, a Unity Asset package providing Unity-specific extensions to RosBridgeClient and UrdfImporter.

ROS# helps you to:

  • Communicate with ROS from within your Windows app: subscribe and publish topics, call and advertize services, set and get parameters and use all features provided by rosbridge_suite.
  CodeExample.png  
  • Import your robot's URDF model as a Gameobject in Unity3D. Import the data either directly from the ROS system using the robot_description service or via a URDF file that you copied into your Unity Asset folder.

(click on the images for videos)

  UrdfImport.png  
  • Control your real Robot via Unity3D.
  Teleoperation.png  
  • Visualize your Robot's actual state and sensor Data in Unity3D.
  RVizUnity.png  
  • Simulate your robot in Unity3D with the data provided by the URDF and without using a connection to ROS. Beside visual components as meshes and textures, also Joint parameters and masses, CoMs, Inertia and Collider specifications of Rigidbodies are imported.
  Simulation.png  
  • And much more! ROS# is useful for a wide variety of applications. Think about Machine Learning, Human-Machine Interaction, Tele-Engineering, Virtual Prototyping, Robot Fleet Operation, Gaming and Entertainment!

Got Interested?

Please do not hesitate to try it out yourself and to get in touch with us! We are very interested in your feedback, applications, improvement suggestions, and contributions!

ROS# Development Team (ros-sharp.ct@siemens.com), Siemens AG, Corporate Technology, 2017

by Mirko Bordignon on January 08, 2018 01:00 PM

Matching RGB image with Point Cloud

@Rakshith_Madhavan wrote:

I have two different sensors,one for capturing an RGB image (from an Intel RealSense SR300), and one for giving me a 3D Point Cloud(from a DUO MC stereo camera). How can I integrate the two? Is it possible to match the pixels of the RGB image to the points in the Point Cloud? I need a separate depth sensor because the SR300 does not work in the presence of ambient light.

Is there any method for this? Can it be done while retaining accuracy?

Posts: 1

Participants: 1

Read full topic

by @Rakshith_Madhavan Rakshith Madhavan on January 08, 2018 09:16 AM

January 05, 2018
Fix released: rviz 1.12.14 not displaying markers etc with invalid quaternions

@dhood wrote:

There was a break in behaviour in rviz 1.12.14 released into kinetic and lunar where ROS messages containing unnormalised or uninitialised quaternions were rejected. This caused a number of plugins to not show visuals e.g. markers.

rviz 1.12.15 allows messages with invalid quaternions to be processed again. Unormalised quaternions will generate a console warning.

Publishers of invalid quaternions should be updated to publish valid quaternions, as rviz will reject invalid quaternions 1 year from now. See https://github.com/ros-visualization/rviz/pull/1179 for the discussion. Add log4j.logger.ros.rviz.quaternions=DEBUG to $ROS_ROOT/config/rosconsole.config to see more detailed messages.

rviz 1.12.15 has not yet been synced into the main ros apt repo but will be available from the testing repo once the distro’s rebuild has completed. Check http://repositories.ros.org/status_page/ros_kinetic_default.html?q=rviz (and lunar equivalent) to know when rviz 1.12.15 is released into the main repo. (@tfoote @marguedas as this breaks users, if it’s appropriate to sync earlier than normal that would be appreciated).

Posts: 4

Participants: 4

Read full topic

by @dhood dhood on January 05, 2018 11:12 PM

January 04, 2018
LiDAR & 3D camera drivers from SICK

@SICK-WestCoast wrote:

SICK’s git repo is growing. See the new sick_scan for drivers for the TiM551, TiM561, and TiM571, plus the new 4-layer MRS1000 LiDAR. Check it out: https://github.com/SICKAG.

Posts: 1

Participants: 1

Read full topic

by @SICK-WestCoast Andrew Etherington on January 04, 2018 07:48 PM

Move_Base theory of operation

@pitosalas wrote:

I’m digging into navigation and experimenting with move_base. There are lots of good tutorials and I’ve done some of them. Also there’s some documentation in the wiki, including a neat diagram. However I am looking for a little deeper explanation of the way the collection of libraries and apis actually work. I’ve downloaded the code but that seems to be a level too deep. On the other hand the wiki and tutorials are very recipe driven. (Naturally I’ve googled.)

Can you point me to some resource: web page, journal articles, blog post or anything? Thanks!

Posts: 3

Participants: 2

Read full topic

by @pitosalas Pito Salas on January 04, 2018 02:05 AM

January 03, 2018
Intelligent Part Reconstruction

It has long been a challenge in industry to image, or leverage non-contact sensors, to generate reconstructions of highly spectral or featureless surfaces. Shiny parts, dark surfaces, occlusion, and limited resolution all corrupt single-shot scanning for first-look robotic solution imaging or scanning systems. A whole new class of applications can be efficiently addressed if there were an efficient way to reconstruct surfaces to enable reliable trajectories for subsequent processing.

In the context of autonomous processing of parts, the mesh is the “stitching” together of points generated by a 3D depth camera that creates a “point cloud.” Algorithms are then applied to derive surfaces from the point cloud, as well as edges, and even detect “engineered features,” such as drilled holes. The process deteriorates when there is a lack of “points” returned to the sensor (i.e. sparse data). Smooth surfaces also make it difficult to “stitch” images together or organize points in a way that enables mesh creation. As in the example below, there is insufficient data to create the mesh over the full scanned surface. There are techniques to mitigate this phenomenon, such as “flat” coating surfaces, but these can be cumbersome, costly, and inefficient.

Spectral Sample Part.JPG

In recent years, academic research in the field of on-line surface reconstruction has built on the Truncated Signed Distance Field (TSDF). The Kinect Fusion TSDF technique pioneered by Microsoft Research involves probabilistically fusing many organized depth images from 3D cameras into a voxelized distance field, to estimate an average, implicit surface. The scanner is manipulated by hand, and each image’s pose is registered relative to the previous images by way of the Iterative Closest Point (ICP) algorithm. While this technique shows promise in fusing partial observations of difficult to scan objects, it suffers from the practical constraint that it must scan very quickly to accurately estimate scanner motion, and the surface being scanned must have sufficient features to enable tracking.

The TSDF-based reconstruction process only produces good results if the sensor gets good views of as much of the surface as possible. This is a fairly intuitive task for a human, since we can look at the partially-reconstructed surface, recognize which areas are incomplete, and move the camera to compensate.

It’s much more difficult for a robot to make these decisions. One way to approach this problem is to track which areas around the surface have and haven’t been seen by the camera. The robot can take an initial measurement, see which areas haven’t been viewed, and pick a new view that looks at these unknown regions. This lets the robot discover that it doesn’t have information about the back side of a wall and decide that it needs to move the camera to the opposite side of the work area to look at the obscured surface.

In this implementation, views around the volume are randomly generated within a range of angles and distances. Rays are cast corresponding to the camera’s field of view from each pose and count how many of these rays hit unknown voxels. The next best view is the one that hits the most unknowns, and the robot tries to move to this view to explore more of the part.

NBV.JPG

The results have been very promising. The performance of the combination of TSDF + Next Best View (NBV) within this work have resolved a number of the issues encountered in a prior Robotic Blending Focused Technical Project (FTP). The first of two primary metrics was: mesh completeness, where a complete part was created, where before insufficient returns left “holes” in the data. An example of a before-and-after can be seen below.

Al Bracket.JPG

The second metric: to generate trajectories within the compliance of the tool leveraged in the robotic blending work. In this case, that was approximately 2 cm. You can see in the video on this aluminum sample that the tool follows the arc and does not bottom out, or lift off of the part. While somewhat qualitative, operating within this compliance range was impossible before the development of this TSDF + NBV implementation.

Future work seeks to refine this tool set into a more cohesive set of packages that can then be contributed to the ROS-Industrial community. In the meantime, further testing to understand the limitations of the current implementation, and subsequent performance improvements, are slated in conjunction with other process development initiatives.

Check back here for more information and/or updates, or feel free to inquire directly about this capability: matt.robinson <at> swri.org.

by Matthew Robinson on January 03, 2018 05:11 PM

December 30, 2017
Journals for ROS contribution

@MerAARIZOU wrote:

Hello everyone!
during this year I was working on optimizing the bandwidth consumption during a web-based remote manipulation in ROS with tf2_web_republisher. The internet connection is limited here in Algeria and we couldn’t perform a smooth remote manipulation on a robot, so the idea was to reduce the amount of TF sent from the manipulation server (remote site) to web client. I was able o reduce over 70% of bandwidth consumption with the same effective result as by tf2_web_republisher. I experimented my algorithm on pioneer mobile robot P3-DX and on the 07Dof robot arm Cyton_gamma_300. Now I intend to publish my results on an international review, the problem is I can not find a journal that accepts these kind of work for reviews, it’s either: “there’s no reviewer for ROS development” or “my work is not a general contribution in robotics” or “a contribution on an open source tool is not useful”! I would like to find an internation jounral indexed on scopus (or ISI thomson) which is not Open access and has more than five years, I know this is nonsense, but these are the criteria of my faculty. Can anyone help me please. I’ll be grateful to all of you, thank you in advance!

Posts: 6

Participants: 3

Read full topic

by @MerAARIZOU Meriem Aarizou on December 30, 2017 08:17 PM

December 28, 2017
Promote ROS2 on GitHub via "awesome" list

@fkromer wrote:

To get people know about, probably interested and involved in ROS2 I created a GitHub repo which lists resources about ROS2 and a PR for adding it to the well-known GitHub repo “awesome” (almost 75k stars). Please star the repo and “thumb up” the PR to get it added.

Posts: 4

Participants: 3

Read full topic

by @fkromer on December 28, 2017 05:46 PM

December 27, 2017
New Packages for Kinetic 2017-12-27

@tfoote wrote:

We’re happy to announce 10 new packages and 125 updated packages for Kinetic.

Thank you to all the maintainers and contributors who helped make this possible! Full details are below.

Package Updates for kinetic

Added Packages [10]:

  • ros-kinetic-camera1394: 1.10.1-0
  • ros-kinetic-four-wheel-steering-controller: 0.13.2-0
  • ros-kinetic-handeye: 0.1.0-0
  • ros-kinetic-rdl: 0.9.5-0
  • ros-kinetic-rdl-benchmark: 0.9.5-0
  • ros-kinetic-rdl-cmake: 0.9.5-0
  • ros-kinetic-rdl-dynamics: 0.9.5-0
  • ros-kinetic-rdl-urdfreader: 0.9.5-0
  • ros-kinetic-rtt-control-msgs: 0.1.1-0
  • ros-kinetic-rtt-controller-manager-msgs: 0.1.1-0

Updated Packages [125]:

  • ros-kinetic-bcap-core: 3.0.1-0 -> 3.0.2-1
  • ros-kinetic-bcap-service: 3.0.1-0 -> 3.0.2-1
  • ros-kinetic-bcap-service-test: 3.0.1-0 -> 3.0.2-1
  • ros-kinetic-combined-robot-hw: 0.12.0-0 -> 0.13.0-0
  • ros-kinetic-combined-robot-hw-tests: 0.12.0-0 -> 0.13.0-0
  • ros-kinetic-controller-interface: 0.12.0-0 -> 0.13.0-0
  • ros-kinetic-controller-manager: 0.12.0-0 -> 0.13.0-0
  • ros-kinetic-controller-manager-msgs: 0.12.0-0 -> 0.13.0-0
  • ros-kinetic-controller-manager-tests: 0.12.0-0 -> 0.13.0-0
  • ros-kinetic-denso-robot-bringup: 3.0.1-0 -> 3.0.2-1
  • ros-kinetic-denso-robot-control: 3.0.1-0 -> 3.0.2-1
  • ros-kinetic-denso-robot-core: 3.0.1-0 -> 3.0.2-1
  • ros-kinetic-denso-robot-core-test: 3.0.1-0 -> 3.0.2-1
  • ros-kinetic-denso-robot-descriptions: 3.0.1-0 -> 3.0.2-1
  • ros-kinetic-denso-robot-gazebo: 3.0.1-0 -> 3.0.2-1
  • ros-kinetic-denso-robot-moveit-config: 3.0.1-0 -> 3.0.2-1
  • ros-kinetic-denso-robot-ros: 3.0.1-0 -> 3.0.2-1
  • ros-kinetic-diff-drive-controller: 0.13.1-0 -> 0.13.2-0
  • ros-kinetic-effort-controllers: 0.13.1-0 -> 0.13.2-0
  • ros-kinetic-explore-lite: 2.1.0-0 -> 2.1.1-0
  • ros-kinetic-force-torque-sensor-controller: 0.13.1-0 -> 0.13.2-0
  • ros-kinetic-forward-command-controller: 0.13.1-0 -> 0.13.2-0
  • ros-kinetic-gazebo-dev: 2.5.13-0 -> 2.5.14-1
  • ros-kinetic-gazebo-msgs: 2.5.13-0 -> 2.5.14-1
  • ros-kinetic-gazebo-plugins: 2.5.13-0 -> 2.5.14-1
  • ros-kinetic-gazebo-ros: 2.5.13-0 -> 2.5.14-1
  • ros-kinetic-gazebo-ros-control: 2.5.13-0 -> 2.5.14-1
  • ros-kinetic-gazebo-ros-pkgs: 2.5.13-0 -> 2.5.14-1
  • ros-kinetic-gripper-action-controller: 0.13.1-0 -> 0.13.2-0
  • ros-kinetic-hardware-interface: 0.12.0-0 -> 0.13.0-0
  • ros-kinetic-hrpsys-ros-bridge: 1.4.0-1 -> 1.4.2-0
  • ros-kinetic-hrpsys-tools: 1.4.0-1 -> 1.4.2-0
  • ros-kinetic-imu-sensor-controller: 0.13.1-0 -> 0.13.2-0
  • ros-kinetic-joint-limits-interface: 0.12.0-0 -> 0.13.0-0
  • ros-kinetic-joint-state-controller: 0.13.1-0 -> 0.13.2-0
  • ros-kinetic-joint-trajectory-controller: 0.13.1-0 -> 0.13.2-0
  • ros-kinetic-libmavconn: 0.21.5-0 -> 0.22.0-0
  • ros-kinetic-libmongocxx-ros: 0.3.6-0 -> 0.3.7-0
  • ros-kinetic-magni-bringup: 0.2.1-0 -> 0.2.4-0
  • ros-kinetic-magni-demos: 0.2.1-0 -> 0.2.4-0
  • ros-kinetic-magni-description: 0.2.1-0 -> 0.2.4-0
  • ros-kinetic-magni-nav: 0.2.1-0 -> 0.2.4-0
  • ros-kinetic-magni-robot: 0.2.1-0 -> 0.2.4-0
  • ros-kinetic-magni-teleop: 0.2.1-0 -> 0.2.4-0
  • ros-kinetic-marti-data-structures: 1.2.0-0 -> 2.0.0-0
  • ros-kinetic-mavlink: 2017.12.1-0 -> 2017.12.12-0
  • ros-kinetic-mavros: 0.21.5-0 -> 0.22.0-0
  • ros-kinetic-mavros-extras: 0.21.5-0 -> 0.22.0-0
  • ros-kinetic-mavros-msgs: 0.21.5-0 -> 0.22.0-0
  • ros-kinetic-micros-swarm-framework: 0.0.15-2 -> 0.0.17-2
  • ros-kinetic-mongodb-log: 0.3.6-0 -> 0.3.7-0
  • ros-kinetic-mongodb-store: 0.3.6-0 -> 0.3.7-0
  • ros-kinetic-mongodb-store-msgs: 0.3.6-0 -> 0.3.7-0
  • ros-kinetic-moveit: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-commander: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-controller-manager-example: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-core: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-fake-controller-manager: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-kinematics: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-planners: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-planners-ompl: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-plugins: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-ros: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-ros-benchmarks: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-ros-control-interface: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-ros-manipulation: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-ros-move-group: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-ros-perception: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-ros-planning: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-ros-planning-interface: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-ros-robot-interaction: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-ros-visualization: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-ros-warehouse: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-runtime: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-setup-assistant: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-moveit-simple-controller-manager: 0.9.10-0 -> 0.9.11-0
  • ros-kinetic-multirobot-map-merge: 2.1.0-0 -> 2.1.1-0
  • ros-kinetic-nextage-calibration: 0.8.2-0 -> 0.8.3-0
  • ros-kinetic-nextage-description: 0.8.2-0 -> 0.8.3-0
  • ros-kinetic-nextage-gazebo: 0.8.2-0 -> 0.8.3-0
  • ros-kinetic-nextage-ik-plugin: 0.8.2-0 -> 0.8.3-0
  • ros-kinetic-nextage-moveit-config: 0.8.2-0 -> 0.8.3-0
  • ros-kinetic-nextage-ros-bridge: 0.8.2-0 -> 0.8.3-0
  • ros-kinetic-openrtm-ros-bridge: 1.4.0-1 -> 1.4.2-0
  • ros-kinetic-openrtm-tools: 1.4.0-1 -> 1.4.2-0
  • ros-kinetic-parameter-pa: 1.1.0-0 -> 1.2.1-0
  • ros-kinetic-position-controllers: 0.13.1-0 -> 0.13.2-0
  • ros-kinetic-realsense-camera: 1.8.0-0 -> 1.8.1-1
  • ros-kinetic-ros-control: 0.12.0-0 -> 0.13.0-0
  • ros-kinetic-ros-controllers: 0.13.1-0 -> 0.13.2-0
  • ros-kinetic-rosnode-rtc: 1.4.0-1 -> 1.4.2-0
  • ros-kinetic-rqt-controller-manager: 0.12.0-0 -> 0.13.0-0
  • ros-kinetic-rqt-joint-trajectory-controller: 0.13.1-0 -> 0.13.2-0
  • ros-kinetic-rtmbuild: 1.4.0-1 -> 1.4.2-0
  • ros-kinetic-rtmros-common: 1.4.0-1 -> 1.4.2-0
  • ros-kinetic-rtmros-nextage: 0.8.2-0 -> 0.8.3-0
  • ros-kinetic-rviz: 1.12.13-0 -> 1.12.14-0
  • ros-kinetic-rviz-visual-tools: 3.4.1-0 -> 3.5.1-3
  • ros-kinetic-sick-tim: 0.0.10-0 -> 0.0.11-0
  • ros-kinetic-swri-console-util: 1.2.0-0 -> 2.0.0-0
  • ros-kinetic-swri-geometry-util: 1.2.0-0 -> 2.0.0-0
  • ros-kinetic-swri-image-util: 1.2.0-0 -> 2.0.0-0
  • ros-kinetic-swri-math-util: 1.2.0-0 -> 2.0.0-0
  • ros-kinetic-swri-nodelet: 1.2.0-0 -> 2.0.0-0
  • ros-kinetic-swri-opencv-util: 1.2.0-0 -> 2.0.0-0
  • ros-kinetic-swri-prefix-tools: 1.2.0-0 -> 2.0.0-0
  • ros-kinetic-swri-roscpp: 1.2.0-0 -> 2.0.0-0
  • ros-kinetic-swri-rospy: 1.2.0-0 -> 2.0.0-0
  • ros-kinetic-swri-route-util: 1.2.0-0 -> 2.0.0-0
  • ros-kinetic-swri-serial-util: 1.2.0-0 -> 2.0.0-0
  • ros-kinetic-swri-string-util: 1.2.0-0 -> 2.0.0-0
  • ros-kinetic-swri-system-util: 1.2.0-0 -> 2.0.0-0
  • ros-kinetic-swri-transform-util: 1.2.0-0 -> 2.0.0-0
  • ros-kinetic-swri-yaml-util: 1.2.0-0 -> 2.0.0-0
  • ros-kinetic-teraranger-array: 1.2.1-0 -> 1.2.3-0
  • ros-kinetic-teraranger-array-converter: 1.1.0-0 -> 1.1.1-0
  • ros-kinetic-test-mavros: 0.21.5-0 -> 0.22.0-0
  • ros-kinetic-trac-ik: 1.4.6-0 -> 1.4.7-0
  • ros-kinetic-trac-ik-examples: 1.4.6-0 -> 1.4.7-0
  • ros-kinetic-trac-ik-kinematics-plugin: 1.4.6-0 -> 1.4.7-0
  • ros-kinetic-trac-ik-lib: 1.4.6-0 -> 1.4.7-0
  • ros-kinetic-transmission-interface: 0.12.0-0 -> 0.13.0-0
  • ros-kinetic-velocity-controllers: 0.13.1-0 -> 0.13.2-0
  • ros-kinetic-visp: 3.0.1-6 -> 3.1.0-2
  • ros-kinetic-zbar-ros: 0.0.5-0 -> 0.1.0-0

Removed Packages [0]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

  • Adolfo Rodriguez Tsouroukdissian
  • Bence Magyar
  • D. Hood
  • DENSO WAVE INCORPORATED
  • Dave Coleman
  • Ed Venator
  • Elliot Johnson
  • Fabien Spindler
  • Francisco Suarez-Ruiz
  • IK Fast Plugin Creater
  • Isaac I. Y. Saito
  • Jack O’Quin
  • Jiri Horner
  • John Hsu
  • Jon Binney
  • Jose Luis Rivero
  • Kei Okada
  • Kelsey Hawkins
  • Kris Kozak
  • Marc Alban
  • Marc Hanheide
  • Martin Günther
  • Mathias Lüdtke
  • Michael Ferguson
  • Michael Görner
  • MoveIt Setup Assistant
  • Nick Hawes
  • Orocos Developers
  • Patrick Beeson
  • Paul Bovbel
  • Peter Weissig
  • Pierre-Louis Kabaradjian
  • Rohan Agrawal
  • Sachin Chitta
  • Sergey Dorodnicov
  • TORK
  • Toni Oliver
  • Vincent Rousseau
  • Vladimir Ermakov
  • Xuefeng Chang
  • jordan

Sync preparations were conduced here: Preparing for Kinetic Sync 2017-12-21

Posts: 2

Participants: 2

Read full topic

by @tfoote Tully Foote on December 27, 2017 03:37 PM

New Packages for Indigo 2017-12-26

@tfoote wrote:

We’re happy to announce 21 new packages and 145 updated packages for Indigo. 8 packages have also been removed in this sync, 6 of which are due to the regression tracked here.

As always thank you to all the maintainers and contributors who make these updates possible! Details are below.

Package Updates for indigo

Added Packages [21]:

  • ros-indigo-bcap-core: 3.0.2-1
  • ros-indigo-bcap-service: 3.0.2-1
  • ros-indigo-bcap-service-test: 3.0.2-1
  • ros-indigo-catkin-virtualenv: 0.1.4-0
  • ros-indigo-denso-robot-bringup: 3.0.2-1
  • ros-indigo-denso-robot-control: 3.0.2-1
  • ros-indigo-denso-robot-core: 3.0.2-1
  • ros-indigo-denso-robot-core-test: 3.0.2-1
  • ros-indigo-denso-robot-descriptions: 3.0.2-1
  • ros-indigo-denso-robot-gazebo: 3.0.2-1
  • ros-indigo-denso-robot-moveit-config: 3.0.2-1
  • ros-indigo-denso-robot-ros: 3.0.2-1
  • ros-indigo-dynamic-transform-publisher: 1.0.1-1
  • ros-indigo-grid-map-sdf: 1.6.0-0
  • ros-indigo-handeye: 0.1.0-0
  • ros-indigo-ros-speech-recognition: 2.1.6-0
  • ros-indigo-sainsmart-relay-usb: 0.0.2-0
  • ros-indigo-tango-ros-messages: 2.0.0-0
  • ros-indigo-test-catkin-virtualenv: 0.1.3-0
  • ros-indigo-test-catkin-virtualenv-py3: 0.1.3-0
  • ros-indigo-tork-moveit-tutorial: 0.0.3-0

Updated Packages [145]:

  • ros-indigo-actionlib: 1.11.9-0 -> 1.11.12-0
  • ros-indigo-amcl: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-assimp-devel: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-auv-msgs: 0.0.1-0 -> 0.1.0-0
  • ros-indigo-base-local-planner: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-bayesian-belief-networks: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-bond: 1.7.19-0 -> 1.7.20-0
  • ros-indigo-bond-core: 1.7.19-0 -> 1.7.20-0
  • ros-indigo-bondcpp: 1.7.19-0 -> 1.7.20-0
  • ros-indigo-bondpy: 1.7.19-0 -> 1.7.20-0
  • ros-indigo-carrot-planner: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-checkerboard-detector: 1.2.2-0 -> 1.2.3-0
  • ros-indigo-class-loader: 0.3.6-0 -> 0.3.8-0
  • ros-indigo-clear-costmap-recovery: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-collada-urdf-jsk-patch: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-costmap-2d: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-downward: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-dwa-local-planner: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-fake-localization: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-ff: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-ffha: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-geometric-shapes: 0.4.5-0 -> 0.4.6-0
  • ros-indigo-global-planner: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-grid-map: 1.5.2-0 -> 1.6.0-0
  • ros-indigo-grid-map-core: 1.5.2-0 -> 1.6.0-0
  • ros-indigo-grid-map-costmap-2d: 1.5.2-0 -> 1.6.0-0
  • ros-indigo-grid-map-cv: 1.5.2-0 -> 1.6.0-0
  • ros-indigo-grid-map-demos: 1.5.2-0 -> 1.6.0-0
  • ros-indigo-grid-map-filters: 1.5.2-0 -> 1.6.0-0
  • ros-indigo-grid-map-loader: 1.5.2-0 -> 1.6.0-0
  • ros-indigo-grid-map-msgs: 1.5.2-0 -> 1.6.0-0
  • ros-indigo-grid-map-octomap: 1.5.2-0 -> 1.6.0-0
  • ros-indigo-grid-map-pcl: 1.5.2-0 -> 1.6.0-0
  • ros-indigo-grid-map-ros: 1.5.2-0 -> 1.6.0-0
  • ros-indigo-grid-map-rviz-plugin: 1.5.2-0 -> 1.6.0-0
  • ros-indigo-grid-map-visualization: 1.5.2-0 -> 1.6.0-0
  • ros-indigo-grpc: 0.0.5-0 -> 0.0.6-0
  • ros-indigo-hrpsys-ros-bridge: 1.4.1-0 -> 1.4.2-0
  • ros-indigo-hrpsys-tools: 1.4.1-0 -> 1.4.2-0
  • ros-indigo-imagesift: 1.2.2-0 -> 1.2.3-0
  • ros-indigo-jsk-3rdparty: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-jsk-pcl-ros: 1.2.2-0 -> 1.2.3-0
  • ros-indigo-jsk-pcl-ros-utils: 1.2.2-0 -> 1.2.3-0
  • ros-indigo-jsk-perception: 1.2.2-0 -> 1.2.3-0
  • ros-indigo-jsk-recognition: 1.2.2-0 -> 1.2.3-0
  • ros-indigo-jsk-recognition-msgs: 1.2.2-0 -> 1.2.3-0
  • ros-indigo-jsk-recognition-utils: 1.2.2-0 -> 1.2.3-0
  • ros-indigo-julius: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-julius-ros: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-laser-filters-jsk-patch: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-libcmt: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-libsiftfast: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-lpg-planner: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-map-server: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-marti-data-structures: 1.2.0-0 -> 2.0.0-0
  • ros-indigo-mini-maxwell: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-move-base: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-move-base-msgs: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-move-slow-and-clear: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-moveit: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-commander: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-controller-manager-example: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-core: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-fake-controller-manager: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-full: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-full-pr2: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-kinematics: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-planners: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-planners-ompl: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-plugins: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-ros: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-ros-benchmarks: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-ros-benchmarks-gui: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-ros-control-interface: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-ros-manipulation: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-ros-move-group: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-ros-perception: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-ros-planning: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-ros-planning-interface: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-ros-robot-interaction: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-ros-visualization: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-ros-warehouse: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-runtime: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-setup-assistant: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-moveit-simple-controller-manager: 0.7.12-0 -> 0.7.13-0
  • ros-indigo-nav-core: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-navfn: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-navigation: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-nextage-calibration: 0.7.16-0 -> 0.7.16-2
  • ros-indigo-nextage-description: 0.7.16-0 -> 0.7.16-2
  • ros-indigo-nextage-gazebo: 0.7.16-0 -> 0.7.16-2
  • ros-indigo-nextage-ik-plugin: 0.7.16-0 -> 0.7.16-2
  • ros-indigo-nextage-moveit-config: 0.7.16-0 -> 0.7.16-2
  • ros-indigo-nextage-ros-bridge: 0.7.16-0 -> 0.7.16-2
  • ros-indigo-nlopt: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-nmea-msgs: 0.1.1-0 -> 1.1.0-0
  • ros-indigo-nodelet: 1.9.10-0 -> 1.9.14-0
  • ros-indigo-nodelet-core: 1.9.10-0 -> 1.9.14-0
  • ros-indigo-nodelet-topic-tools: 1.9.10-0 -> 1.9.14-0
  • ros-indigo-openrtm-ros-bridge: 1.4.1-0 -> 1.4.2-0
  • ros-indigo-openrtm-tools: 1.4.1-0 -> 1.4.2-0
  • ros-indigo-opt-camera: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-parameter-pa: 1.1.0-0 -> 1.2.1-0
  • ros-indigo-pgm-learner: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-pid: 0.0.20-0 -> 0.0.23-0
  • ros-indigo-plotjuggler: 1.4.2-0 -> 1.5.0-0
  • ros-indigo-pluginlib: 1.10.5-0 -> 1.10.6-0
  • ros-indigo-rail-object-detector: 1.0.4-0 -> 2.0.1-0
  • ros-indigo-realsense-camera: 1.8.0-0 -> 1.8.1-1
  • ros-indigo-resized-image-transport: 1.2.2-0 -> 1.2.3-0
  • ros-indigo-robot-localization: 2.3.2-0 -> 2.3.3-0
  • ros-indigo-robot-pose-ekf: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-rosnode-rtc: 1.4.1-0 -> 1.4.2-0
  • ros-indigo-rospatlite: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-rosping: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-rostwitter: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-rotate-recovery: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-rtmbuild: 1.4.1-0 -> 1.4.2-0
  • ros-indigo-rtmros-common: 1.4.1-0 -> 1.4.2-0
  • ros-indigo-rtmros-nextage: 0.7.16-0 -> 0.7.16-2
  • ros-indigo-sick-tim: 0.0.10-0 -> 0.0.11-0
  • ros-indigo-slic: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-smclib: 1.7.19-0 -> 1.7.20-0
  • ros-indigo-swri-console-util: 1.2.0-0 -> 2.0.0-0
  • ros-indigo-swri-geometry-util: 1.2.0-0 -> 2.0.0-0
  • ros-indigo-swri-image-util: 1.2.0-0 -> 2.0.0-0
  • ros-indigo-swri-math-util: 1.2.0-0 -> 2.0.0-0
  • ros-indigo-swri-nodelet: 1.2.0-0 -> 2.0.0-0
  • ros-indigo-swri-opencv-util: 1.2.0-0 -> 2.0.0-0
  • ros-indigo-swri-prefix-tools: 1.2.0-0 -> 2.0.0-0
  • ros-indigo-swri-roscpp: 1.2.0-0 -> 2.0.0-0
  • ros-indigo-swri-rospy: 1.2.0-0 -> 2.0.0-0
  • ros-indigo-swri-route-util: 1.2.0-0 -> 2.0.0-0
  • ros-indigo-swri-serial-util: 1.2.0-0 -> 2.0.0-0
  • ros-indigo-swri-string-util: 1.2.0-0 -> 2.0.0-0
  • ros-indigo-swri-system-util: 1.2.0-0 -> 2.0.0-0
  • ros-indigo-swri-transform-util: 1.2.0-0 -> 2.0.0-0
  • ros-indigo-swri-yaml-util: 1.2.0-0 -> 2.0.0-0
  • ros-indigo-trac-ik: 1.4.5-0 -> 1.4.7-0
  • ros-indigo-trac-ik-examples: 1.4.5-0 -> 1.4.7-0
  • ros-indigo-trac-ik-kinematics-plugin: 1.4.5-0 -> 1.4.7-0
  • ros-indigo-trac-ik-lib: 1.4.5-0 -> 1.4.7-0
  • ros-indigo-voice-text: 2.1.4-0 -> 2.1.6-0
  • ros-indigo-voxel-grid: 1.12.13-0 -> 1.12.14-0
  • ros-indigo-zbar-ros: 0.0.5-0 -> 0.1.0-0

Removed Packages [8]:

  • ros-indigo-cepton
  • ros-indigo-cost-map
  • ros-indigo-cost-map-core
  • ros-indigo-cost-map-cv
  • ros-indigo-cost-map-demos
  • ros-indigo-cost-map-ros
  • ros-indigo-cost-map-visualisations
  • ros-indigo-schunk-sdhx

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

  • Allison Thackston
  • Andy Zelenak
  • Bence Magyar
  • DENSO WAVE INCORPORATED
  • Dave Coleman
  • David V. Lu!!
  • Davide Faconti
  • Ed Venator
  • Elliot Johnson
  • Francisco Suarez-Ruiz
  • Hitoshi Kamada
  • IK Fast Plugin Creater
  • Ioan Sucan
  • Isaac I. Y. Saito
  • Jon Binney
  • Kei Okada
  • Kevin Hallenbeck
  • Kris Kozak
  • Marc Alban
  • Martin Günther
  • Mathias Lüdtke
  • Michael Ferguson
  • Michael Görner
  • Mikael Arguedas
  • MoveIt Setup Assistant
  • Noda Shintaro
  • Patrick Beeson
  • Paul Bovbel
  • Peter Weissig
  • Péter Fankhauser
  • Ruben Smits
  • Ryohei Ueda
  • Sergey Dorodnicov
  • Shengye Wang
  • Siddhartha Banerjee
  • TORK
  • Takuya Nakaoka
  • Tom Moore
  • Yohei Kakiuchi
  • Youhei Kakiuchi
  • Yuki Furuta
  • Yuto Inagaki
  • k-okada

Planning for this sync was at: Preparing for Indigo Sync 2017-12-21

Posts: 5

Participants: 5

Read full topic

by @tfoote Tully Foote on December 27, 2017 06:24 AM

December 25, 2017
New Packages for Lunar 2017-12-25

@marguedas wrote:

We’re happy to announce the availability of 11 new packages and 84 updated packages for ROS Lunar.
As always thank you to all the maintainers who are making these releases as well as all the contributors who have helped contribute to these releases. Full details are below.

Package Updates for lunar

Added Packages [11]:

  • ros-lunar-catkin-virtualenv: 0.1.4-0
  • ros-lunar-four-wheel-steering-controller: 0.13.2-0
  • ros-lunar-naoqi-libqi: 2.5.0-2
  • ros-lunar-nmea-msgs: 1.1.0-0
  • ros-lunar-osm-cartography: 0.2.4-0
  • ros-lunar-route-network: 0.2.4-0
  • ros-lunar-test-catkin-virtualenv: 0.1.3-0
  • ros-lunar-test-catkin-virtualenv-py3: 0.1.3-0
  • ros-lunar-test-osm: 0.2.4-0
  • ros-lunar-vision-msgs: 0.0.1-1
  • ros-lunar-zbar-ros: 0.1.0-0

Updated Packages [84]:

  • ros-lunar-auv-msgs: 0.0.1-0 -> 0.1.0-0
  • ros-lunar-combined-robot-hw: 0.12.0-0 -> 0.13.0-0
  • ros-lunar-combined-robot-hw-tests: 0.12.0-0 -> 0.13.0-0
  • ros-lunar-control-toolbox: 1.15.0-0 -> 1.16.0-0
  • ros-lunar-controller-interface: 0.12.0-0 -> 0.13.0-0
  • ros-lunar-controller-manager: 0.12.0-0 -> 0.13.0-0
  • ros-lunar-controller-manager-msgs: 0.12.0-0 -> 0.13.0-0
  • ros-lunar-controller-manager-tests: 0.12.0-0 -> 0.13.0-0
  • ros-lunar-diff-drive-controller: 0.13.1-0 -> 0.13.2-0
  • ros-lunar-effort-controllers: 0.13.1-0 -> 0.13.2-0
  • ros-lunar-explore-lite: 2.1.0-0 -> 2.1.1-0
  • ros-lunar-force-torque-sensor-controller: 0.13.1-0 -> 0.13.2-0
  • ros-lunar-forward-command-controller: 0.13.1-0 -> 0.13.2-0
  • ros-lunar-gazebo-dev: 2.7.2-0 -> 2.7.3-0
  • ros-lunar-gazebo-msgs: 2.7.2-0 -> 2.7.3-0
  • ros-lunar-gazebo-plugins: 2.7.2-0 -> 2.7.3-0
  • ros-lunar-gazebo-ros: 2.7.2-0 -> 2.7.3-0
  • ros-lunar-gazebo-ros-control: 2.7.2-0 -> 2.7.3-0
  • ros-lunar-gazebo-ros-pkgs: 2.7.2-0 -> 2.7.3-0
  • ros-lunar-geometric-shapes: 0.5.2-0 -> 0.5.3-0
  • ros-lunar-gripper-action-controller: 0.13.1-0 -> 0.13.2-0
  • ros-lunar-hardware-interface: 0.12.0-0 -> 0.13.0-0
  • ros-lunar-imu-sensor-controller: 0.13.1-0 -> 0.13.2-0
  • ros-lunar-joint-limits-interface: 0.12.0-0 -> 0.13.0-0
  • ros-lunar-joint-state-controller: 0.13.1-0 -> 0.13.2-0
  • ros-lunar-joint-trajectory-controller: 0.13.1-0 -> 0.13.2-0
  • ros-lunar-libmavconn: 0.21.5-0 -> 0.22.0-0
  • ros-lunar-marti-data-structures: 1.2.0-0 -> 2.0.0-0
  • ros-lunar-mavlink: 2017.11.11-0 -> 2017.12.12-0
  • ros-lunar-mavros: 0.21.5-0 -> 0.22.0-0
  • ros-lunar-mavros-extras: 0.21.5-0 -> 0.22.0-0
  • ros-lunar-mavros-msgs: 0.21.5-0 -> 0.22.0-0
  • ros-lunar-moveit: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-commander: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-controller-manager-example: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-core: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-fake-controller-manager: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-kinematics: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-planners: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-planners-ompl: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-plugins: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-ros: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-ros-benchmarks: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-ros-control-interface: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-ros-manipulation: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-ros-move-group: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-ros-perception: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-ros-planning: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-ros-planning-interface: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-ros-robot-interaction: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-ros-visualization: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-ros-warehouse: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-runtime: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-setup-assistant: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-moveit-simple-controller-manager: 0.9.9-0 -> 0.9.10-0
  • ros-lunar-multirobot-map-merge: 2.1.0-0 -> 2.1.1-0
  • ros-lunar-nerian-stereo: 2.0.3-0 -> 2.1.0-0
  • ros-lunar-parameter-pa: 1.1.0-0 -> 1.2.1-0
  • ros-lunar-position-controllers: 0.13.1-0 -> 0.13.2-0
  • ros-lunar-robot-localization: 2.4.0-1 -> 2.5.0-0
  • ros-lunar-ros-control: 0.12.0-0 -> 0.13.0-0
  • ros-lunar-ros-controllers: 0.13.1-0 -> 0.13.2-0
  • ros-lunar-rqt-controller-manager: 0.12.0-0 -> 0.13.0-0
  • ros-lunar-rqt-joint-trajectory-controller: 0.13.1-0 -> 0.13.2-0
  • ros-lunar-rviz: 1.12.13-0 -> 1.12.14-0
  • ros-lunar-sick-tim: 0.0.10-0 -> 0.0.11-0
  • ros-lunar-swri-console-util: 1.2.0-0 -> 2.0.0-0
  • ros-lunar-swri-geometry-util: 1.2.0-0 -> 2.0.0-0
  • ros-lunar-swri-image-util: 1.2.0-0 -> 2.0.0-0
  • ros-lunar-swri-math-util: 1.2.0-0 -> 2.0.0-0
  • ros-lunar-swri-nodelet: 1.2.0-0 -> 2.0.0-0
  • ros-lunar-swri-opencv-util: 1.2.0-0 -> 2.0.0-0
  • ros-lunar-swri-prefix-tools: 1.2.0-0 -> 2.0.0-0
  • ros-lunar-swri-roscpp: 1.2.0-0 -> 2.0.0-0
  • ros-lunar-swri-rospy: 1.2.0-0 -> 2.0.0-0
  • ros-lunar-swri-route-util: 1.2.0-0 -> 2.0.0-0
  • ros-lunar-swri-serial-util: 1.2.0-0 -> 2.0.0-0
  • ros-lunar-swri-string-util: 1.2.0-0 -> 2.0.0-0
  • ros-lunar-swri-system-util: 1.2.0-0 -> 2.0.0-0
  • ros-lunar-swri-transform-util: 1.2.0-0 -> 2.0.0-0
  • ros-lunar-swri-yaml-util: 1.2.0-0 -> 2.0.0-0
  • ros-lunar-test-mavros: 0.21.5-0 -> 0.22.0-0
  • ros-lunar-transmission-interface: 0.12.0-0 -> 0.13.0-0
  • ros-lunar-velocity-controllers: 0.13.1-0 -> 0.13.2-0

Removed Packages [0]:

Thanks to all ROS maintainers who make packages available to the ROS community. The above list of packages was made possible by the work of the following maintainers:

  • Adam Allevato
  • Adolfo Rodriguez Tsouroukdissian
  • Bence Magyar
  • D. Hood
  • Dave Coleman
  • Ed Venator
  • Elliot Johnson
  • Isaac I. Y. Saito
  • Jack O’Quin
  • Jiri Horner
  • John Hsu
  • Jon Binney
  • Jose Luis Rivero
  • Kelsey Hawkins
  • Konstantin Schauwecker
  • Kris Kozak
  • Marc Alban
  • Martin Günther
  • Mathias Lüdtke
  • Michael Ferguson
  • Michael Görner
  • Paul Bovbel
  • Peter Weissig
  • Sachin Chitta
  • Surya Ambrose
  • Tom Moore
  • Toni Oliver
  • Vincent Rousseau
  • Vladimir Ermakov

Posts: 1

Participants: 1

Read full topic

by @marguedas Mikael Arguedas on December 25, 2017 08:30 PM

December 21, 2017
A brief report from the ROS-Industrial Conference 2017

The ROS-Industrial Conference 2017 was held last week, and once again it grew bigger compared to the previous year’s edition. It expanded to a three-days event, with 28 talks attended by more than 110 participants from both industry and applied research organizations. The talks covered a wide range of topics including technical aspects of open-source robotics, as well as non-technical ones like community dynamics and business viability, application-oriented aspects and future challenges for open-source robotics, like safety and security. Here follows a selection from some of the topics and the side events covered during the conference.

20171212_131417.jpg
IMG_1754-bearbeitet.jpg
IMG_1822.JPG
20171212_181843.jpg

Matt Robinson, Program Manager for the ROS-Industrial Consortium Americas, described how ROS-Industrial has provided large players in manufacturing, who have struggled introducing automation, with an opportunity to introduce agility to manufacturing operations, hence improving utilization of resources and a broader impact on the overall value stream. Martin Hägele, head of department robot and assistive systems at Fraunhofer IPA, gave an overview about ongoing developments in the global robotics market. He addressed both industrial and service robots and presented data which the International Federation of Robotics (IFR) collects and publishes annually in the “World Robotics Report.” Jaime Martin Losa, CEO of eProsima, showed how Micro-ROS bridges the technological gap between the established robotic software platforms on high-performance computational devices and low-level libraries for microcontrollers. The first day ended with guided tours the Robotics Lab, the Application Center Industry 4.0 and the “Milestones of Robotics” exhibition at Fraunhofer IPA.

20171212_152153.jpg
IMG_1837.JPG
20171213_144418.jpg
IMG_1874.JPG

Min Ling Chan reported on how the ROS-Industrial Consortium in Asia Pacific is setting its objective and strategy towards understanding the industry needs in this region. Dirk Thomas from the Open Source Robotics Foundation introduced the forthcoming ROS2 which will provide notable advantages over ROS1, such as support for multiple operating systems and for DDS rather than a custom built middleware. Torsten Kröger, former Head of the Robotics Software Division at Google and now professor at the Karlsruhe Institute of Technology (KIT), showed examples and use-cases of manipulation and human-robot interaction tasks in order to provide a comprehensible insight into deterministic robot motion planning for safety-critical robot applications. As part of the ROSIN project Yvonne Dittrich, professor at University of Copenhagen, investigates how the ROS community takes care of quality and presented her preliminary findings. After some demonstrations of ROS-native hardware and installations the second conference day closed with a stroll through the Stuttgart Christmas market and the social dinner.

20171213_193559.jpg
IMG_1889.JPG
IMG_1894.JPG

Felipe Garcia Lopez, researcher at Fraunhofer IPA, gave insights into the Cloud Navigation he developed for mobile robots in intralogistics applications. Communication via cloud between mobile systems operating in the same traffic area enables efficient interaction without idle times even with dynamic obstacles present. Finally, Kimberly Hambuchen, Principal Technologist for Robotics in NASA’s Space Technology Mission Directorate (STMD), and Martin Azkarate from the European Space Agency (ESA) showed which requirements on software frameworks for space robotics currently exist and presented information on how NASA is using ROS for robotic prototypes for future space exploration missions.

As the event was sold out a week before the event started, we plan on hosting it on a bigger scale next year, while still targeting an early December timeframe. For your reference, the detailed agenda of the whole event as well as all slides from the speakers can be found here.

by Mirko Bordignon on December 21, 2017 06:05 PM

Ros_control academic reference

@bmagyar wrote:

Hello friends,

ros_control has just received an academic paper.
No more sleepless nights searching for ros_control on Google Scholar! :slight_smile:

If you find this work useful please give credits to the authors by citing:

  • S. Chitta, E. Marder-Eppstein, W. Meeussen, V. Pradeep, A. Rodríguez Tsouroukdissian, J. Bohren, D. Coleman, B. Magyar, G. Raiola, M. Lüdtke and E. Fernandez Perdomo
    "ros_control: A generic and simple control framework for ROS",
    The Journal of Open Source Software, 2017. (PDF)

Bibtex:

@article{ros_control,
author = {Chitta, Sachin and Marder-Eppstein, Eitan and Meeussen, Wim and Pradeep, Vijay and Rodr{\'i}guez Tsouroukdissian, Adolfo  and Bohren, Jonathan and Coleman, David and Magyar, Bence and Raiola, Gennaro and L{\"u}dtke, Mathias and Fern{\'a}ndez Perdomo, Enrique},
title = {ros\_control: A generic and simple control framework for ROS},
journal = {The Journal of Open Source Software},
year = {2017},
doi = {10.21105/joss.00456},
URL = {http://www.theoj.org/joss-papers/joss.00456/10.21105.joss.00456.pdf}
}

Thanks,
Your friendly neighbourhood ros_control team

Posts: 1

Participants: 1

Read full topic

by @bmagyar Bence Magyar on December 21, 2017 11:25 AM

December 18, 2017
NIST grant helping enhance ROS-Industrial interoperability with MTConnect

A program to integrate ROS-Industrial with the machine tool platform MTConnect is getting a boost from a grant through the National Institute of Standards and Technology (NIST).

The recent grant builds on a 2013 prototype application developed by a team of companies led by the National Center for Defense Manufacturing and Machining (NCDMM).

That effort resulted in a successful application demonstration with testing by NIST manufacturing researchers, providing the framework for a “generic bridge” to break down the well-documented language barrier in factories. In effect, the work to date, and moving forward is simply a translator that converts data and messages written in two languages—one popularized in the robotics open-source and research community, ROS/ROS-Industrial, and the other by the builders of machine tools, MTConnect—into a form that both can leverage.

www.MTConnect.org | www.rosindustrial.org The system design used in the demonstration enabled peer to peer communications between the robot and the machine tool utilizing MTConnect and ROS-Industrial. Sponsored by the National Institute of Standards and Technology (NIST) and managed by the National Center for Defense Manufacturing and Machining, partnering with System Insights, Southwest Research Institute and AMT - The Association For Manufacturing Technology.

This work set the foundation for the new NIST grant and an alliance between Southwest Research Institute (SwRI), the Association of Manufacturing Technology (AMT), and System Insights. The initial project demonstrated the ability to implement ROS-Industrial to program a robot and use MTConnect protocol for communications between the robot and a CNC machine tool. Similar to the previous effort, this new initiative is primarily software-based and will use the open standard application level protocol, MTConnect, and open-source ROS-Industrial to enable facility-level interoperability between robot teams and machine-cell devices, facilitating a “many-to-many” relationship. The expansion of the ROS-I/MTConnect solution further enhances the viability of using industry-supported, open-source software for smart manufacturing applications. Open-source software permits a continuation of free development over a very large development workspace that ultimately solves complex problems where the solution is free to the end user. The output from this project is intended to be an enabler for industry-wide adoption of open-source technologies by providing a use-case and testbed showcasing lower cost solutions for comprehensive factory floor integration for small- and medium-sized manufacturers.

Prototype Demonstration Cell

Prototype Demonstration Cell

A test-bed will be developed with an eventual demonstration to be unveiled at IMTS, within the Emerging Technology Center, in the fall of 2018 in Chicago. This will highlight a lean implementation, leveraging the latest software developments by the team, and highlight the advantages of the many-to-many approach, leveraging open-standard and open-source tools. This also extends the open standards/common communication paradigm of supporting work cells that have historically been a single stationary device, to multiple interconnected devices, and potentially swarms of devices in the mobile/dynamic environment of the future.

by Matthew Robinson on December 18, 2017 08:05 PM

Announcing updates in auv_msgs

@bmagyar wrote:

TL;DR: A new version of auv_msgs has been released to Indigo, Kinetic and Lunar. Broke message API to fix names.

For more details see the changes here
Feel free to open PR-s if you’ve got something to add :slight_smile:

We’d also like to welcome Ignacio to the maintainers team!

Posts: 3

Participants: 2

Read full topic

by @bmagyar Bence Magyar on December 18, 2017 04:01 PM

December 17, 2017
When can we use ROS answer?

@sjw wrote:

ROS answer has closed for about a week…
I think it is too long to do maintenance for a website.
I want to search some information in answer.
Thus, I wonder when we can use answer function.

Posts: 12

Participants: 7

Read full topic

by @sjw sjw on December 17, 2017 05:42 AM

December 13, 2017
ROS 2 Ardent Apalone released

We're happy to announce the ROS 2 release Ardent Apalone!

Installation instructions and tutorials can be found on the ROS 2 wiki.

To get an idea of what's in this release, be sure to read the Ardent page.

A few features and improvements we would like to highlight in this release:

  • The first non-beta release.
  • rviz including a few plugins (the Windows version will follow in a few weeks)
  • Different initialization options for message data structures in C++
  • Logging API improvements, now also used in the demos
  • Time support in C++ with different clocks
  • wait-for-service support in the Python client library
  • Draft implementation of REP 149 specifying format 3 of the package manifest files

While there is always more work to be done we consider several of the core components to be ready to be used by a broader audience. Therefore we have dropped the "beta" label and will support Ardent for one year, fixing bugs and keeping the release working, especially on platforms with rolling dependency releases (OS X / Windows). We'll start a regular six month release cycle for newer versions of ROS 2. While we do aim to keep the API as stable as possible, we can't guarantee 100% API compatibility between releases. That being said, whether or not ROS 2 is ready to be used for your application or if you can switch from ROS 1 to ROS 2 right now depends on the exact feature set and requirements of your use case. Please check the features page as well as the roadmap for more information.

As always, we invite you to try out the new software, give feedback, report bugs, and suggest features (and contribute code!): https://github.com/ros2/ros2/wiki/Contact

Your friendly neighborhood ROS 2 Team

by Tully Foote on December 13, 2017 07:13 PM

Beta of official ROS driver for Ensenso stereo cameras (ROSIN)

@gavanderhoorn wrote:

A quick update on an early result of the ROSIN project: Ensenso GmbH has made the first beta available of the driver for their stereo cameras.

ROS wiki page: wiki/ensenso_driver
Github repository: ensenso/ros_driver

This is a beta, so try it out and please use the issue tracker to report any problems.

Posts: 1

Participants: 1

Read full topic

by @gavanderhoorn gavanderhoorn on December 13, 2017 08:06 AM


Powered by the awesome: Planet