December 14, 2019
New Packages for Eloquent Elusor 2019-12-14

@mjcarroll wrote:

We’re happy to announce 52 new packages and 47 updated packages for Eloquent Elusor this week.

Thank you to all the maintainers and contributors who have helped make these packages possible!

Details are below:

Package Updates for eloquent

Added Packages [52]:

  • ros-eloquent-control-msgs: 2.2.0-1
  • ros-eloquent-control-msgs-dbgsym: 2.2.0-1
  • ros-eloquent-diagnostic-updater: 2.0.1-1
  • ros-eloquent-diagnostic-updater-dbgsym: 2.0.1-1
  • ros-eloquent-dynamic-edt-3d: 1.9.2-1
  • ros-eloquent-dynamic-edt-3d-dbgsym: 1.9.2-1
  • ros-eloquent-geodesy: 1.0.1-1
  • ros-eloquent-geographic-info: 1.0.1-1
  • ros-eloquent-geographic-msgs: 1.0.1-1
  • ros-eloquent-geographic-msgs-dbgsym: 1.0.1-1
  • ros-eloquent-joy-teleop: 1.0.1-1
  • ros-eloquent-key-teleop: 1.0.1-1
  • ros-eloquent-libphidget22: 2.0.1-1
  • ros-eloquent-libphidget22-dbgsym: 2.0.1-1
  • ros-eloquent-mouse-teleop: 1.0.1-1
  • ros-eloquent-octomap: 1.9.2-1
  • ros-eloquent-octomap-dbgsym: 1.9.2-1
  • ros-eloquent-octovis: 1.9.2-1
  • ros-eloquent-octovis-dbgsym: 1.9.2-1
  • ros-eloquent-perception-pcl: 2.1.0-1
  • ros-eloquent-phidgets-accelerometer: 2.0.1-1
  • ros-eloquent-phidgets-accelerometer-dbgsym: 2.0.1-1
  • ros-eloquent-phidgets-analog-inputs: 2.0.1-1
  • ros-eloquent-phidgets-analog-inputs-dbgsym: 2.0.1-1
  • ros-eloquent-phidgets-api: 2.0.1-1
  • ros-eloquent-phidgets-api-dbgsym: 2.0.1-1
  • ros-eloquent-phidgets-digital-inputs: 2.0.1-1
  • ros-eloquent-phidgets-digital-inputs-dbgsym: 2.0.1-1
  • ros-eloquent-phidgets-digital-outputs: 2.0.1-1
  • ros-eloquent-phidgets-digital-outputs-dbgsym: 2.0.1-1
  • ros-eloquent-phidgets-drivers: 2.0.1-1
  • ros-eloquent-phidgets-gyroscope: 2.0.1-1
  • ros-eloquent-phidgets-gyroscope-dbgsym: 2.0.1-1
  • ros-eloquent-phidgets-high-speed-encoder: 2.0.1-1
  • ros-eloquent-phidgets-high-speed-encoder-dbgsym: 2.0.1-1
  • ros-eloquent-phidgets-ik: 2.0.1-1
  • ros-eloquent-phidgets-magnetometer: 2.0.1-1
  • ros-eloquent-phidgets-magnetometer-dbgsym: 2.0.1-1
  • ros-eloquent-phidgets-motors: 2.0.1-1
  • ros-eloquent-phidgets-motors-dbgsym: 2.0.1-1
  • ros-eloquent-phidgets-msgs: 2.0.1-1
  • ros-eloquent-phidgets-msgs-dbgsym: 2.0.1-1
  • ros-eloquent-phidgets-spatial: 2.0.1-1
  • ros-eloquent-phidgets-spatial-dbgsym: 2.0.1-1
  • ros-eloquent-phidgets-temperature: 2.0.1-1
  • ros-eloquent-phidgets-temperature-dbgsym: 2.0.1-1
  • ros-eloquent-rqt-common-plugins: 1.0.0-1
  • ros-eloquent-self-test: 2.0.1-1
  • ros-eloquent-self-test-dbgsym: 2.0.1-1
  • ros-eloquent-teleop-tools: 1.0.1-1
  • ros-eloquent-teleop-tools-msgs: 1.0.1-1
  • ros-eloquent-teleop-tools-msgs-dbgsym: 1.0.1-1

Updated Packages [47]:

  • ros-eloquent-ament-cmake: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-auto: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-core: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-export-definitions: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-export-dependencies: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-export-include-directories: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-export-interfaces: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-export-libraries: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-export-link-flags: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-gmock: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-gtest: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-include-directories: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-libraries: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-nose: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-pytest: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-python: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-target-dependencies: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-test: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-cmake-version: 0.8.1-1 -> 0.8.2-1
  • ros-eloquent-ament-package: 0.8.5-1 -> 0.8.8-1
  • ros-eloquent-connext-cmake-module: 0.8.2-1 -> 0.8.4-1
  • ros-eloquent-desktop: 0.8.3-1 -> 0.8.4-1
  • ros-eloquent-libcurl-vendor: 2.2.0-1 -> 2.2.1-1
  • ros-eloquent-pcl-conversions: 2.0.0-1 -> 2.1.0-1
  • ros-eloquent-py-trees: 2.0.1-1 -> 2.0.4-1
  • ros-eloquent-py-trees-ros: 1.2.1-1 -> 2.0.1-1
  • ros-eloquent-py-trees-ros-interfaces: 1.2.0-1 -> 2.0.0-1
  • ros-eloquent-py-trees-ros-interfaces-dbgsym: 1.2.0-1 -> 2.0.0-1
  • ros-eloquent-py-trees-ros-tutorials: 1.0.6-1 -> 2.0.0-1
  • ros-eloquent-resource-retriever: 2.2.0-1 -> 2.2.1-1
  • ros-eloquent-resource-retriever-dbgsym: 2.2.0-1 -> 2.2.1-1
  • ros-eloquent-ros-base: 0.8.3-1 -> 0.8.4-1
  • ros-eloquent-ros-core: 0.8.3-1 -> 0.8.4-1
  • ros-eloquent-ros1-bridge: 0.8.1-3 -> 0.8.1-4
  • ros-eloquent-ros1-bridge-dbgsym: 0.8.1-3 -> 0.8.1-4
  • ros-eloquent-ros2trace: 0.2.10-1 -> 0.2.12-1
  • ros-eloquent-rosidl-typesupport-connext-c: 0.8.2-1 -> 0.8.4-1
  • ros-eloquent-rosidl-typesupport-connext-c-dbgsym: 0.8.2-1 -> 0.8.4-1
  • ros-eloquent-rosidl-typesupport-connext-cpp: 0.8.2-1 -> 0.8.4-1
  • ros-eloquent-rosidl-typesupport-connext-cpp-dbgsym: 0.8.2-1 -> 0.8.4-1
  • ros-eloquent-tracetools: 0.2.10-1 -> 0.2.12-1
  • ros-eloquent-tracetools-dbgsym: 0.2.10-1 -> 0.2.12-1
  • ros-eloquent-tracetools-launch: 0.2.10-1 -> 0.2.12-1
  • ros-eloquent-tracetools-read: 0.2.10-1 -> 0.2.12-1
  • ros-eloquent-tracetools-test: 0.2.10-1 -> 0.2.12-1
  • ros-eloquent-tracetools-test-dbgsym: 0.2.10-1 -> 0.2.12-1
  • ros-eloquent-tracetools-trace: 0.2.10-1 -> 0.2.12-1

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:

  • Aaron Blasdel
  • Armin Hornung
  • Austin Hendrix
  • Bence Magyar
  • Brice Rebsamen
  • Chris Lalancette
  • Christoph Sprunk
  • Christophe Bedard
  • Daniel Stonier
  • Dirk Thomas
  • Enrique Fernandez
  • Jack O’Quin
  • Martin Günther
  • Paul Bovbel
  • Steven! Ragnarök
  • William Woodall

