March 23, 2019
New Packages for Indigo 2019-03-23

@tfoote wrote:

We’re happy to announce 3 new packages and 24 updated packages for Indigo.

Thank you to all the maintainers and contributors who have helped make these packages available and keep them updated. Full details are below.

Package Updates for indigo

Added Packages [3]:

Updated Packages [24]:

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:

  • Devon Ash
  • Kevin Hallenbeck
  • Martin Günther
  • Martin Pecka
  • Micho Radovnikovich

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on March 23, 2019 11:41 PM

robot ignite academy

@tyrellcorp wrote:

Hey, I want to make a bipedal robot walk via machine learning. I found the robot ignite academy course and it $40 a month. I have searched for reviews on google but have not across any. Was wondering if any of you have done the course before I commit.

Posts: 1

Participants: 1

Read full topic

by @tyrellcorp brendan browne on March 23, 2019 08:26 PM

ROSshow: View ROS topics in the terminal (updated!)

@dheera wrote:

Have you ever ssh’d into a robot wanting to see if a topic is outputting what it should? Have you ever wished you could get something more meaningful that what you’d get by doing rostopic echo /velodyne_points or rostopic echo /camera/image_raw? Have you ever been annoyed about how much work it takes to fire up a visualization in rviz just to see if a sensor is working? Read on.

I created this more than a year ago but there were some suggestions to make it a ROS node as well as Python 2.x compatibility. Got too busy and never got around to it back then. Well, I think I’ve done that now. It is now a ROS package that you can install. I also added support for several more data types, including CompressedImage, PointCloud2, and time series plots of most std_msgs types.

Please keep the suggestions coming! Contributions welcome too!

For std_msgs types, you’ll get a time series plot, which is great for topics like motor current or voltage.

Posts: 1

Participants: 1

Read full topic

by @dheera Dheera Venkatraman on March 23, 2019 07:58 AM

March 22, 2019
How to: ROS and Reinforcement Learning

@adamd wrote:

Hey everyone, today AWS launched a fantastic tutorial titled: “How to Train a Robot Using Reinforcement Learning”

You will go through the steps to build a robot application. This application will use reinforcement learning to train a robot (TurtleBot 3 Waffle) to drive autonomously towards a stationary robot (TurtleBot 3 Burger). You will learn to train and evaluate the reinforcement learning model in AWS RoboMaker simulation and deploy the model to a physical robot using AWS RoboMaker fleet management.

Check it out here:

Posts: 1

Participants: 1

Read full topic

by @adamd Adam Duncan on March 22, 2019 09:29 PM

March 20, 2019
Announcing MoveIt 1.0

image|690x454

MoveIt has been in beta since 2013 (6 years), but today we’re excited to announce MoveIt is all grown up. We are releasing MoveIt 1.0 for ROS Melodic.

What does this mean for you? The MoveIt maintainer team is moving towards clearer release schedules with better understood API breakage rational. Notably, we are now doing all our development in a master branch rather than the melodic-devel branch, etc. This will allow us to add exciting new features, even if it means we have to break API in certain areas and refactor the code to support new motion planning paradigms. See my Open Letter To MoveIt Community for more reasoning.

It also allows us to break ground on MoveIt 2.0, which will provide support for the exciting ROS 2.0 framework. The port of MoveIt to ROS 2 has already begun, as described in this recent blog post. For a full roadmap of MoveIt versioning, see the MoveIt 1.0 release plan.

What’s New In MoveIt 1.0?

There have been lots of new features being added to MoveIt the past year that we’re really excited about. Beyond features, a ton of code cleanup has occurred (clang-tidy, catkin lint) and we have a lot more code coverage. For more info, see Migration Notes.

Highlights of changes:

Thanks to all our contributors!

MoveIt is a vibrant open source community with a rapidly improving codebase. Our maintainer team is awesome, particularly Robert Haschke and Michael Görner, both hailing from Germany.

We’ve had 158 contributors to date that have made MoveIt 1.0 possible. We’ve come a long way from the early days of MoveIt at Willow Garage. MoveIt is now a huge international effort with contributors from research labs and companies around the world. See our 2017 montage for some of the impressive applications using MoveIt.

Under PickNik Consulting’s guidance, we’re encouraging more people to get involved – including you! Our third year of World MoveIt Day had approximately 310 participants from 13 locations around the globe. Together with Open Robotics, PickNik sponsored three Google Summer of Code students to work on MoveIt last summer. We’ve also put in a ton of effort making MoveIt easier to use, from the MoveIt Setup Assistant 2.0 to new tutorials using the Franka Emika Panda robot.

We hope MoveIt 1.0 continues to support the worldwide open source robotics effort and the ideals of ROS.

by Dave Coleman on March 20, 2019 02:16 AM

March 19, 2019
ROS on the new Jetson Nano with ZED cameras

@Myzhar wrote:

Yesterday Nvidia announced a new amazing Jetson board targeting the maker and the robotics market.
In Stereolabs we tested it and we published a tutorial about how to install ROS and configure it to be used with ZED and ZED Mini stereo cameras.

Let me know what you think about:

Posts: 1

Participants: 1

Read full topic

by @Myzhar Walter Lucetti on March 19, 2019 04:00 PM

Check out gym-gazebo2 and ROS2Learn!

@nzlz wrote:

Hello everyone,

I am software engineer at Acutronic Robotics and I would like to present our latest open-sourced work. We have released gym-gazebo2, an upgraded, real world application oriented version of gym-gazebo, the ROS and Gazebo based Reinforcement Learning (RL) toolkit, which complies with OpenAI’s Gym. This time fully focused on ROS2.

We have also released ROS2Learn, a novel framework for Deep Reinforcement Learning (DRL) in modular robotics, which uses the environments created in gym-gazebo2. We are including training scripts and creating tutorials so that anyone can replicate and improve our results.

The following tutorials will help you get an idea of what you can achieve using our tools.

Join the discussion on reddit or share your thoughts below! We invite everyone in the community to provide us feedback and contribute to both of the projects.

gym-gazebo2: paper, code, tutorials.
ROS2Learn: paper, code, tutorials.

Thanks,
Nestor

Posts: 2

Participants: 2

Read full topic

by @nzlz Nestor Gonzalez on March 19, 2019 09:23 AM

March 18, 2019
2019 ROS COURSE Ultimate Guide : Implement ROS on all Robots

@Muhammad_Luqman wrote:

I have been working on robots from couple of years and after graduation I made a course that contains all the ROS essential you need to work using ROS.

This course is not just simulation Implementation on hardware as well I will be Using Cheap Robots (any one can buy) to be controlled by ROS , including raspberry PI , esp-8266 and 2 wheel plastic car with sensors

After this course you can work with ROS so easily and will start making your upcoming robotics projects powered with ROS.

packages used are
-rviz
-gazeebo
-turtlebot3

Find Course on this --> !LINK!

Posts: 1

Participants: 1

Read full topic

by @Muhammad_Luqman Muhammad Luqman on March 18, 2019 06:20 PM

March 17, 2019
Announcing teleop_keyboard_omni3 package

@YugAjmera wrote:

Hi everyone,
I am pleased to announce the release of a new package: teleop_keyboard_omni3.

I was working with three-wheeled holonomic robots and wanted to control it using a keyboard, something similar to teleop_twist_keyboard. So I have created teleop_keyboard_omni3 package which is a generic keyboard teleop for 3 wheeled omnidirectional robots.

The package lets to control your robot in both normal as well as holonomic(strafing) modes. I have tested it and it works awesome!