Posts: 1

Participants: 1

Read full topic

by @mjcarroll Michael Carroll on December 14, 2019 10:11 PM

New packages and patch release for ROS 2 Dashing Diademata 2019-12-13

@nuclearsandwich wrote:

The new release of ROS 2 Dashing is here! For details about changes to the core ROS 2 packages see the “Released” column of the project board on GitHub.

Package Updates for dashing

Note that package counts include dbgsym packages which have been filtered out from the list below

Added Packages [43]:

  • ros-dashing-ament-cmake-virtualenv: 0.0.4-1
  • ros-dashing-ament-virtualenv: 0.0.4-1
  • ros-dashing-dynamic-edt-3d: 1.9.2-1
  • ros-dashing-libphidget22: 2.0.1-1
  • ros-dashing-novatel-gps-driver: 4.0.2-1
  • ros-dashing-novatel-gps-msgs: 4.0.2-1
  • ros-dashing-octomap: 1.9.2-1
  • ros-dashing-octovis: 1.9.2-1
  • ros-dashing-perception-pcl: 2.0.0-1
  • ros-dashing-phidgets-accelerometer: 2.0.1-1
  • ros-dashing-phidgets-analog-inputs: 2.0.1-1
  • ros-dashing-phidgets-api: 2.0.1-1
  • ros-dashing-phidgets-digital-inputs: 2.0.1-1
  • ros-dashing-phidgets-digital-outputs: 2.0.1-1
  • ros-dashing-phidgets-drivers: 2.0.1-1
  • ros-dashing-phidgets-gyroscope: 2.0.1-1
  • ros-dashing-phidgets-high-speed-encoder: 2.0.1-1
  • ros-dashing-phidgets-ik: 2.0.1-1
  • ros-dashing-phidgets-magnetometer: 2.0.1-1
  • ros-dashing-phidgets-motors: 2.0.1-1
  • ros-dashing-phidgets-msgs: 2.0.1-1
  • ros-dashing-phidgets-spatial: 2.0.1-1
  • ros-dashing-phidgets-temperature: 2.0.1-1
  • ros-dashing-rqt-common-plugins: 1.0.0-1
  • ros-dashing-rqt-tf-tree: 1.0.0-1

Updated Packages [127]:

  • ros-dashing-ament-cmake: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ament-cmake-auto: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ament-cmake-core: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ament-cmake-export-definitions: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ament-cmake-export-dependencies: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ament-cmake-export-include-directories: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ament-cmake-export-interfaces: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ament-cmake-export-libraries: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ament-cmake-export-link-flags: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ament-cmake-gmock: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ament-cmake-gtest: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ament-cmake-include-directories: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ament-cmake-libraries: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ament-cmake-nose: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ament-cmake-pytest: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ament-cmake-python: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ament-cmake-target-dependencies: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ament-cmake-test: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-connext-cmake-module: 0.7.2-1 -> 0.7.3-1
  • ros-dashing-cv-bridge: 2.1.2-1 -> 2.1.3-1
  • ros-dashing-cyclonedds-cmake-module: 0.4.1-1 -> 0.4.2-1
  • ros-dashing-depthimage-to-laserscan: 2.2.2-1 -> 2.2.5-1
  • ros-dashing-desktop: 0.7.2-1 -> 0.7.3-1
  • ros-dashing-image-geometry: 2.1.2-1 -> 2.1.3-1
  • ros-dashing-kinesis-video-msgs: 3.0.0-2 -> 3.1.0-1
  • ros-dashing-kinesis-video-streamer: 3.0.0-2 -> 3.1.0-1
  • ros-dashing-libcurl-vendor: 2.1.0-2 -> 2.1.2-1
  • ros-dashing-message-filters: 3.1.2-1 -> 3.1.3-1
  • ros-dashing-orocos-kdl: 3.2.0-1 -> 3.2.1-1
  • ros-dashing-python-cmake-module: 0.7.9-1 -> 0.7.10-1
  • ros-dashing-rcl: 0.7.7-1 -> 0.7.8-1
  • ros-dashing-rcl-action: 0.7.7-1 -> 0.7.8-1
  • ros-dashing-rcl-lifecycle: 0.7.7-1 -> 0.7.8-1
  • ros-dashing-rcl-yaml-param-parser: 0.7.7-1 -> 0.7.8-1
  • ros-dashing-rclcpp: 0.7.11-1 -> 0.7.12-1
  • ros-dashing-rclcpp-action: 0.7.11-1 -> 0.7.12-1
  • ros-dashing-rclcpp-components: 0.7.11-1 -> 0.7.12-1
  • ros-dashing-rclcpp-lifecycle: 0.7.11-1 -> 0.7.12-1
  • ros-dashing-rclpy: 0.7.8-1 -> 0.7.10-1
  • ros-dashing-rcutils: 0.7.3-1 -> 0.7.5-1
  • ros-dashing-resource-retriever: 2.1.0-2 -> 2.1.2-1
  • ros-dashing-rmw-connext-cpp: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-rmw-connext-shared-cpp: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-rmw-cyclonedds-cpp: 0.4.1-1 -> 0.4.2-1
  • ros-dashing-rmw-implementation: 0.7.1-2 -> 0.7.2-1
  • ros-dashing-robot-state-publisher: 2.2.4-1 -> 2.2.5-1
  • ros-dashing-ros-base: 0.7.2-1 -> 0.7.3-1
  • ros-dashing-ros-core: 0.7.2-1 -> 0.7.3-1
  • ros-dashing-ros1-bridge: 0.7.3-1 -> 0.7.4-1
  • ros-dashing-ros2action: 0.7.7-1 -> 0.7.9-1
  • ros-dashing-ros2cli: 0.7.7-1 -> 0.7.9-1
  • ros-dashing-ros2component: 0.7.7-1 -> 0.7.9-1
  • ros-dashing-ros2lifecycle: 0.7.7-1 -> 0.7.9-1
  • ros-dashing-ros2msg: 0.7.7-1 -> 0.7.9-1
  • ros-dashing-ros2multicast: 0.7.7-1 -> 0.7.9-1
  • ros-dashing-ros2node: 0.7.7-1 -> 0.7.9-1
  • ros-dashing-ros2param: 0.7.7-1 -> 0.7.9-1
  • ros-dashing-ros2pkg: 0.7.7-1 -> 0.7.9-1
  • ros-dashing-ros2run: 0.7.7-1 -> 0.7.9-1
  • ros-dashing-ros2service: 0.7.7-1 -> 0.7.9-1
  • ros-dashing-ros2srv: 0.7.7-1 -> 0.7.9-1
  • ros-dashing-ros2topic: 0.7.7-1 -> 0.7.9-1
  • ros-dashing-rosidl-adapter: 0.7.7-1 -> 0.7.8-1
  • ros-dashing-rosidl-cmake: 0.7.7-1 -> 0.7.8-1
  • ros-dashing-rosidl-generator-c: 0.7.7-1 -> 0.7.8-1
  • ros-dashing-rosidl-generator-cpp: 0.7.7-1 -> 0.7.8-1
  • ros-dashing-rosidl-generator-py: 0.7.9-1 -> 0.7.10-1
  • ros-dashing-rosidl-parser: 0.7.7-1 -> 0.7.8-1
  • ros-dashing-rosidl-runtime-py: 0.7.9-1 -> 0.7.10-1
  • ros-dashing-rosidl-typesupport-connext-c: 0.7.2-1 -> 0.7.3-1
  • ros-dashing-rosidl-typesupport-connext-cpp: 0.7.2-1 -> 0.7.3-1
  • ros-dashing-rosidl-typesupport-interface: 0.7.7-1 -> 0.7.8-1
  • ros-dashing-rosidl-typesupport-introspection-c: 0.7.7-1 -> 0.7.8-1
  • ros-dashing-rosidl-typesupport-introspection-cpp: 0.7.7-1 -> 0.7.8-1
  • ros-dashing-rviz-assimp-vendor: 6.1.4-1 -> 6.1.5-1
  • ros-dashing-rviz-common: 6.1.4-1 -> 6.1.5-1
  • ros-dashing-rviz-default-plugins: 6.1.4-1 -> 6.1.5-1
  • ros-dashing-rviz-ogre-vendor: 6.1.4-1 -> 6.1.5-1
  • ros-dashing-rviz-rendering: 6.1.4-1 -> 6.1.5-1
  • ros-dashing-rviz-rendering-tests: 6.1.4-1 -> 6.1.5-1
  • ros-dashing-rviz-visual-testing-framework: 6.1.4-1 -> 6.1.5-1
  • ros-dashing-rviz2: 6.1.4-1 -> 6.1.5-1
  • ros-dashing-tf2: 0.11.5-1 -> 0.11.6-1
  • ros-dashing-tf2-eigen: 0.11.5-1 -> 0.11.6-1
  • ros-dashing-tf2-geometry-msgs: 0.11.5-1 -> 0.11.6-1
  • ros-dashing-tf2-kdl: 0.11.5-1 -> 0.11.6-1
  • ros-dashing-tf2-msgs: 0.11.5-1 -> 0.11.6-1
  • ros-dashing-tf2-ros: 0.11.5-1 -> 0.11.6-1
  • ros-dashing-tf2-sensor-msgs: 0.11.5-1 -> 0.11.6-1
  • ros-dashing-vision-opencv: 2.1.2-1 -> 2.1.3-1

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:

  • AWS RoboMaker
  • Aaron Blasdel
  • Anup Pemmaiah
  • Armin Hornung
  • Chris Lalancette
  • Christoph Sprunk
  • Dirk Thomas
  • Erik Boasson
  • Ethan Gao
  • Isaac I.Y. Saito
  • Jacob Perron
  • Karsten Knese
  • Martin Günther
  • Max Krichenbauer
  • Michael Carroll
  • Michel Hidalgo
  • Mikael Arguedas
  • P. J. Reed
  • Paul Bovbel
  • Scott K Logan
  • Steven! Ragnarök
  • Tully Foote
  • Vincent Rabaud
  • William Woodall

Posts: 1

Participants: 1

Read full topic

by @nuclearsandwich Steven! Ragnarök on December 14, 2019 02:14 PM

December 13, 2019
New Packages for Kinetic Kame 2019-12-13

@tfoote wrote:

We’re happy to announce 12 new packages and 114 updated packages for Kinetic Kame this week.

Thank you to all the maintainers and contributors who have helped make these packages possible!

Details are below:

Package Updates for kinetic

Added Packages [12]:

Updated Packages [114]:

Removed Packages [1]:

  • ros-kinetic-noid-typef-description

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:

  • Adi Singh
  • Alexander W. Winkler
  • Bence Magyar
  • Bruno Brito
  • Chris Bollinger
  • Christoph Rösmann
  • Dave Niewinski
  • David V. Lu!!
  • Davide Faconti
  • Dirk Thomas
  • F-ROSROBO
  • Florian Weisshardt
  • G.A. vd. Hoorn
  • G.A. vd. Hoorn (TU Delft Robotics Institute)
  • Hitoshi Kamada
  • John Zhao
  • Justin Carpentier
  • Kei Okada
  • Konstantin Schauwecker
  • Ludovic Delval
  • Michael Ferguson
  • Michael Lehning
  • Nick Rotella
  • Noda Shintaro
  • Patrick Beeson
  • Praveen Palanisamy
  • Ryohei Ueda
  • Sam Pfeiffer
  • Sergey Dorodnicov
  • Shingo Kitagawa
  • Takuya Nakaoka
  • Yasuto Shiigi
  • Yohei Kakiuchi
  • Yosuke Yamamoto
  • Yuki Furuta
  • Yuto Inagaki
  • hi.kondo
  • k-okada

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on December 13, 2019 07:58 PM

New packages and patch release for ROS 2 Crystal Clemmys

@nuclearsandwich wrote:

After a wonderful year with more than 300 bloom releases it is time to say farewell to ROS 2 Crystal Clemmys. Unless there are major regressions reported with this sync there won’t be any further releases into Crystal.

You can get the release here.

Changes in ROS 2 core packages are shown on the Released column of the patch release board.

Package Updates for crystal

Added Packages [2]:

  • ros-crystal-ament-cmake-virtualenv: 0.0.4-1
  • ros-crystal-ament-virtualenv: 0.0.4-1

Updated Packages [21]:

  • ros-crystal-rclcpp: 0.6.4-0 -> 0.6.5-1
  • ros-crystal-rclcpp-action: 0.6.4-0 -> 0.6.5-1
  • ros-crystal-rclcpp-lifecycle: 0.6.4-0 -> 0.6.5-1
  • ros-crystal-rclpy: 0.6.4-0 -> 0.6.5-1
  • ros-crystal-rviz-assimp-vendor: 5.1.0-0 -> 5.1.1-1
  • ros-crystal-rviz-common: 5.1.0-0 -> 5.1.1-1
  • ros-crystal-rviz-default-plugins: 5.1.0-0 -> 5.1.1-1
  • ros-crystal-rviz-ogre-vendor]: 5.1.0-0 -> 5.1.1-1
  • ros-crystal-rviz-rendering: 5.1.0-0 -> 5.1.1-1
  • ros-crystal-rviz-rendering-tests: 5.1.0-0 -> 5.1.1-1
  • ros-crystal-rviz-visual-testing-framework: 5.1.0-0 -> 5.1.1-1
  • ros-crystal-rviz2: 5.1.0-0 -> 5.1.1-1

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:

  • Dirk Thomas
  • Karsten Knese
  • Max Krichenbauer
  • Scott K Logan
  • William Woodall