The package`s wiki page : ROS Wiki . I have also included the theory(motion analysis) used while creating the package.

Please let me know if you have any feedback, suggestions or any trouble using the package.

Cheers!
Yug Ajmera

Posts: 1

Participants: 1

Read full topic

by @YugAjmera Yug Ajmera on March 17, 2019 11:25 PM

March 15, 2019
AWS RoboMaker - Free Workshop in NYC on March 29

@ajmac wrote:

Hello ROS community. I’m a Solutions Architect working with the AWS RoboMaker service and the team working on contributions to ROS2. I’m writing to announce an exciting meetup I’ll be hosting. If you’re interested in learning more about ROS, Amazon Web Services, or both, you might be interested in attending!

At AWS RoboMaker Day, you’ll learn about robotics and machine learning within AWS, get an introduction to working with Robot Operating System, and get hands on with RoboMaker by building a robotics application that will “Find Fido” using image detection. You’ll have the chance to test it virtually in simulation to iterate and fine tune your code. You’ll then complete the challenge by deploying the application to a physical robot to see if it can complete its mission.

The workshop is free and open to anyone. You can sign up here: https://awsrobomakerday.splashthat.com/

I’m happy to answer any questions you might have, and I hope to see you there!

Allan MacInnis

Posts: 5

Participants: 3

Read full topic

by @ajmac Allan MacInnis on March 15, 2019 11:17 PM

March 14, 2019
Patch release and new packages for ROS 2 Crystal Clemmys 2019-03-14

@nuclearsandwich wrote:

Crystal’s third patch release is here!

The changes I’m most excited about:

  • Actions are now available in rclpy. You can get the details from ros2/rclpy#257.
  • If you’re interested in using log4cxx for your logging needs, the rcl_logging_log4cxx package has now been released. Using this package naturally relies on log4cxx, so refer to the installation instructions for your platform to get it.

The changes in sros2 introduce a new dependency on the rosdep key: python3-lxml
The installation documentation has been updated but I’ll highlight the changes here:

Depending on the platform, users may need to get the additional dependency:

You can check out full list of changes in the patch release tracking issue. We’ve also discovered some issues in Fast-RTPS that are being added to the Known issues section of the Crystal Clemmys release page. I’m linking the section now even though they won’t appear until the next documentation rebuild. This is the change for you first viewers.

Package Updates for crystal

Added Packages [11]:

  • ros-crystal-behaviortree-cpp-v3: 3.0.4-0
  • ros-crystal-behaviortree-cpp-v3-dbgsym: 3.0.4-0
  • ros-crystal-examples-rclpy-minimal-action-client: 0.6.3-0
  • ros-crystal-examples-rclpy-minimal-action-server: 0.6.3-0
  • ros-crystal-nav2-common: 0.1.7-0
  • ros-crystal-py-trees-ros-interfaces: 1.0.0-0
  • ros-crystal-py-trees-ros-interfaces-dbgsym: 1.0.0-0
  • ros-crystal-rcl-logging-log4cxx: 0.2.0-0
  • ros-crystal-rcl-logging-log4cxx-dbgsym: 0.2.0-0
  • ros-crystal-rqt-action: 1.0.1-0
  • ros-crystal-rqt-topic: 1.0.0-0

Updated Packages [165]:

  • ros-crystal-action-msgs: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-action-msgs-dbgsym: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-ament-clang-format: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-cmake: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-auto: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-clang-format: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-cmake-copyright: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-cmake-core: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-cppcheck: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-cmake-cpplint: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-cmake-export-definitions: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-export-dependencies: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-export-include-directories: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-export-interfaces: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-export-libraries: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-export-link-flags: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-flake8: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-cmake-gmock: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-gtest: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-include-directories: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-libraries: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-lint-cmake: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-cmake-nose: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-pclint: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-cmake-pep257: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-cmake-pep8: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-cmake-pyflakes: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-cmake-pytest: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-python: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-target-dependencies: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-test: 0.6.0-4 -> 0.6.1-0
  • ros-crystal-ament-cmake-uncrustify: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-cmake-xmllint: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-copyright: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-cppcheck: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-cpplint: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-flake8: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-lint-auto: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-lint-cmake: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-lint-common: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-pclint: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-pep257: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-pep8: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-pyflakes: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-uncrustify: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-ament-xmllint: 0.6.3-0 -> 0.6.4-0
  • ros-crystal-builtin-interfaces: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-builtin-interfaces-dbgsym: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-costmap-queue: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-dwb-controller: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-dwb-controller-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-dwb-core: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-dwb-core-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-dwb-critics: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-dwb-critics-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-dwb-msgs: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-dwb-msgs-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-dwb-plugins: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-dwb-plugins-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-examples-rclcpp-minimal-action-client: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclcpp-minimal-action-client-dbgsym: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclcpp-minimal-action-server: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclcpp-minimal-action-server-dbgsym: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclcpp-minimal-client: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclcpp-minimal-client-dbgsym: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclcpp-minimal-composition: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclcpp-minimal-composition-dbgsym: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclcpp-minimal-publisher: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclcpp-minimal-publisher-dbgsym: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclcpp-minimal-service: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclcpp-minimal-service-dbgsym: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclcpp-minimal-subscriber: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclcpp-minimal-subscriber-dbgsym: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclcpp-minimal-timer: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclcpp-minimal-timer-dbgsym: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclpy-executors: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclpy-minimal-client: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclpy-minimal-publisher: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclpy-minimal-service: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-examples-rclpy-minimal-subscriber: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-gazebo-dev: 3.1.0-0 -> 3.2.0-0
  • ros-crystal-gazebo-msgs: 3.1.0-0 -> 3.2.0-0
  • ros-crystal-gazebo-msgs-dbgsym: 3.1.0-0 -> 3.2.0-0
  • ros-crystal-gazebo-plugins: 3.1.0-0 -> 3.2.0-0
  • ros-crystal-gazebo-plugins-dbgsym: 3.1.0-0 -> 3.2.0-0
  • ros-crystal-gazebo-ros: 3.1.0-0 -> 3.2.0-0
  • ros-crystal-gazebo-ros-dbgsym: 3.1.0-0 -> 3.2.0-0
  • ros-crystal-gazebo-ros-pkgs: 3.1.0-0 -> 3.2.0-0
  • ros-crystal-lifecycle-msgs: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-lifecycle-msgs-dbgsym: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-nav-2d-msgs: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav-2d-msgs-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav-2d-utils: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav-2d-utils-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-amcl: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-amcl-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-bringup: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-bt-navigator: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-bt-navigator-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-costmap-2d: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-costmap-2d-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-dwb-controller: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-dynamic-params: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-dynamic-params-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-map-server: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-map-server-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-mission-executor: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-mission-executor-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-motion-primitives: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-motion-primitives-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-msgs: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-msgs-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-navfn-planner: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-navfn-planner-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-robot: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-robot-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-simple-navigator: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-simple-navigator-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-tasks: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-tasks-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-util: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-util-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-voxel-grid: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-voxel-grid-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-world-model: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-nav2-world-model-dbgsym: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-navigation2: 0.1.5-0 -> 0.1.7-0
  • ros-crystal-python-cmake-module: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-rcl-interfaces: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-rcl-interfaces-dbgsym: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-rcl-logging-noop: 0.1.0-0 -> 0.2.0-0
  • ros-crystal-rcl-logging-noop-dbgsym: 0.1.0-0 -> 0.2.0-0
  • ros-crystal-rclpy: 0.6.2-0 -> 0.6.3-1
  • ros-crystal-rclpy-dbgsym: 0.6.2-0 -> 0.6.3-1
  • ros-crystal-ros1-bridge: 0.6.1-1 -> 0.6.2-0
  • ros-crystal-ros1-bridge-dbgsym: 0.6.1-1 -> 0.6.2-0
  • ros-crystal-ros1-rosbag-storage-vendor: 0.0.5-0 -> 0.0.6-0
  • ros-crystal-ros2bag: 0.0.5-0 -> 0.0.6-0
  • ros-crystal-rosbag2: 0.0.5-0 -> 0.0.6-0
  • ros-crystal-rosbag2-bag-v2-plugins: 0.0.5-0 -> 0.0.6-0
  • ros-crystal-rosbag2-converter-default-plugins: 0.0.5-0 -> 0.0.6-0
  • ros-crystal-rosbag2-converter-default-plugins-dbgsym: 0.0.5-0 -> 0.0.6-0
  • ros-crystal-rosbag2-dbgsym: 0.0.5-0 -> 0.0.6-0
  • ros-crystal-rosbag2-storage: 0.0.5-0 -> 0.0.6-0
  • ros-crystal-rosbag2-storage-dbgsym: 0.0.5-0 -> 0.0.6-0
  • ros-crystal-rosbag2-storage-default-plugins: 0.0.5-0 -> 0.0.6-0
  • ros-crystal-rosbag2-storage-default-plugins-dbgsym: 0.0.5-0 -> 0.0.6-0
  • ros-crystal-rosbag2-test-common: 0.0.5-0 -> 0.0.6-0
  • ros-crystal-rosbag2-tests: 0.0.5-0 -> 0.0.6-0
  • ros-crystal-rosbag2-transport: 0.0.5-0 -> 0.0.6-0
  • ros-crystal-rosbag2-transport-dbgsym: 0.0.5-0 -> 0.0.6-0
  • ros-crystal-rosgraph-msgs: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-rosgraph-msgs-dbgsym: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-rosidl-generator-py: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-rosidl-typesupport-c: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-rosidl-typesupport-c-dbgsym: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-rosidl-typesupport-cpp: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-rosidl-typesupport-cpp-dbgsym: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-shared-queues-vendor: 0.0.5-0 -> 0.0.6-0
  • ros-crystal-sqlite3-vendor: 0.0.5-0 -> 0.0.6-0
  • ros-crystal-sros2: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-sros2-cmake: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-teleop-twist-keyboard: 2.1.1-1 -> 2.2.0-0
  • ros-crystal-test-msgs: 0.6.2-0 -> 0.6.3-0
  • ros-crystal-test-msgs-dbgsym: 0.6.2-0 -> 0.6.3-0

Removed Packages [1]:

  • ros-crystal-nav2-system-tests

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 B9 Team
  • Amazon B9
  • Brian Wilcox
  • Carl Delsey
  • Carlos Orduno
  • Chris Lalancette
  • Daniel Stonier
  • David V. Lu!!
  • Davide Faconti
  • Dirk Thomas
  • Jacob Perron
  • Jose Luis Rivero
  • Juan Pablo Samper
  • Karsten Knese
  • Michael Carroll
  • Michael Ferguson
  • Michael Jeronimo
  • Mikael Arguedas
  • Scott K Logan
  • Shane Loretz
  • Steve Macenski
  • Steven! Ragnarok
  • Tully Foote
  • William Woodall

Posts: 2

Participants: 1

Read full topic

by @nuclearsandwich Steven! Ragnarök on March 14, 2019 11:50 PM

New packages for Lunar 2019-03-14

@clalancette wrote:

We’re happy to announce the next update for ROS Lunar. We have 36 new packages as well as 108 updated packages.

As always, thanks to all of the maintainers and contributors who help make these updates possible!

Full details are below.

Added Packages [36]:

Updated Packages [108]:

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
  • Atsushi Watanabe
  • AutonomouStuff Software Development Team
  • Daniel Koch
  • David Feil-Seifer
  • David Uhm
  • David V. Lu!!
  • Davide Faconti
  • Devon Ash
  • Felix Ruess
  • Isaac I.Y. Saito
  • Jack O’Quin
  • Josh Whitley
  • Kei Okada
  • Kevin Hallenbeck
  • Konstantin Schauwecker
  • Kris Kozak
  • Lennart Puck
  • Marc Alban
  • Martin Günther
  • Martin Pecka
  • Michael Lehning
  • Michele Colledanchise
  • Monika Florek-Jasinska
  • P. J. Reed
  • Paul Bovbel
  • Péter Fankhauser
  • Sam Pfeiffer
  • Tom Moore
  • Vladimir Ermakov
  • Yohei Kakiuchi

Posts: 1

Participants: 1

Read full topic

by @clalancette Chris on March 14, 2019 12:29 PM

ROS Developers LIVE-Class #50: Autonomous Robot Navigation with ROS

@Maricho_CM wrote:

ROS Developers LIVE-Class #50: Autonomous Robot Navigation with ROS

  • Date&Time: Mar 19th, 2019 | 6pm to 7pm · CET

About
On the previous Live Class we learnt how to create a map and localize a robot on it. In this class we are going to learn how to make a robot use that map to plan paths, move autonomously on the environment and avoid obstacles, using the ROS navigation stack and the move_base. We will use a simulation but also a real Summit XL robot.

Robots used in this class

For this class we are going to use the Summit XL by Robotnik . You can find more information about Summit XL robot here.

Posts: 1

Participants: 1

Read full topic

by @Maricho_CM Marisol Cm on March 14, 2019 11:29 AM

March 13, 2019
ROSCon 2019: registration open

@gerkey wrote:

We’re happy to announce that registration for ROSCon 2019 is now open!

Note: Early Student and Early General tickets are limited in quantity and will be offered first come, first served until they sell out or until 24 August 2019, whichever comes first.

We’re looking forward to a great event in Macau. The event website has more information on the venue and key dates.

Thank you again to our Platinum Sponsor: Amazon, and to all our Gold Sponsors: Acutronic Robotics, ADLINK, Apex.ai, Clearpath Robotics, eProsima, Fetch Robotics, iRobot, Microsoft, Rapyuta Robotics, ROBOTIS, Silexica, Tier IV, Toyota Research Institue, and Ubuntu.

Questions or requests can be sent to the organizing committee: roscon-2019-oc@openrobotics.org.

– Your friendly neighborhood ROSCon Organizing Committee

Posts: 1

Participants: 1

Read full topic

by @gerkey gerkey on March 13, 2019 01:05 AM

March 11, 2019
Abstract Submission to Springer Book on ROS Volume 5

@Anis_Koubaa wrote:

Hello,

The deadline to submit abstracts to the Springer book on ROS is March 15, 2019.
If you have good contributions to ROS, then this book is the best place to submit your work.
This year we have a special focus on the emerging ROS2, but submissions on ROS1 are still welcomed.

For more details, please refer to
http://www.riotu-lab.org/rosbook/

The four first volumes were quite successful and provided a great added value to the community. The previous volumes were in the top 25% most downloadable books in Springer, based on Springer annual analytics.

All the volumes, including the coming fifth volume, are indexed in SCOPUS database.

Looking forward to receiving your submissions.

image

Thanks
Anis

Posts: 3

Participants: 2

Read full topic

by @Anis_Koubaa Anis Koubaa on March 11, 2019 03:58 PM

March 08, 2019
Announcing MoveIt 1.0

@davetcoleman wrote:

MoveIt has been in beta since 2013 (6 years), but today we’re excited to announce MoveIt is all grown up. We are releasing MoveIt 1.0 for ROS Melodic.

What does this mean for you? The MoveIt maintainer team is moving towards clearer release schedules with better understood API breakage rational. Notably, we are now doing all our development in a master branch rather than the melodic-devel branch, etc. This will allow us to add exciting new features, even if it means we have to break API in certain areas and refactor the code to support new motion planning paradigms. See my Open Letter To MoveIt Community for more reasoning.

It also allows us to break ground on MoveIt 2.0, which will provide support for the exciting ROS 2.0 framework. The port of MoveIt to ROS 2 has already begun, as described in this recent blog post. For a full roadmap of MoveIt versioning, see the MoveIt 1.0 release plan.

What’s New In MoveIt 1.0?

There have been lots of new features being added to MoveIt the past year that we’re really excited about. Beyond features, a ton of code cleanup has occurred (clang-tidy, catkin lint) and we have a lot more code coverage. For more info, see Migration Notes.

Highlights of changes:

Thanks to all our contributors!

MoveIt is a vibrant open source community with a rapidly improving codebase. Our maintainer team is awesome, particularly Robert Haschke and Michael Görner, both hailing from Germany.

We’ve had 158 contributors to date that have made MoveIt 1.0 possible. We’ve come a long way from the early days of MoveIt at Willow Garage. MoveIt is now a huge international effort with contributors from research labs and companies around the world. See our 2017 montage for some of the impressive applications using MoveIt.

Under PickNik Consulting’s guidance, we’re encouraging more people to get involved – including you! Our third year of World MoveIt Day had approximately 310 participants from 13 locations around the globe. Together with Open Robotics, PickNik sponsored three Google Summer of Code students to work on MoveIt last summer. We’ve also put in a ton of effort making MoveIt easier to use, from the MoveIt Setup Assistant 2.0 to new tutorials using the Franka Emika Panda robot.

We hope MoveIt 1.0 continues to support the worldwide open source robotics effort and the ideals of ROS.

Posts: 3

Participants: 2

Read full topic

by @davetcoleman Dave Coleman on March 08, 2019 07:00 PM

[meetings] Call for tutorials: Second ROS Developers Conference 2019

@Maricho_CM wrote:

The 2nd ROS Developers Conference
JUNE 15 -16, 2019
Online
Website: http://www.rosdevcon.com

[ OVERVIEW ]

ROS Developers Conference is an online conference for ROS developers worldwide. The conference aims to connect ROS developers around the world without geographical restrictions and to advance ROS levels through real-time practice.

We will host eight top ROS developers to give tutorials of real ROS projects: during the conference, all participants will program together at the same time.

  • All the participants will practice at the same time with the speaker along the conference.
  • No installation of anything required. Only require a computer and internet connection. Any type of computer will work.
  • All the participants will have full access to the ROS development studio for programming
  • All participants will receive a pdf document with all the steps described during the conference
  • All the participants will have access to all packages with pre-defined code
  • All the participants will receive a copy of the ROS2 Basics book
  • Each speech will be 30 minutes plus 10 minutes Q&A.

[ CALL FOR TUTORIALS ]

  • The proposals must be sent to this address: tutorial@rosdevcon.com
  • Submission deadline: April 30, 2019
  • The tutorial should last 30 mins + 10 mins Q&A

Tutorials can target any field of ROS or ROS2 and should focus on practice, in order to provide a real practical conference for participants and to exchange results and ideas. The submission of a tutorial must contain the following information:

  • Title
  • Speaker Information
  • A short statement of objectives
  • Special requests (equipment or other issues)

If your tutorial is accepted, you will have to prepare a ROSject containing the following material (with our support):

  • A notebook with the tutorial
  • Package with pre-defined code for participants

[ ORGANIZERS ]

The Construct (http://www.theconstructsim.com/)
You can contact us with questions and doubts here: info@rosdevcon.com

Posts: 1

Participants: 1

Read full topic

by @Maricho_CM Marisol Cm on March 08, 2019 06:30 PM

March 06, 2019
New Packages For Indigo 2019-03-06

@tfoote wrote:

We’re happy to announce 37 updated packages for Indigo Igloo.

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

Full details are below.

Package Updates for indigo

Added Packages [0]:

Updated Packages [37]:

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 Tiderko
  • Davide Faconti
  • Francois Pomerleau
  • Kei Okada
  • Marc Alban
  • Péter Fankhauser
  • Ryohei Ueda
  • Stéphane Magnenat
  • TORK
  • Yusuke Furuta
  • furuta

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on March 06, 2019 08:09 AM

March 05, 2019
Open Robotics accepted for Google Summer of Code 2019

From Open Robotics

Do you want to spend the summer coding on Gazebo or ROS? Open Robotics has been accepted for GSoC and we are looking for talented students who want to participate as remote interns.

Accepted students will participate in real-world software development, contributing to open source robotics projects and engaging with the global robotics community, all while getting paid.

Check out our GSoC site and don't forget to visit our ideas page, which lists projects that we're interested in. Feel free to ask questions and propose suggestions at gsoc@openrobotics.org. The student application period opens on March 25th and closes April 9th

Get ready for a robotics coding summer!

by Tully Foote on March 05, 2019 08:37 PM

GSoC and the fate of OpenEmbedded

@braineniac wrote:

Hello! I am currently writing an application for the upcoming GSoC which involves ROS2 and OpenEmbedded. Is it fine if I go into detail about the experiences and my vision for ROS and OpenEmbedded? I would be interested in discussing my ideas and how they line up with OSRF, I just dont know with whom and where exactly. Also what part of that vision could be implemented during the GSoC. I would stay on after that and maintain/update regularly to achieve them.

Posts: 14

Participants: 5

Read full topic

by @braineniac Daniel Hammer on March 05, 2019 12:45 PM

March 04, 2019
New Packages for Kinetic 2019-03-04

@tfoote wrote:

We’re happy to announce 13 new packages and 71 updated packages for ROS Kinetic.

Thank you to all the maintainers who helped make this possible as well as the many more contributors. Full details are below.

Package Updates for kinetic

Added Packages [13]:

Updated Packages [71]:

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 Gutenkunst
  • Alexander Tiderko
  • AutonomouStuff Software Development Team
  • Daniel Koch
  • Daniel Stonier
  • Davide Faconti
  • Devon Ash
  • Kei Okada
  • Luiz Ricardo Douat
  • Mike Purvis
  • Musa Morena Marcusso Manhaes
  • Péter Fankhauser
  • Ryohei Ueda
  • Shadow Robot’s software team
  • Shaun Edwards
  • Steve Macenski
  • Tokyo Opensource Robotics Kyokai (TORK) Developer Team
  • Tokyo Opensource Robotics Kyokai(TORK) Developer Team
  • Wolfgang Merkt
  • Yohei Kakiuchi
  • Youhei Kakiuchi

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on March 04, 2019 07:23 PM

New packages for Melodic 2019-03-04

@clalancette wrote:

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

As always, thanks to all of the maintainers and contributors who help make these updates possible! Special thanks to @martiniil for a timely pilz release to fix a regression.

Full details are below.

Package Updates for melodic

Added Packages [90]:

Updated Packages [86]:

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 Gutenkunst
  • Alexander Moriarty
  • Alexander Tiderko
  • AutonomouStuff Software Development Team
  • Bence Magyar
  • Carlos Aguero
  • Chad Rockey
  • Christopher Berner
  • Daniel Koch
  • Daniel Stonier
  • David V. Lu!!
  • Davide Faconti
  • Enrique Fernandez
  • Eric Relson
  • Kei Okada
  • Konstantin Schauwecker
  • Kris Kozak
  • Marc Alban
  • Masaru Morita
  • Michael Ferguson
  • Michael Lehning
  • P. J. Reed
  • Pilz GmbH and Co. KG
  • Pyo
  • Péter Fankhauser
  • ROS Orphaned Package Maintainers
  • Russell Toris
  • Ryohei Ueda
  • Sachin Chitta
  • Shaun Edwards
  • Tom Moore
  • Vincent Rousseau
  • Wolfgang Merkt
  • Yohei Kakiuchi
  • Youhei Kakiuchi
  • Yusuke Furuta
  • furuta

Posts: 1

Participants: 1

Read full topic

by @clalancette Chris on March 04, 2019 06:40 PM

ROS with Google Summer of Code 2019?

@thet_paing wrote:

Hello ,
I’ve heard GSoC 2019 will accept Registration in this coming March 26. I’m interested and wanna apply to this program. But, as my programming experiences , I was more familiar with ROS than other programming fields(like Android,Web,etc) because I’m a Mechanical Engineer. I searched on GSoC proposals about ROS and I found posts (dealing with MoveIt! & GSoC) in here. Exactly , it gave me hope :smile:

So, may I know if any chance for ROS + GSoC collaboration this year and is there anyone who participated in GSoC with ROS projects ? (I wanna ask about experiences) Thanks a lot.

With Respect ,
Paing
Myanmar

Posts: 4

Participants: 2

Read full topic

by @thet_paing Thet Paing on March 04, 2019 04:51 AM

March 01, 2019
ROS TSC Meeting Notes 2019-02-21

@tfoote wrote:

ROS TSC Meeting Notes February 21st, 2019

  • Attendees:
    • Dirk, Tully, Brian (Open Robotics)
    • Peter (Intel)
    • Karsten (Bosch)
    • Victor (Acutronic)
    • Jaime (eProsima)
    • Allison (TRI)
    • Dejan (Apex)
    • Rutvik (Amazon)
    • Seonman (LGE)
    • Matt D & Jon Smereka (TARDEC)
  • [10 min] [Brian] New member introductions:
    • [Victor] Acutronic
      • 2 minute company overview
    • [Jaime] eProsima
      • 2 minute company overview
  • [2 min] [Brian] ROS trademark status update
    • Application is mostly prepared, with a few remaining questions. Draft “descriptions of goods and services” is ready.
    • We may need more details on ROS logo usage in some classes, including first dates.
  • [2 min] [Dirk] DCO bot update
    • Some limitations when using the web UI to edit [e.g. #102]
    • Want to add more information to the repos CONTRIBUTING.md files before enabling globally
    • Amazon has successfully used it.
  • [5 min] [Brian] Elevator pitch
    • Why ROS 2? Draft shared by Brian, with summary bullets being:
    • Designed for production
  • Multi-platform
  • No vendor lock-in
  • Built on open standards
  • Permissive open source license
  • Global community
    • Suggestions to be added / integrated:
      • Tools, libraries, capabilities
      • Ecosystem
      • Industry grade vs. production, with respect to quality
      • Platform implies hardware (e.g., specific SBCs, BSPs) in automotive
      • Highlight companies’ support (e.g., via TSC)
      • Cross-domain platforms (not just ground), planes, quads, orbiting satellites, subterranean robots
      • Accelerating time to market, should be faster than proprietary solutions
    • Brian to circulate updated draft among TSC.
  • [5 min] [Dirk] Dashing update:
  • WG updates
    • [5 min] [Peter (in lieu of Matt H.)] Navigation
      • Q: Replacing custom actions with standard actions planned?
      • Q: Replacing custom dyn reconf with standard parameters (once they support ranges) planned?
      • Matt on vacation – look for offline update
    • [5 min] [Rutvik] Security
      • Primary work stream was for threat model, picked up again, working on first draft of document
      • Working on reference architecture based on TurtleBot
    • [5 min] [Dejan] Real-time and safety
      • Real-time status and goals tracked at https://gitlab.com/AutowareAuto/AutowareAuto/issues/65
      • Q: What is latency target?
        • Focused on example automotive use case
      • Q: Behavior can be very different on hardware platforms. There’s not a lot of testing on specific hardware.
        • Building on prior work by OSADL (empirical demonstration of latencies in RT-PREEMPT-patched kernel on specific hardware)
      • Safety WG will be picked up by Geoff Biggs, expect a Discourse post to start this effort.
    • [5 min] [Karsten] Embedded
  • [5 min] [Dejan] ROS 2 integration test framework
  • [5 min] [Victor] From Matt H.: Acutronic and PickNik announced a partnership on Discourse, beginning work on MoveIt! 2.0 on ROS2.
    • Q: Can they give us a brief overview of their plans and schedule?
    • Q: Will it be done in time for Dashing release?
      • Yes, its targeted for Dashing release
      • It’s on the Dashing ticket.
    • Q: Are there areas they are seeking help?
    • Q: Does this include porting ROS control?
      • Targeting minimal viable option. Might not be fully ported. There may be more use cases for more of ros_control that would be needed, but collaborators to fill that out would be appreciated.
    • Q: Does this include a refactor to take advantage of new features or a direct port?
      • Trying to take long run, leaving it up to Dave’s judgement, to still meet the deadline.
      • Would like to hear about more use cases.
  • [5 min] [Karsten] diagnostics pull request status
    • https://github.com/ros/diagnostics/pull/94
    • We were wondering how we can help pushing this PR in a review-able state. Bosch is willing to help but we want to double check with Persistent / Amazon first.
      • Amazon no longer actively working on this, would be willing to collaborate.
      • Bosch will plan to comment on the existing PR and make a set of new smaller PRs to replace them
  • [10 min] [Brian] Need for regular dev call and/or new chat system?
    • Discuss recent threads from Discourse:
    • Dejan: See two challenges. When actions were designed there wasn’t a concrete use case. Their use case has a specific corner that wasn’t in the generic design. Github is good and open/visible. Slack is horrible, only good if you need an answer in 5 minutes. Everything should have a good design doc. Adding more tooling isn’t solving the problem, you need to know what you want to do.
    • Karsten: Seconded new system will just cause more notification overloads. Highlight Deanna’s ROSCon talk, proposals, designs, etc.
    • Brian: Previous regular dev call. Worked well, but had a problem of it really just another way for people to make feature requests. Maybe new scope to say it’s only for information sharing.
    • Rutvik: Maybe an office hours model. Find a way to spread design feedback burden. Amazon would be interested in staffing an office hours.
    • Dirk: Effective deep discussions are hard with high latency written communication channels. Might make sense to have specific calls for focused topics.
    • Allison: Regular scheduled is easier for people to keep up with and find. Cartographer open house seems to work well. Mostly advice not bug fixing/reporting.
    • Dejan: Other projects have community managers who scan through tickets for unsolved issues, and ping people. Sometimes start discussions about what’s the slowdown.
      • Brian: Yeah we are distributing that role among our team.
      • Rutvik: +1 for good job from Open Robotics, but see bandwidth limitations
    • Peter: A developer conference, more working groups and discussions not as much of a presentation out like ROSCon.
  • [10 min] [Brian] New TSC applicant
    • Follow up questions, please email Brian directly. We’ll call for an asynchronous vote in the next week or two.

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on March 01, 2019 06:12 PM

February 22, 2019
New Packages for Kinetic 2019-02-22

@tfoote wrote:

We’re happy to announce 25 new packages and 159 updated packages for ROS Kinetic. There were also 2 removed packages.

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

Full details are below:

Package Updates for kinetic

Added Packages [25]:

Updated Packages [159]:

Removed Packages [2]:

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
  • Alexander Gutenkunst
  • Andres Palomino
  • Bence Magyar
  • Daniel Stonier
  • David Uhm
  • David V. Lu!!
  • Davide Faconti
  • Felix Ruess
  • Isaac I.Y. Saito
  • Kei Okada
  • Konstantin Schauwecker
  • Kris Kozak
  • Krzysztof Żurad
  • Luiz Ricardo Douat
  • Marc Alban
  • Martin Pecka
  • Masaru Morita
  • Michael Lehning
  • Monika Florek-Jasinska
  • Musa Morena Marcusso Manhaes
  • P. J. Reed
  • Pyo
  • Ryohei Ueda
  • Sachin Chitta
  • TORK
  • Timo Röhling
  • Tom Moore
  • Vincent Rousseau
  • Vladimir Ermakov
  • Wolfgang Merkt
  • Yannick Roberts
  • Yohei Kakiuchi
  • YoheiKakiuchi
  • Youhei Kakiuchi
  • Yuki Furuta
  • Yusuke Furuta
  • furuta

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on February 22, 2019 11:46 PM


Powered by the awesome: Planet