Posts: 2

Participants: 1

Read full topic

by @nuclearsandwich Steven! Ragnarök on December 13, 2019 03:34 AM

ROSCon 2019 Macau: Videos are Live!

@Katherine_Scott wrote:

ROSCon 2019 Macau videos are now live on Vimeo and the ROSCon website along with slides! We apologize for the delay in getting the videos out. Please let us know what talks you found the most helpful as your feedback helps the ROSCon review committee make better selections next year.

We would like to thank Qualcomm for making it possible to share these videos with our global community.

We also want to thank or ROSCon speakers, volunteers, and sponsors that make the event possible.

Posts: 10

Participants: 10

Read full topic

by @Katherine_Scott Katherine Scott on December 13, 2019 12:26 AM

December 10, 2019
Observations from CRAV.AI 2019 Conference on Collaborative Robotics and AI

I had the opportunity to attend CRAV.ai 2019 in San Jose CA and present SwRI's work on collaborative robots; this work described how we built a sophisticated collaborative robotics application where various tasks were taught to a robot arm by way of human demonstration. One highlight of this application is that it leveraged low-cost sensors and open-source software frameworks such as ROS, MoveIt, AruCo, Ceres, etc.

CRAV slide.JPG

The presentation was very well received, and we hope it'll lead to opportunities to further that work and continue to do research in that space.

Furthermore, there were a great deal of interesting presentations that explored innovative ways to make robots collaborate and empower human workers in the various industries where the inherent adaptability and dexterity of humans remains irreplaceable.

Human Augmentation of Robots for the Automation Age (SARCOS):

  • Described the following challenges in manufacturing:

  • Projected labor shortages in the US and many other industrialized nations in the next decade will have a negative impact on the economy in the trillions of dollars.

  • Occupational injuries incur an annual cost of \$100 billion in the US

  • Complete automation isn’t the solution to the labor shortage challenges ahead

    • Humans will continue to play a role in manufacturing due to the unstructured and unpredictable nature of very many tasks for which automation falls off short.

    • SARCOS showed its GUARDIAN XO powered exoskeleton which a human can operate in unstructured environments in order to carry out a diverse set of tasks.

    • The suit provides the human worker with added strength and endurance, reduces the risk of injuries and enhances productivity.

How Robot Motion Planning is setting Robots Free (Collaborative Robotics):

  • Interesting approach to multi robot motion planning using precomputed swept volumes

How AI, Robotics, Vision, and Industry 4.0 Will Revolutionize manufacturing (Canon USA)

  • Great summary of past technological revolutions

    • Mechanization, steam power, weaving loom (Industry 1.0)

    • Mass production, assembly line, electrical energy (Industry 2.0)

    • Automation, computers, electronics (Industry 3.0)

  • Industry 4.0 forecast

    • Increased efficiency through robot/human collaboration

    • The concept of the Smart Factory (highly digitized and interconnected production)

    • Large scale data anaylysis

  • Lights Out Manufacturing

    • Advanced sensing technologies that allows robots and machines to operate in the dark

    • If implemented correctly could maximize efficiency and profitability.

    • Not a common approach in factories but its viable given current technologies.

  • The Role of AI

    • Predictive maintenance would eliminate the need for predetermined schedules

    • Through machine learning and data collection, systems could adapt to changes or function with fewer interruptions

    • Increase the remaining useful life of machinery

Volumetric Technologies for Future Sports Experiences (Intel Sports)

  • The role of advanced technologies in today’s sports

    • An array of cameras placed around the stadium allows creating a virtual camera view at any desired location

    • Broadcast Enhancements allow creating a narrative or facilitate advertisement

    • Automated virtual camera movement allows following players, follow ball, predict best camera position, etc.

    • Used by various professional tournaments and leagues

  • Volumetric video

    • Can create rich, compelling and immersive media experience.

    • Combined with VR headsets would provide a fundamentally new way to experience sports

It was a pleasure to be part of such an interesting event, and we look forward to both contributing and working with others to advance robotics, in particular where collaboration is a key element.

by Jorge Nicho on December 10, 2019 10:43 PM

New packages for Melodic 2019-12-10

@clalancette wrote:

We’re happy to announce the next update for ROS Melodic. We have 63 new packages as well as 107 updated packages.

Full details are below.

Package Updates for melodic

Added Packages [63]:

Updated Packages [107]:

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:

  • Aaron Hoy
  • Abraham Monrroy
  • Adi Singh
  • Alexander Gutenkunst
  • Alexander W. Winkler
  • Bence Magyar
  • Bruno Brito
  • Chris Bollinger
  • Christian Henkel
  • Christoph Rösmann
  • Dave Niewinski
  • David Feil-Seifer
  • David V. Lu!!
  • Davide Faconti
  • Diego Centelles
  • Dirk Thomas
  • Dorian Scholz
  • F-ROSROBO
  • Felix Messmer
  • Florian Weisshardt
  • Francisco Suarez-Ruiz
  • Gareth Cross
  • HXR
  • Jack O’Quin
  • Justin Carpentier
  • Konstantin Schauwecker
  • Kris Kozak
  • Ludovic Delval
  • Marc Alban
  • Mario Prats
  • Mark Moll
  • Masaya Kataoka
  • Michael Ferguson
  • Michael Lehning
  • Mike Lautman
  • Nick Rotella
  • P. J. Reed
  • Patrick Beeson
  • Praveen Palanisamy
  • ROS Orphaned Package Maintainers
  • Sam Pfeiffer
  • Shohei Fujii
  • Steve Macenski
  • Veronica Lane
  • Vladimir Ermakov
  • William Woodall
  • Yasuto Shiigi
  • Yosuke Yamamoto
  • Yusuke Fujii
  • hi.kondo
  • mitsudome-r
  • syouji

Posts: 1

Participants: 1

Read full topic

by @clalancette Chris on December 10, 2019 04:21 PM

December 06, 2019
What Went Down at ROSCon 2019

ROS-Industrial representatives from the three global regions attended and presented at ROSCon Macau 2019, held from Oct. 31 to Nov 1.

The booth was supported by all the three consortia from Asia Pacific, Americas and Europe. Some initial changes were the introduction of workshops ahead of the formal agenda, including a very good workshop on “Day 0” on the ecosystem (ROS is getting bigger and bigger, how do we get those people more into an active role?).

This year, the ROS-Industrial team presented the demonstration titled “Robotic Pick & Place with Augmented Reality” which was made to showcase the interoperability of ROS by allowing robots to perform tasks by learning from an operator input using an intuitive augmented reality interface – removing the need for programming of robots.

As far as exhibitors along with ROS-I, it was noticed that there was a noticeable increase in exhibitors (~40) with more companies attending/supporting ROSCon, so this speaks to the growth and evolution of the community and for the event itself.

Obvious recruitment, seeking of ROS-skilled professionals, part of "we are hiring”, even more so than in past years. While another hot topic, or maybe the red ribbon of the event, was "we need more and complete documentation of ROS2."

As such with such full in content events, or how long the coffee breaks, they are never sufficient to meet and greet everybody.

IMG-20191030-WA0063.jpg

Photo : Ng Wei Kien & Dejanira Araiza at the ROS-Industrial Booth showcasing the demo.

The ROS-I teams were selected and gave three talks:

Levi Armstrong and Chris Lewis presented on “Industrial Manufacturing Automation Leveraging ROS” and Dejanira Araiza-Illan on the topic “PackML2: State Machine Based System Programming, Monitoring and Control in ROS2” with Michael Ripperger presenting on “Flexible Framework for Quantitative Reachability Analysis.”

IMG-20191031-WA0000.jpg

Photo : Levi Armstrong, ROS-I Americas/SwRI presenting Industrial Manufacturing Automation Leveraging ROS .

There was also one of the major keynote presentations on the Robotics Middleware Framework (RMF) about roadmap to adopt robotic solutions and smart systems in Singapore’s public healthcare sectors.

A brief summary of presentations that stood out to the teams present:

  • ROS Real Time Workshop
    • Both hardware and software requirements
      • Real-time kernel, messaging, etc.
    • Lots of effort required to setup/run real-time Linux kernel
    • Security and real-time conflict of interest?
    • Timing and determinism
      • TCP/IP can meet determinism
      • UDP can meet timing
      • Neither meet both
    • Large effort by various companies to benchmark timing, processing speed, memory usage, latency, etc. of ROS2 with various DDS implementations
    • Very important for mobile robotics and autonomous applications
    • Benefits of this effort will likely be available by the time most industrial manipulation applications we work on care about this functionality
  • ROS2 on VxWorks
    • ROS2 dependencies installed
    • Run ROS2 on an RTOS
  • ROS2 migration of Navigation Stack
    • Re-design of the architecture to leverage ROS2 features
      • Component and life-cycle nodes
    • Run-time definable behavior trees for decision-making in fault scenario
  • Reactive programming
  • ROS in Jupyter Notebook
    • Essentially an online IDE that can compile and run code
    • Alternative for industrial training (Python)
    • C++ support?
  • High Assurance ROS
  • Reactive Jogger
    • UT Austin Robotics Lab
    • Teleoperation robot jogger with singularity avoidance, signal filtering, reactive control
  • Cartesian Controllers
  • OMPL constrained planning
  • MoveIt Task Constructor
  • Pilz Industrial Motion Control
    • Deterministic motion planners for industrial move types (MoveL, MoveJ, MoveC)
    • Include blending parameters
20191102_115204.jpg

Photo : Michael Ripperger, ROS-I Americas/SwRI, presents processes planning framework at the MoveIt Workshop.

Things to take away…

  • High level observations:
    • Majority of attendance/presentations related to mobile robots in logistics space and autonomous driving
    • Lots of people care about real-time capability
    • Lots of people diving deep into the RMW and DDS layers to fix bugs and improve performance
    • Lots of people care about scaling robot operations
      • Discussion around how ROS fits into fleet deployment framework
      • System of systems architecture approach
    • Not much about manipulation
      • One half of one day
      • Not a lot of manufacturing-centric content outside of ROS-I
  • Interesting Information
    • TRAC_IK has mutliple objectives for driving gradient
      • Speed: default (joint speed?)
      • Distance: minimizes joint distance from seed
        • Should probably be preferred to minimize configuration changes
      • Manipulability
    • BioIK
    • ROS2 Life-cycle nodes
      • State-machine for nodes
    • ROS2 component nodes
      • Similar to nodelets
      • Can share memory with other component nodes in the same container
    • Use MoveIt planning objects in favor of the MoveGroup
    • Microsoft is releasing HoloLens v2.0 that are “industrial grade”

Thoughts relative to ROS-I...

  • We should become more familiar with ros_control capability
    • Trajectory replacement
    • Cartesian and force control capability
    • Create some compelling demos
    • Real-time interaction with external devices
  • We need to be more active/supportive of core ROS repositories
  • Creation of ROS Calibration GitHub organization
    • We should move our calibration libraries here to make them more discoverable
    • We can still brand them thoroughly as ROS-I developed

Finally, it is clear that ROS2 development, including for navigation, and optimization of the DDS/transport layer and discussion of real-time capabilities are making great progress. However, there are challenges, particularly related to areas that ROS-I seeks to address. Capabilities for manipulation/path planning for manipulators, documentation, and significant progress on ease of use, to enable manufacturing-centric organizations to really jump in. In the interim there is enough tech industry engagement to fill the void, to provide additional tools and offer solutions to meet industry needs. Now is the time to create compelling ROS2 demonstrations/reference applications that drive further end-user engagement. ROSCon always lights a fire of inspiration, now to just set to the work of getting that fire to spread. Looking forward to 2020!

Content provided by Sheila Suppiah, ROS-I AP, Thilo Zimmerman, ROS-I EU, and Michael Ripperger, ROS-I Americas.

by Matthew Robinson on December 06, 2019 02:08 PM

December 03, 2019
Feedback wanted: ROS Developer Experience

@seanyen-msft wrote:

We at Microsoft are looking for ways to improve the VS Code extension for ROS and take it to the next level. Our goal is to make it easy for you to create, build, simulate and deploy ROS applications. We are looking to gather feedback from the community on these lines. If you are interested in speaking with our product team on your thoughts or even expressing some of the challenges that you currently face, we would love to hear from you. Please PM me directly and I can setup some time for us to talk.

Thank you!
Microsoft Edge Robotics team

Posts: 1

Participants: 1

Read full topic

by @seanyen-msft Sean Yen [Msft] on December 03, 2019 09:52 PM

ROS Clock - Countdown to Extinction

@DLu wrote:

There was a lot of discussion at ROSCon about how much longer various distros (and ROS1 as a whole) will be supported. Some people were likening it to the Python2 -> Python3 switch. And since the Python community has pythonclock.org to count down the remaining days, I figured we could use something similar. So enjoy ROS Clock.

Source: https://github.com/DLu/ros_clock

Posts: 3

Participants: 3

Read full topic

by @DLu David!! on December 03, 2019 02:34 AM

December 02, 2019
Selfception: TIAGo robot, to recognize itself in the mirror using AI

Perception in robotics can be trickier than we think. Just think for a moment how complex the human perception is: How do we know that it is us when we look at the mirror, even if we see us from a different perspective? How can we recognize a person even if time passess and he/she gets older?

Our brain is amazingly capable of making sense to this uncertainty that is part of the world, after processing the information received by our senses. and automatically makes sense of it, enabling us to act coherently based on these impressions.

Humans’ perception could be an inspiration to improve the way robots interact with the world, which perception skills are still far from ours, and way more rigid. And that’s what researcher in robotics and AI, Dr. Pablo Lanillos, is working on: to give this flexible perception humans have to robots, through the MSCA Selfception project hosted at the Technical University of Munich.

Lanillos made some cool experiments to enable TIAGo robot recognize itself in the mirror thanks to Artificial Intelligence!

Using TIAGo robot in the Selfception research

During his stay at PAL Robotics, we asked Lanillos how it was to work with TIAGo robot: “I was able to implement everything in TIAGo in less than one month. You have a robot that is ready for research, and this actually shortens the research time. Imagine that I had to build a robot, the robot’s control framework and everything related to its interface, all by myself. I would have spent two years!”, he answered.

One of the things the robotics researcher highlighted of our ROS-based mobile manipulator was its robustness: “Roboticists will understand me on this: every time I turn the robot on, it works. The reliability of the robot is super important, because I can perform the experiments and repeat them, and nothing changes.”

 

TIAGo robot using AI to recognize itself in the mirror

 

The experiment conducted by Lanillos used mathematical models in body perception to help the TIAGo robot determine that what it perceives in the mirror is itself. “Of course, you cannot ask the robot to identify itself as a human does. Instead of that, what we have is a probabilistic model that actually learns how the body behaves in the mirror and, according to that, it decides whether it is itself or not,” details the MSCA researcher.

 

Lanillos’ model tries to use the world’s uncertainty in order to enable TIAGo to perceive its body, and know where its body is acting just as we do: “How can we move the arm and know that it’s ourselves in front of the mirror? It is a different perspective, we don’t have the same model. Here we don’t have inverse kinematics or anything like that, we have to learn it. That’s why the mirror experiment is important: because it is a reflection of yourself – of the robot’s body – and we cannot use the usual procedures used in robotics.”

 

Thank you, Dr. Lanillos, for presenting your interesting research to our team! You can follow closely his project’s progress through the Selfception webpage.

 

Remember! TIAGo robot is open source: you can use its simulation online by easily following the steps on its ROS Tutorials, and get started today with your idea!

 

The post Selfception: TIAGo robot, to recognize itself in the mirror using AI appeared first on PAL Robotics Blog.

by Elitsa Dimitrova on December 02, 2019 03:27 PM

November 27, 2019
ROS Russia Meetup in Moscow November 30 2019

@amburkoff wrote:

We invite you to the ROS Meetup on Robotics, which will be held in Moscow on November 30, 2019
Program announcement https://habr.com/ru/news/t/475704/ and registration links by the participant or speaker.
Video and slides of robotics presentations from Russia’s first ROS Meetup on April 16 https://habr.com/ru/post/476436/
Let’s develop the ROS community together!

Posts: 1

Participants: 1

Read full topic

by @amburkoff on November 27, 2019 09:02 AM

November 22, 2019
ROS 2 Eloquent Elusor Released!

@mjcarroll wrote:

We’re happy to announce the ROS 2 release Eloquent Elusor!

To get an idea of what’s in this release, be sure to read the Eloquent Elusor page.

In addition to feature development, there has been a focus on organizing and improving tutorials for ROS2. We are asking the community to try these tutorials with Eloquent Elusor and provide feedback where possible. This feedback helps the team continuously improve the documentation.

Here are a few features and improvements we would like to highlight in this release:

And finally the name of the next ROS 2 release scheduled for May 2020 will be:

Foxy Fitzroy

Your friendly ROS 2 Team

P.S. Get your Elusor swag (including socks!)

Posts: 6

Participants: 5

Read full topic

by @mjcarroll Michael Carroll on November 22, 2019 11:16 PM

November 21, 2019
ROS Eloquent Elusor Release Tshirt

@tfoote wrote:

ROS Eloquent Elusor Tshirts Available Until Dec 12th

With the release of ROS Eloquent Elusor just around the corner we’re happy to announce that there’s now a Teespring Tshirt campaign open for you to order your tshirts.

Order yours before Dec 12th!

image

This release we have hoodies again. And we’re trying out socks too.

image

And if you’d like a poster you can also get one from the Open Robotics store on Zazzle. There are both paper posters and wrapped canvas posters available.

alt
Eloquent Elusor Release Poster
by OpenRobotics

alt
Eloquent Elusor Release Poster on Wrapped Canvas
by OpenRobotics

Posts: 5

Participants: 1

Read full topic

by @tfoote Tully Foote on November 21, 2019 12:04 AM

November 19, 2019
[WEBINAR] How to Teach ROS | Nov 27, 2019

@YUHONG_LIN wrote:

WEBINAR • How to Teach ROS

Date&Time: 27 November, 2019 @ 7 - 8 P.M. CEST

Registration website: http://www.theconstructsim.com/webinar-how-to-teach-ros/

*Free Event

Robot Operating System (ROS) is the standard of robot programming and is one of the most essential course for a Robotics degree. But teaching ROS to students can be a daunting process. In this free webinar, we are going to show you how to make a practical ROS course for your undergraduate or master students. (NO ROS INSTALLATION REQUIRED)

Content outline:

  • Problems teaching ROS
  • Creating the perfect hands-on ROS Course
  • How to define the Teaching Schedule / Syllabus
  • How to create a ROS Jupyter Notebook
  • How to create some Gazebo Robot Simulations
  • How to connect the Notebook to Robot Simulations
  • How to add a Practical Project
  • How to include a Practical Exam

Outcomes:

  • Change the ROS course from passive listening to active practicing.
  • Move away from a slides based teaching method to a notebook based one, where direct interaction with robots is embedded in the method itself.

Webinar for:

Professors / Teaching Assistants in Robotics who are preparing the ROS Course for 2020.

Materials:

  • The whole code will be provided to all attendees as a ROSject, containing simulation, notebook with instructions and code.
  • All attendees will receive a guide on HOW TO TEACH ROS WITH NO HASSLE.
    For those who are unable to make the time and date of the webinar, a recorded version and teaching materials of the webinar will be available for download.

Speaker:

RICARDO TÉLLEZ, Ph.D.

Dr. Ricardo Tellez is the CEO of The Construct (www.theconstruct.ai), the company world leader in teaching ROS online. He has a Ph.D. in Artificial Intelligence. He has almost 10 years of experience building software for ROS based robots including human-sized humanoids. He is the author of 4 books about learning ROS (the ROS in 5 days series of books). He teaches ROS at the University of LaSalle in Barcelona for the graduate students at the Master on Robotics. Additionally, he delivers every Tuesday a free ROS Live Class on his Youtube channel, where attendants can learn and practice a ROS subject. He is also the conductor of the ROS Developers Podcast where he interviews every week a ROS expert about how to better program robots with ROS.
His goal is to make robots understand their world. And he has a plan.

Posts: 1

Participants: 1

Read full topic

by @YUHONG_LIN on November 19, 2019 12:59 PM

November 16, 2019
New packages for ROS Kinetic Kame 2019-11-15

@tfoote wrote:

We’re happy to announce 12 new and 144 updated packages for Kinetic.

There is one regression of pinocchio due to cmake/pkg-config that’s being actively worked on to be resolved.

Thank you to all the maintainers and contributors who have helped make these packages available!

Details are below.

Package Updates for kinetic

Added Packages [12]:

  • ros-kinetic-cob-gazebo-tools: 0.7.3-1
  • ros-kinetic-cob-hardware-emulation: 0.7.9-1
  • ros-kinetic-leuze-description: 1.0.0-2
  • ros-kinetic-leuze-msgs: 1.0.0-2
  • ros-kinetic-leuze-phidget-driver: 1.0.0-2
  • ros-kinetic-network-autoconfig: 0.1.1-1
  • ros-kinetic-robot-indicator: 0.1.3-1
  • ros-kinetic-robot-systemd: 0.1.2-1
  • ros-kinetic-seed-r7-moveit-config: 0.3.0-1
  • ros-kinetic-seed-r7-ros-controller: 0.3.0-1
  • ros-kinetic-seed-r7-samples: 0.3.0-1
  • ros-kinetic-turtlebot-loadout-kha1: 0.1.0-3

Updated Packages [144]:

Removed Packages [1]:

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:

  • AWS RoboMaker
  • Alexander Bubeck
  • Benjamin Maidel
  • Christoph Rösmann
  • Daniel Miller
  • Davide Faconti
  • Felipe Garcia Lopez
  • Felix Messmer
  • Felix Zeltner
  • Florian Weisshardt
  • HXR
  • Jannik Abbenseth
  • Jordy van Appeven
  • Joshua Hampp
  • Justin Carpentier
  • Kevin Hallenbeck
  • Kris Kozak
  • Ludovic Delval
  • Marc Alban
  • Mathias Lüdtke
  • Matthias Gruhler
  • Micho Radovnikovich
  • Nick Rotella
  • P. J. Reed
  • Richard Bormann
  • Rohan Agrawal
  • Scott K Logan
  • Vladimir Ermakov
  • Yasuto Shiigi
  • dfaconti
  • hi.kondo
  • turtlebot

Posts: 5

Participants: 2

Read full topic

by @tfoote Tully Foote on November 16, 2019 02:41 AM

November 15, 2019
New packages for ROS 2 Crystal Clemmys 2019-11-15

@nuclearsandwich wrote:

A small update but a worthy one. I also want to remind everyone that Crystal support ends in December. There will probably be one or two more syncs before the final one depending on necessity.

Package Updates for crystal

Added Packages [2]:

  • ros-crystal-px4-msgs: 2.0.1-1
  • ros-crystal-px4-msgs-dbgsym: 2.0.1-1

Updated Packages [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:

  • Nuno Marques

Posts: 1

Participants: 1

Read full topic

by @nuclearsandwich Steven! Ragnarök on November 15, 2019 12:55 PM

New packages for ROS 2 Dashing Diademata 2019-11-15

@nuclearsandwich wrote:

We have new packages and a good number of updates for ROS 2 Dashing.

Thanks as always to everyone who has contributed to this release. This sync has only updated the Debian packages. A patch release for all platforms will be made with the next sync.

Package Updates for dashing

Added Packages [25]:

  • ros-dashing-ament-download: 0.0.1-1
  • ros-dashing-can-msgs: 2.0.0-1
  • ros-dashing-cross-compile: 0.1.1-1
  • ros-dashing-foonathan-memory-vendor: 0.3.0-1
  • ros-dashing-px4-msgs: 2.0.1-1
  • ros-dashing-rqt-robot-steering: 1.0.0-1
  • ros-dashing-sick-scan2: 0.1.4-1
  • ros-dashing-swri-console-util: 3.0.3-1
  • ros-dashing-swri-dbw-interface: 3.0.3-1
  • ros-dashing-swri-geometry-util: 3.0.3-1
  • ros-dashing-swri-image-util: 3.0.3-1
  • ros-dashing-swri-math-util: 3.0.3-1
  • ros-dashing-swri-opencv-util: 3.0.3-1
  • ros-dashing-swri-prefix-tools: 3.0.3-1
  • ros-dashing-swri-roscpp: 3.0.3-1
  • ros-dashing-swri-route-util: 3.0.3-1
  • ros-dashing-swri-serial-util: 3.0.3-1
  • ros-dashing-swri-system-util: 3.0.3-1
  • ros-dashing-swri-transform-util: 3.0.3-1

Updated Packages [33]:

  • ros-dashing-behaviortree-cpp-v3: 3.0.9-1 -> 3.1.1-1
  • ros-dashing-cloudwatch-logs-common: 1.1.1-0 -> 1.1.2-1
  • ros-dashing-cloudwatch-metrics-common: 1.1.1-0 -> 1.1.2-1
  • ros-dashing-cyclonedds: 0.1.0-1 -> 0.1.0-3
  • ros-dashing-cyclonedds-cmake-module: 0.4.0-1 -> 0.4.1-1
  • ros-dashing-dataflow-lite: 1.1.1-0 -> 1.1.2-1
  • ros-dashing-file-management: 1.1.1-0 -> 1.1.2-1
  • ros-dashing-h264-encoder-core: 2.0.2-1 -> 2.0.3-1
  • ros-dashing-lex-common-msgs: 3.0.0-1 -> 3.1.0-1
  • ros-dashing-lex-node: 3.0.0-1 -> 3.1.0-1
  • ros-dashing-rmw-cyclonedds-cpp: 0.4.0-1 -> 0.4.1-1
  • ros-dashing-ros2action: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-ros2cli: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-ros2component: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-ros2lifecycle: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-ros2msg: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-ros2multicast: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-ros2node: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-ros2param: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-ros2pkg: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-ros2run: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-ros2service: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-ros2srv: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-ros2topic: 0.7.6-1 -> 0.7.7-1

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:

  • AWS RoboMaker
  • Davide Faconti
  • Dirk Thomas
  • Eclipse Foundation, Inc.
  • Erik Boasson
  • Jacob Perron
  • Mathias Lüdtke
  • Michael Lehning
  • Michel Hidalgo
  • Miguel Company
  • Nuno Marques
  • P. J. Reed
  • Steve Macenski
  • William Woodall

Posts: 1

Participants: 1

Read full topic

by @nuclearsandwich Steven! Ragnarök on November 15, 2019 12:46 PM

November 14, 2019
New packages for Melodic 2019-11-14

@clalancette wrote:

We’re happy to announce the next update for ROS Melodic. We have 32 new packages as well as 126 updated packages.

Full details are below.

Package Updates for melodic

Added Packages [32]:

Updated Packages [126]:

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:

  • AWS RoboMaker
  • Alexander Bubeck
  • Benjamin Maidel
  • Chris Lalancette
  • Christoph Rösmann
  • Daniel Miller
  • Davide Faconti
  • Devon Ash
  • Diego Centelles
  • Felipe Garcia Lopez
  • Felix Messmer
  • Felix Zeltner
  • Florian Weisshardt
  • HXR
  • Jannik Abbenseth
  • Javier Perez
  • Johannes Meyer
  • Jon Binney
  • Joshua Hampp
  • Justin Carpentier
  • Kevin Hallenbeck
  • Marc Hanheide
  • Mario Prats
  • Martin Pecka
  • Mathias Lüdtke
  • Matthias Gruhler
  • Max Schwarz
  • Micho Radovnikovich
  • Nick Hawes
  • P. J. Reed
  • Richard Bormann
  • Rohan Agrawal
  • Scott K Logan
  • Siddhartha Banerjee
  • Vladimir Ermakov
  • Yasuto Shiigi
  • dfaconti

Posts: 1

Participants: 1

Read full topic

by @clalancette Chris on November 14, 2019 02:09 PM

Which board/microprocessor should I use? I want to use ROS Kinetic on Ubuntu 16.04, along with packages like move_base, laser_scan_matcher for indoor autonomous navigation

@parzival wrote:

I am confused as to which board will be able to handle the necessary computation to run autonomous navigation for my turtlebot-like-robot.
I want to run Ubuntu 16.04 OS and ROS Kinetic, and need packages like move_base, laser_scan_matcher.
I’ve heard that Raspberry Pi 3 and its Arm Cortex A53 isn’t enough for the purpose.
What are your views?

Posts: 8

Participants: 6

Read full topic

by @parzival Jash Mota on November 14, 2019 08:53 AM

November 13, 2019
World MoveIt Day Hackathon - Next Week

@davetcoleman wrote:

Hi ROS Community,

This year’s World MoveIt Day hackathon is fast approaching - see you next Wednesday November 20th. We now have 10 official locations around the world, but you can join in from anywhere!

Full event details

Posts: 3

Participants: 3

Read full topic

by @davetcoleman Dave Coleman on November 13, 2019 05:58 PM

ROS Installer Tooling

@LucidOne wrote:

Hello fellow humans and robots,

We have recently been working on a new TurtleBot ISO release and have now finally written enough documentation for an official release of the build toolchain for the installer.

Roll Your Own ISO

ryo-iso [0] is a modern ISO builder that streamlines the process of deploying a complete robot operating system from a yaml config file. It has been tested with Ubuntu 16.04 and 18.04 and has significant automation for caching and tracking upstream releases.

As an example, the TurtleBot ryo-iso project is being used to generate an ISO installer with Ubuntu 16.04 + ROS Kinetic + drivers + desktop and system enhancements.

Along the way we have developed a few ROS packages, that should be available in the next Kinetic sync, which we would like to highlight for potential collaborators. Melodic support should be done within a few weeks.

Network Autoconfiguration

network_autoconfig [1] provides automatic configuration of the ROS_MASTER_URI, ROS_IP, and ROS_HOSTNAME for most use cases by introspecting the kernel routing tables and network interfaces for the current IP address. This allows mobile robots running on a wireless network to automagically connect to a workstation running ROS. It is designed to support fixed interfaces, Zeroconf, DHCP and/or a VPN.

Caveat emptor: It may also make it easier to access your robot from the internet.

Robot Startup

robot_systemd [2] builds on a broad survey of previous work starting ROS at bootup. This package should work with most robots that have Systemd installed.

For example to run roslaunch turtlebot_bringup minimal.launch at bootup

sudo apt install ros-kinetic-robot-systemd
systemctl --user enable roslaunch@turtlebot_bringup:minimal.launch
systemctl --user start roslaunch@turtlebot_bringup:minimal.launch
# Start at bootup instead of graphical login
sudo loginctl enable-linger $USER

robot_indicator provides an efficient GUI interface for locally starting and stopping services enabled by the robot_systemd package.

Please let me know if you have any feedback!

Thanks,
Bil

Posts: 1

Participants: 1

Read full topic

by @LucidOne Bil, hxr.io on November 13, 2019 09:27 AM

November 12, 2019
Your first robot: A beginner’s guide to ROS and Ubuntu Core

@kyrofa wrote:

Hey everyone. Several years ago I created a blog/video series discussing taking a ROS prototype to production using snaps and Ubuntu Core. I got good feedback on that series, but a few folks mentioned that the barrier to entry was a little high as it used the Turtlebot 2, which is by no means cheap. As a result, a while ago I began a blog/video series that uses the CamJam EduKit #3 (the robotics kit) which is incredibly inexpensive. It doesn’t have any particularly useful sensors, but it was still a good platform for hobbyists to learn ROS, snaps, and Ubuntu Core in a five-part series. I got off to a strong start, but due to a few internal issues I was unable to finish the series :cry:… until now :partying_face:.

Please allow me to present the now-completed blog/video series.

The videos have all been collected into the Your first robot: A beginner’s guide to ROS and Ubuntu Core playlist.

Posts: 3

Participants: 3

Read full topic

by @kyrofa Kyle Fazzari on November 12, 2019 07:47 PM

Alliance with The Singapore Industrial Automation Association

ROS-Industrial Consortium Asia Pacific signs alliance with Singapore Industrial Automation Association (SIAA)

On the third day of the Industrial Transformation Asia Pacific (ITAP) 2019, a Memorandum of Understanding was signed between the Singapore Industrial Automation Association (SIAA) , ROS-Industrial Consortium Asia Pacific and the National Robotics R&D Programme Office (NR2PO), The guest-of-honour to witness this event was the Senior Minister of State for Trade and Industry, Singapore, Dr. Koh Poh Koon.

The signing ceremony taking place at ITAP 2019, Sandbox 2 on 24th October 2019.

The signing ceremony taking place at ITAP 2019, Sandbox 2 on 24th October 2019.

5.jpg

This partnership will enable collaboration between the three organizations to accelerate the adoption of robotics using the Robot Operating System (ROS) in the automation industry and by system integrators in Singapore. ROS-Industrial Consortium will continue to work with organizations and associations to promote open innovation and collaborations, as well as the use of democratic robotics.

by Sheila Devi on November 12, 2019 06:31 AM

[ROS Developers Podcast] #59: AWS RoboMaker With Roger Barga

@RebeccaU wrote:

ROS Developers Podcast #59: AWS RoboMaker With Roger Barga
Podcast Link: https://www.theconstructsim.com/aws-robomaker-with-roger-barga/

Today, we are going to talk with the person behind RoboMaker, the cloud robotics solution from Amazon.

It is my pleasure to introduce you to Roger Barga. Roger is an expert in computing clouds. First, by working as Group Program Manager for Microsoft Azure, and now as the General Manager of Amazon Web Services for robotics and autonomous services. He is the leader of AWS RoboMaker, the robotics cloud solution created by Amazon to speed up ROS development.

Related links

Posts: 1

Participants: 1

Read full topic

by @RebeccaU Rebecca Ushiroda on November 12, 2019 06:18 AM


Powered by the awesome: Planet