October 19, 2019
Requesting a "Security" Category

@vmayoral wrote:

The same way we have a QA, would it be possible to get a Security category please?

Ping @tfoote, @dirk-thomas, @wjwwood, @nuclearsandwich and other folks managing discourse.

Posts: 1

Participants: 1

Read full topic

by @vmayoral Víctor Mayoral Vilches on October 19, 2019 07:09 AM

October 18, 2019
ROS 2 TSC Meeting Minutes: 2019-10-17

@gerkey wrote:

ROS 2 TSC Meeting Minutes: 2019-10-17

  • Attendees
    • Southwest Research Institute, representing CCDC GVSC - Jerry Towler
    • Samsung Research America - Steve Macenski
    • ADLINK - Joe Speed
    • Amazon - Adam Duncan, Thomas Moulard, Aaron Blasdel
    • eProsima - Jaime Martin Losa
    • Toyota Research Institute - Toffee Albina
    • Bosch - Karsten Knese
    • Open Robotics - Brian Gerkey, Dirk Thomas, Tully Foote
    • Tier IV - Geoff Biggs
    • Intel - Matt Hansen
    • LG Electronics - Brian Shin
    • Microsoft - Sean Yen
  • Old business
    • [Hansen] Follow up on MoveIt2 - There is some good news that Picknik has secured some funding to begin working on the port again, but there is still help needed. We at Intel are committed to contributing to the port, but would like a call to action from other TSC members to also commit some resources to helping.
      • Plan to meet and discuss at ROSCon
      • Hansen to start a discussion on Discourse looking for help.
    • [Speed] Edge AI WG status
      • Steve, Adam, Geoff, Tully, Joe wrote proposal. Will post on discourse next week to get input & solicit interest
    • [Duncan] Tooling WG status
      • Discuss later in this meeting
    • [Duncan] Development/Release framework
      • PR to REP in progress: https://github.com/ros-infrastructure/rep/pull/209
      • TSC and everyone invited to review and offer feedback
      • Elevator pitch: if a previously released package is building and testing successfully, then no developer bloom-type action should be required to automatically include it in a new “rolling” distro.
    • [Gerkey] In-person TSC informal gathering at ROSCon
      • Set for Oct 30th @ 1715-1815, location TBD (bar/lounge nearby workshop location, Joe is buying a round)
        • Gerkey to send out location and calendar invite before then
  • New business
  • Recurring business
    • Eloquent release status
      • [Thomas] API and feature freeze for core packages planned for tomorrow Oct. 18th
      • [Gerkey/Thomas] Let’s all review the Eloquent ticket
      • [Albina] TRI continues to work with OSRC on the Eloquent tasks they have on their plate
      • [Hansen] How can we flag blockers for Eloquent?
        • If you see something that you consider to be a blocker, comment on that ticket (wherever it lives) to assert that position (e.g., “This issue is a blocker for Eloquent; please escalate priority to address.”).
        • Should we collect a list of Eloquent blockers somewhere and if so, how and where?
          • Gerkey to look into this. Foote suggests working with the ROS Boss.
      • Apex.AI updates for the last month are listed here: https://github.com/ros2/ros2/issues/734#issuecomment-519425530 => Update 2019-Oct-17
      • AWS: Recent updates:
        https://github.com/ros2/ros2/issues/734#issuecomment-518482696
      • Tier IV:
        • Tier IV has contracted with a real-time embedded software specialist company to provide 3 FTEs to work on real-time and deterministic execution for ROS 2. We expect them to get up to speed over the next few months, so they will not be able to contribute to Eloquent. We will coordinate their work via the real-time WG.
        • Tier IV’s efforts to bring Debian to Tier 2 status are starting to bear fruit but there are still some catches.
          • Unable to compile any GUI tools. The reason is under investigation.
          • Unsure if we need our own Connext DDS license to do binaries and tests for those parts of the stack: Adding Debian as a Tier 2 platform
      • ADLINK: recent updates, ROS 2 E developer improvements https://github.com/ros2/ros2/issues/734#issuecomment-520542532
      • ePROSIMA
    • Working group updates
      • [Geoff] Safety
        • Working group regular participant numbers have shrunk to two
        • But we have a Plan!
        • Will focus our activities on producing sample ROS structures for common safety patterns (as discussed in previous TSC meeting).
        • A project has been acquired courtesy of Tully, where we will start producing content. It is hoped that by starting to produce content we will kick-start some discussion and further contributions from new people.
      • [Dejan] Real-time

Posts: 2

Participants: 2

Read full topic

by @gerkey gerkey on October 18, 2019 10:02 PM

RFC on REP-2002 : A Rolling ROS 2 release

@nuclearsandwich wrote:

As we iterate on the ROS release schedule with ROS 2, I’ve started a proposal for how a rolling ROS 2 distribution might work. Please take a look at the draft of REP-2002 and give it your feedback: https://github.com/ros-infrastructure/rep/pull/209.

PS, you can view the latest state of the draft REP rendered on GitHub with this link.

Posts: 1

Participants: 1

Read full topic

by @nuclearsandwich Steven! Ragnarök on October 18, 2019 09:24 PM

Participants wanted for a survey on Robotics Simulation!

@ChrisTimperley wrote:

Have you ever used a robotics simulator? Do you have ideas for how robotics simulators might be improved? We want to hear from you! We are a group of software engineering researchers at Carnegie Mellon University trying to better understand why and how robotics developers use simulation when developing and testing their systems.

Simulation holds the potential to provide an automated, cost-effective, and scalable alternative to the manual and expensive process of field testing. Numerous companies in the autonomy sector, such as Uber, NVIDIA, and Waymo, have begun to use simulation on a large scale to aid the testing and development of their products.

Motivated by this potential, we want to learn why, when, and how developers are using simulation to develop and test their robotics software, and the reasons that developers opt not to use simulation. We hope that the results of our study can be used to provide guidance to developers and researchers on building the next generation of simulation platforms that better serve the needs of developers.

If you are interested in participating in our study, please follow this link: https://www.surveymonkey.com/r/88GBDVY

Posts: 1

Participants: 1

Read full topic

by @ChrisTimperley Chris Timperley on October 18, 2019 09:05 PM

Contribute to ros_map - the crowd sourced ROS users map

@DLu wrote:

tldr: Increase your group’s visibility on the local ROS scene by adding it to the ros_map

It is no secret that I like aggregating data. A few years ago, I started a crowd-sourced map for the purpose of helping people find other ROS users in their area. This is your occasional reminder to add your group to the map, which could help you find other people/companies/schools using ROS in your area. You might find someone to hire, or someone to hire you.

But the map is only as good as its data. You can contribute via creating a pull request on the data itself. I even added a command line script so you don’t even have to manually look up your lat/long.

Posts: 1

Participants: 1

Read full topic

by @DLu David!! on October 18, 2019 08:25 PM

New packages for ROS 2 Crystal 2019-10-18

@nuclearsandwich wrote:

I’m happy to announce an update for ROS 2 Crystal Clemmys.

Package Updates for crystal

Added Packages [1]:

  • ros-crystal-xacro: 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:

  • Robert Haschke

Posts: 1

Participants: 1

Read full topic

by @nuclearsandwich Steven! Ragnarök on October 18, 2019 03:35 PM

New packages and patch release for ROS 2 Dashing 2019-10-18

@nuclearsandwich wrote:

The new sync and patch release is here!

This release includes a number of core changes including an updated version of Fast-RTPS. For full details of this patch release refer to the Released column of the project board.

Due to dropped support from Homebrew for macOS 10.12 Sierra, this will be the last Dashing release to include macOS binaries as there is no other supported macOS platform for this release. End of support for macOS 10.12

Thanks, as always, to those who made this release possible. I want to express specific gratitude to @cottsay for managing a very challenging span of platform upgrades for this release.

Package Updates for dashing

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

Added Packages [89]:

  • ros-dashing-automotive-navigation-msgs: 3.0.0-1
  • ros-dashing-automotive-platform-msgs: 3.0.0-1
  • ros-dashing-autoware-auto-algorithm: 0.0.2-1
  • ros-dashing-autoware-auto-helper-functions: 0.0.2-1
  • ros-dashing-delphi-esr-msgs: 3.0.0-2
  • ros-dashing-delphi-mrr-msgs: 3.0.0-2
  • ros-dashing-delphi-srr-msgs: 3.0.0-2
  • ros-dashing-derived-object-msgs: 3.0.0-2
  • ros-dashing-eigen-stl-containers: 1.0.0-1
  • ros-dashing-euclidean-cluster: 0.0.2-1
  • ros-dashing-euclidean-cluster-nodes: 0.0.2-1
  • ros-dashing-gps-msgs: 1.0.0-1
  • ros-dashing-gps-tools: 1.0.0-1
  • ros-dashing-gps-umd: 1.0.0-1
  • ros-dashing-gpsd-client: 1.0.0-1
  • ros-dashing-hungarian-assigner: 0.0.2-1
  • ros-dashing-ibeo-msgs: 3.0.0-2
  • ros-dashing-kalman-filter: 0.0.2-1
  • ros-dashing-kartech-linear-actuator-msgs: 3.0.0-2
  • ros-dashing-launch-ros-sandbox: 0.0.2-4
  • ros-dashing-lidar-utils: 0.0.2-1
  • ros-dashing-localization-common: 0.0.2-1
  • ros-dashing-localization-nodes: 0.0.2-1
  • ros-dashing-marti-can-msgs: 1.0.0-1
  • ros-dashing-marti-common-msgs: 1.0.0-1
  • ros-dashing-marti-nav-msgs: 1.0.0-1
  • ros-dashing-marti-perception-msgs: 1.0.0-1
  • ros-dashing-marti-sensor-msgs: 1.0.0-1
  • ros-dashing-marti-status-msgs: 1.0.0-1
  • ros-dashing-marti-visualization-msgs: 1.0.0-1
  • ros-dashing-mobileye-560-660-msgs: 3.0.0-2
  • ros-dashing-motion-model: 0.0.2-1
  • ros-dashing-move-base-msgs: 2.0.2-1
  • ros-dashing-nav2-system-tests: 0.2.6-1
  • ros-dashing-ndt: 0.0.2-1
  • ros-dashing-neobotix-usboard-msgs: 3.0.0-2
  • ros-dashing-optimization: 0.0.2-1
  • ros-dashing-pacmod-msgs: 3.0.0-2
  • ros-dashing-pcl-msgs: 1.0.0-1
  • ros-dashing-point-cloud-fusion: 0.0.2-1
  • ros-dashing-radar-msgs: 3.0.0-2
  • ros-dashing-ray-ground-classifier: 0.0.2-1
  • ros-dashing-ray-ground-classifier-nodes: 0.0.2-1
  • ros-dashing-ros2trace-analysis: 0.2.1-1
  • ros-dashing-serial-driver: 0.0.2-1
  • ros-dashing-slam-toolbox: 2.0.2-1
  • ros-dashing-velodyne-driver: 0.0.2-1
  • ros-dashing-velodyne-node: 0.0.2-1
  • ros-dashing-voxel-grid: 0.0.2-1
  • ros-dashing-voxel-grid-nodes: 0.0.2-1
  • ros-dashing-xacro: 2.0.1-2

Updated Packages [240]:

  • ros-dashing-action-tutorials: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-ament-clang-format: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-clang-tidy: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-cmake-clang-format: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-cmake-clang-tidy: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-cmake-copyright: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-cmake-cppcheck: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-cmake-cpplint: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-cmake-flake8: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-cmake-lint-cmake: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-cmake-pclint: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-cmake-pep257: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-cmake-pep8: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-cmake-pyflakes: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-cmake-uncrustify: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-cmake-xmllint: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-copyright: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-cppcheck: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-cpplint: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-flake8: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-index-cpp: 0.7.1-1 -> 0.7.2-1
  • ros-dashing-ament-index-python: 0.7.1-1 -> 0.7.2-1
  • ros-dashing-ament-lint: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-lint-auto: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-lint-cmake: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-lint-common: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-package: 0.7.2-1 -> 0.7.3-1
  • ros-dashing-ament-pclint: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-pep257: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-pep8: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-pyflakes: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-uncrustify: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-ament-xmllint: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-autoware-auto-cmake: 0.0.1-1 -> 0.0.2-1
  • ros-dashing-autoware-auto-create-pkg: 0.0.1-1 -> 0.0.2-1
  • ros-dashing-autoware-auto-examples: 0.0.1-1 -> 0.0.2-1
  • ros-dashing-autoware-auto-geometry: 0.0.1-1 -> 0.0.2-1
  • ros-dashing-autoware-auto-msgs: 0.0.1-1 -> 0.0.2-1
  • ros-dashing-composition: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-costmap-queue: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-demo-nodes-cpp: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-demo-nodes-cpp-native: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-demo-nodes-py: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-depthimage-to-laserscan: 2.2.1-1 -> 2.2.2-1
  • ros-dashing-dummy-map-server: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-dummy-robot-bringup: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-dummy-sensors: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-dwb-controller: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-dwb-core: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-dwb-critics: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-dwb-msgs: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-dwb-plugins: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-fastcdr: 1.0.9-2 -> 1.0.11-1
  • ros-dashing-fastrtps: 1.8.0-2 -> 1.8.2-1
  • ros-dashing-image-tools: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-intra-process-demo: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-launch: 0.8.6-1 -> 0.8.7-1
  • ros-dashing-launch-ros: 0.8.6-1 -> 0.8.7-1
  • ros-dashing-launch-testing: 0.8.6-1 -> 0.8.7-1
  • ros-dashing-launch-testing-ament-cmake: 0.8.6-1 -> 0.8.7-1
  • ros-dashing-launch-testing-ros: 0.8.6-1 -> 0.8.7-1
  • ros-dashing-lifecycle: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-logging-demo: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-map-msgs: 2.0.1-1 -> 2.0.2-1
  • ros-dashing-nav-2d-msgs: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav-2d-utils: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav2-amcl: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav2-behavior-tree: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav2-bringup: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav2-bt-navigator: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav2-common: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav2-costmap-2d: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav2-dwb-controller: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav2-dynamic-params: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav2-lifecycle-manager: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav2-map-server: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav2-msgs: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav2-navfn-planner: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav2-recoveries: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav2-rviz-plugins: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav2-util: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav2-voxel-grid: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-nav2-world-model: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-navigation2: 0.2.4-1 -> 0.2.6-1
  • ros-dashing-osrf-pycommon: 0.1.7-1 -> 0.1.9-1
  • ros-dashing-pendulum-control: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-pendulum-msgs: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-pluginlib: 2.3.2-1 -> 2.3.3-1
  • ros-dashing-py-trees: 1.2.2-1 -> 1.3.0-1
  • ros-dashing-py-trees-ros: 1.1.2-1 -> 1.2.1-2
  • ros-dashing-py-trees-ros-interfaces: 1.1.2-1 -> 1.2.0-1
  • ros-dashing-py-trees-ros-tutorials: 1.0.3-1 -> 1.0.5-1
  • ros-dashing-python-cmake-module: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-python-qt-binding: 1.0.1-1 -> 1.0.2-1
  • ros-dashing-qt-dotgraph: 1.0.6-1 -> 1.0.7-1
  • ros-dashing-qt-gui: 1.0.6-1 -> 1.0.7-1
  • ros-dashing-qt-gui-app: 1.0.6-1 -> 1.0.7-1
  • ros-dashing-qt-gui-core: 1.0.6-1 -> 1.0.7-1
  • ros-dashing-qt-gui-cpp: 1.0.6-1 -> 1.0.7-1
  • ros-dashing-qt-gui-py-common: 1.0.6-1 -> 1.0.7-1
  • ros-dashing-quality-of-service-demo-cpp: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-quality-of-service-demo-py: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-rclcpp: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-rclcpp-action: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-rclcpp-components: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-rclcpp-lifecycle: 0.7.10-1 -> 0.7.11-1
  • ros-dashing-rclpy: 0.7.7-1 -> 0.7.8-1
  • ros-dashing-rmw-fastrtps-cpp: 0.7.5-1 -> 0.7.6-1
  • ros-dashing-rmw-fastrtps-dynamic-cpp: 0.7.5-1 -> 0.7.6-1
  • ros-dashing-rmw-fastrtps-shared-cpp: 0.7.5-1 -> 0.7.6-1
  • ros-dashing-ros-testing: 0.1.0-1 -> 0.1.1-1
  • ros-dashing-ros-workspace: 0.7.1-1 -> 0.7.2-1
  • ros-dashing-ros2action: 0.7.4-1 -> 0.7.6-1
  • ros-dashing-ros2bag: 0.1.6-1 -> 0.1.8-1
  • ros-dashing-ros2cli: 0.7.4-1 -> 0.7.6-1
  • ros-dashing-ros2component: 0.7.4-1 -> 0.7.6-1
  • ros-dashing-ros2launch: 0.8.6-1 -> 0.8.7-1
  • ros-dashing-ros2lifecycle: 0.7.4-1 -> 0.7.6-1
  • ros-dashing-ros2msg: 0.7.4-1 -> 0.7.6-1
  • ros-dashing-ros2multicast: 0.7.4-1 -> 0.7.6-1
  • ros-dashing-ros2node: 0.7.4-1 -> 0.7.6-1
  • ros-dashing-ros2param: 0.7.4-1 -> 0.7.6-1
  • ros-dashing-ros2pkg: 0.7.4-1 -> 0.7.6-1
  • ros-dashing-ros2run: 0.7.4-1 -> 0.7.6-1
  • ros-dashing-ros2service: 0.7.4-1 -> 0.7.6-1
  • ros-dashing-ros2srv: 0.7.4-1 -> 0.7.6-1
  • ros-dashing-ros2test: 0.1.0-1 -> 0.1.1-1
  • ros-dashing-ros2topic: 0.7.4-1 -> 0.7.6-1
  • ros-dashing-ros2trace: 0.2.0-1 -> 0.2.8-1
  • ros-dashing-rosapi: 1.0.1-1 -> 1.0.2-1
  • ros-dashing-rosbag2: 0.1.6-1 -> 0.1.8-1
  • ros-dashing-rosbag2-converter-default-plugins: 0.1.6-1 -> 0.1.8-1
  • ros-dashing-rosbag2-storage: 0.1.6-1 -> 0.1.8-1
  • ros-dashing-rosbag2-storage-default-plugins: 0.1.6-1 -> 0.1.8-1
  • ros-dashing-rosbag2-test-common: 0.1.6-1 -> 0.1.8-1
  • ros-dashing-rosbag2-tests: 0.1.6-1 -> 0.1.8-1
  • ros-dashing-rosbag2-transport: 0.1.6-1 -> 0.1.8-1
  • ros-dashing-rosbridge-library: 1.0.1-1 -> 1.0.2-1
  • ros-dashing-rosbridge-msgs: 1.0.1-1 -> 1.0.2-1
  • ros-dashing-rosbridge-server: 1.0.1-1 -> 1.0.2-1
  • ros-dashing-rosbridge-suite: 1.0.1-1 -> 1.0.2-1
  • ros-dashing-rosidl-adapter: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-rosidl-cmake: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-rosidl-generator-c: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-rosidl-generator-cpp: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-rosidl-generator-py: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-rosidl-parser: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-rosidl-runtime-py: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-rosidl-typesupport-interface: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-rosidl-typesupport-introspection-c: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-rosidl-typesupport-introspection-cpp: 0.7.6-1 -> 0.7.7-1
  • ros-dashing-rqt: 1.0.4-1 -> 1.0.5-1
  • ros-dashing-rqt-console: 1.0.1-1 -> 1.1.0-1
  • ros-dashing-rqt-graph: 1.0.1-1 -> 1.0.2-1
  • ros-dashing-rqt-gui: 1.0.4-1 -> 1.0.5-1
  • ros-dashing-rqt-gui-cpp: 1.0.4-1 -> 1.0.5-1
  • ros-dashing-rqt-gui-py: 1.0.4-1 -> 1.0.5-1
  • ros-dashing-rqt-plot: 1.0.6-1 -> 1.0.7-1
  • ros-dashing-rqt-publisher: 1.0.5-1 -> 1.1.0-1
  • ros-dashing-rqt-py-common: 1.0.4-1 -> 1.0.5-1
  • ros-dashing-rqt-reconfigure: 1.0.3-1 -> 1.0.4-1
  • ros-dashing-shared-queues-vendor: 0.1.6-1 -> 0.1.8-1
  • ros-dashing-sqlite3-vendor: 0.1.6-1 -> 0.1.8-1
  • ros-dashing-teleop-twist-keyboard: 2.3.0-1 -> 2.3.1-1
  • ros-dashing-topic-monitor: 0.7.8-1 -> 0.7.9-1
  • ros-dashing-tracetools: 0.2.0-1 -> 0.2.8-1
  • ros-dashing-tracetools-analysis: 0.1.1-1 -> 0.2.1-1
  • ros-dashing-tracetools-launch: 0.2.0-1 -> 0.2.8-1
  • ros-dashing-tracetools-read: 0.2.0-1 -> 0.2.8-1
  • ros-dashing-tracetools-test: 0.2.0-1 -> 0.2.8-1
  • ros-dashing-tracetools-trace: 0.2.0-1 -> 0.2.8-1
  • ros-dashing-turtlebot3-msgs: 2.1.0-1 -> 2.2.0-1
  • ros-dashing-turtlesim: 1.0.0-1 -> 1.0.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:

  • AWS RoboMaker
  • Amazon ROS Contributions
  • Apex.AI
  • Apex.AI, Inc.
  • AutonomouStuff Software Development Team
  • AutonomouStuff Software Team
  • Brian Wilcox
  • Carl Delsey
  • Carlos Orduno
  • Chris Lalancette
  • Christophe Bedard
  • Daniel Stonier
  • David V. Lu!!
  • Dirk Thomas
  • Dorian Scholz
  • Hans-Joachim Krauch
  • Jacob Perron
  • John Shepherd
  • Juan Pablo Samper
  • Karsten Knese
  • Michael Carroll
  • Michael Jeronimo
  • Michel Hidalgo
  • Mohammad Haghighipanah
  • P. J. Reed
  • Paul Bovbel
  • Pete Baughman
  • Pyo
  • Robert Haschke
  • Russell Toris
  • Scott K Logan
  • Steve Macenski
  • Steven! Ragnarok
  • Steven! Ragnarök
  • William Woodall

Posts: 1

Participants: 1

Read full topic

by @nuclearsandwich Steven! Ragnarök on October 18, 2019 03:23 PM

ROS 2 F Name Brainstorming

@jacob wrote:

As we approach the release date of Eloquent Elusor, it’s time to start brainstorming names for the F turtle ROS 2 release!

Existing ROS 2 names and codenames:

  • Ardent Apalone - ardent
  • Bouncy Bolson - bouncy
  • Crystal Clemmys - crystal
  • Dashing Diademata - dashing
  • Eloquent Elusor - eloquent

Existing ROS 1 names and codenames:

  • Boxturtle - boxturtle
  • C Turtle - cturtle
  • Diamondback - diamondback
  • Electric Emys - electric
  • Fuerte - fuerte
  • Groovy Galapagos - groovy
  • Hydro Medusa - hydro
  • Indigo Igloo - indigo
  • Jade Turtle - jade
  • Kinetic Kame - kinetic
  • Lunar Loggerhead - lunar
  • Melodic Morenia - melodic
  • Noetic Ninjemys - noetic

Here are some links to turtle species to get us started.
http://www.chelonia.org/byspecies.htm
https://en.wikipedia.org/wiki/Category:Turtle_genera
https://en.wikipedia.org/wiki/Category:Prehistoric_turtle_genera

Please share your suggestions and comments.

There are no rules to this process so be creative.

I’ll start us off with a couple:

Posts: 25

Participants: 21

Read full topic

by @jacob Jacob Perron on October 18, 2019 02:06 AM

October 16, 2019
What are some of the challenges while using ROS on Windows?

@roycey wrote:

I am a product manager and I am trying to understand what are the challenges that developers face while building their robotics applications in general and specifically around using ROS on windows.
What is your checklist for get your dev environment ready?
How easy of difficult is it to incorporate ROS nodes into your app especially on Windows?
How do you go about testing and simulating your code?
How do you deploy your code to your robots? Do you use a CI/CD pipeline?
How do you update your applications once deployed on to robots.

Forgive me if this seems too high level for dev forum. Appreciate your inputs.

Posts: 4

Participants: 3

Read full topic

by @roycey Roycey on October 16, 2019 04:19 PM

October 15, 2019
[ROSject] of the week: How to Open a SolidWorks Model in Gazebo?

@RebeccaU wrote:

This week, we would like to share with you a ROS project prepared by Miguel Angel Rodriguez, a member of The Construct Team, on how to open a SolidWorks model in Gazebo, which contains all the code needed. In this case, an example is given in this video: https://www.youtube.com/watch?v=T7X_p_KMwus on how to import a Fish Robot Model in SolidWorks to Gazebo. We will create the URDF, associate the meshes, and add the control. This will be done for a simplified geometric version and for a complete 3D mesh version.

You can get the whole code, simulation and notebook with instructions (everything running off-the-shelf), by clicking on this link.

Let us know if you are missing any feature in the project or if you would like to contribute to make it better.

Posts: 1

Participants: 1

Read full topic

by @RebeccaU Rebecca Ushiroda on October 15, 2019 09:45 PM

October 14, 2019
[LIVE Class] How to Launch a Robot Simulation with ROS2 (Dashing)

@RebeccaU wrote:

ROS Developers LIVE-Class #69: How to Launch a Robot Simulation with ROS2 (Dashing)
Live Class Link: https://www.twitch.tv/events/hxiwPDWXSne1zcKJsbTRfA

LIVE DATE & TIME

Scheduled for October 15, 2019 @ 6pm - 7pm CEST

WHAT YOU WILL LEARN IN CLASS #69

In this class, you will learn how to launch a ROS2 Gazebo simulation of a wheeled robot. You are going to understand the differences between a ROS1 Gazebo simulation and a ROS2 Gazebo simulation.

Why is so important to learn this topic?

I’m sorry guys, but you need to use simulations for your robot development. ROS2 is quickly moving to become the standard version of ROS for robots so you need to understand how to simulate robots with ROS2.

We provide full code and instructions during the Live Class to all the attendants

We are going to package all the simulation code, documentation and ROS code into a package that we call a ROSject. We will give it for free to all the attendants, at the beginning of the class.

The ROSject of this live class has been created by Christian Chavez and Ricardo Tellez from The Construct. You can use this ROSject freely as long as you keep this notice.

In this class, we’ll learn:

  • How to launch a ROS2 simulation.
  • How to compile a ROS2 simulation.
  • Which packages do you need in order to launch a ROS2 simulation.

PREVIOUS KNOWLEDGE REQUIREMENTS

HOW TO JOIN THE CLASS

  • FREE event open for everyone, the only thing you may need to do is “set reminder” on our twitch channel.
  • We will share the full ROSject (containing robot simulation, notebook with instructions and code) with all the attendants at the beginning of the class. Remember to be on time.
  • In Live Classes, you will practice with the instructor at the same time, with the provided free ROS material.

If you missed the class, you can find the ROSject files and full-code used in the class at the Robot Ignite Academy: https://www.robotigniteacademy.com

Posts: 1

Participants: 1

Read full topic

by @RebeccaU Rebecca Ushiroda on October 14, 2019 11:58 PM

Answers is down (502s), but status page doesn't reflect it

@gavanderhoorn wrote:

Right now (October 14, 2019 7:15 AM) ROS Answers appears to be down for me (I get a 503: bad gateway).

Looking at status.ros.org however does not show anything wrong:

ros_status_answers

It’s unclear how Statuspage is configured (so what it actually checks), but it doesn’t seem to take this kind of problem into account.

PS: I also noticed that the trend graphs seem to have disappeared?

Posts: 7

Participants: 6

Read full topic

by @gavanderhoorn gavanderhoorn on October 14, 2019 07:21 AM

October 11, 2019
New Packages for Kinetic 2019-10-11

@tfoote wrote:

We’re happy to announce 2 new packages and 51 updated packages for Kinetic.

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

Package Updates for kinetic

Added Packages [2]:

Updated Packages [51]:

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:

  • Alessandro Tondo
  • Atsushi Watanabe
  • Carlos Aguero
  • Daniel Miller
  • Davide Faconti
  • Jordy van Appeven
  • Jose Luis
  • Jose Luis Blanco Claraco
  • Jose-Luis Blanco-Claraco
  • Ken Tossell
  • Markus Bader
  • Nick Rotella
  • Nikos Koukis
  • Rhys Mainwaring
  • Timo Roehling
  • Vladislav Tananaev
  • nrotella

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on October 11, 2019 06:26 PM

October 10, 2019
What do you want to see in an educational ROS platform?

@davecrawley wrote:

We’ve started developing a table top / ground ROS robot for use in educational environments. We’d like to hear from educators that really want to teach ROS based robotics, but don’t feel they can because currently available robots are either too expensive, too complicated or too [insert your adjective here].

We’d also like to hear from educators that are teaching ROS robotics but want to broaden what they do, or find alternative platforms.

If you are an educator who offers courses and would like to do so with ROS can you respond to this thread with the one thing that you’d like to see in a educational platform for ROS. If enough people express interest we will do a couple of group calls so we can hear what people would like and make trade-off decisions. Then we will do our best to build what the group wants with open source repos to go along with it!

Please respond with the one thing you’d like to see in an ROS robot platform oriented for education.

David

P.S. Thanks to Tully and Kat for suggesting this!

Posts: 23

Participants: 12

Read full topic

by @davecrawley David Crawley on October 10, 2019 05:21 AM

October 09, 2019
Gazebo version in packages.ros.org is quite outdated?

@peci1 wrote:

Hi, I’ve just found out that there is a big difference in version numbers of Gazebo pulled from packages.ros.org and from packages.osrfoundation.org.

$ apt-cache policy libgazebo9
libgazebo9:
  Installed: 9.11.0-1~bionic
  Candidate: 9.11.0-1~bionic
  Version table:
 *** 9.11.0-1~bionic 500
        500 http://packages.osrfoundation.org/gazebo/ubuntu-stable bionic/main amd64 Packages
        100 /var/lib/dpkg/status
     9.0.0+dfsg5-3ubuntu1+ppa2 500
        500 http://packages.ros.org/ros/ubuntu bionic/main amd64 Packages
        500 http://packages.ros.org/ros2/ubuntu bionic/main amd64 Packages
     9.0.0+dfsg5-3ubuntu1 500
        500 http://cz.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages

Why is that? I understand ROS doesn’t want to tie with Gazebo release schedule, so I’d expect a 1-2 version delay against the osrfoundation repo, but not 11! Is this a desired state? I thought Gazebo is distributed as one of the core packages for ROS, so I’d expect better support…

Posts: 7

Participants: 3

Read full topic

by @peci1 Martin Pecka on October 09, 2019 02:33 PM

2019 ROS Metrics Report

@tfoote wrote:

We’ve posted the annual ROS Metrics report for 2019. You can download it from here and it’s been added to the Metrics wiki page where you can find links to all the previous versions as well.

Background

We started collecting metrics in 2011. Reviewing the history you can see the growth and evolution of the community.

Measuring open source communities is very hard. The nature of being open and redistributable means that we definitely do not know everyone who is using it and that’s part of being open. These metrics can provide insight into trends within the community but should not be considered exhaustive or even close to complete but as a consistent snapshot. We have public instructions for setting up mirrors and these measurements do not count the any statistics for mirrors either private or public. Public mirrors are listed at http://wiki.ros.org/Mirrors

Updates

Every year we seek to provide the same metrics so that trends can be observed. However we also look to update the metrics to include new statistics or cover new aspects that we think may be interesting trends in the future. This year we have added a new viewing metric which is the viewing statistics for https://index.ros.org . It is part of our revamp of resources to evolve the ROS infrastructure as we continue to need to scale upward.

Commentary

At a high level the growth trend continues for the ROS community.
We are now regularly providing around 8,000 GB of package downloads each month.
Last year we provided over 72,000 GB of downloads, and we’ve almost reached that point already with 67,000 GB already download at the beginning of October.

One trend that has been continuing over the last few years is that the growth of ROS in China has continued to the point that they are now the largest userbase by country.

There are two metrics in this report that appear to be different than the general trend.
The first is that wiki edits are significantly up from last year. I suspect that this might just be a sampling artifact. If a few people are particularly active for a few days, especially if there’s a refactoring of a wiki page or two this can quite easily update the numbers.

The other number that has grown a lot is the answers.ros.org users number. The site is currently under a spam attack and through the generous support of our many moderators we have successfully prevented the spammers from posting to the site. However they have broken every captcha effort that we’ve been able to throw at them and so the spammers continue to register but remain with their accounts in a probationary status. When looking at these numbers I suggest considering the users who have contributed to the site and have non-zero karma.

Related Work

I’d also like to highlight again the work of @DLu who has also put together a site for viewing longer term trends of various ROS metrics. It’s a great complement to this annual report. Please see his announcement

And visit the site at: metrics.ros.org

Posts: 1

Participants: 1

Read full topic

by @tfoote Tully Foote on October 09, 2019 08:41 AM

October 08, 2019
The State of Robotics monthly blog

@miker256 wrote:

This a new monthly blog series by the Robotics team at Canonical. If you have any questions @kyrofa from the Ubuntu Robotics team can answer them.

Posts: 1

Participants: 1

Read full topic

by @miker256 Mike Royal on October 08, 2019 10:40 PM

Some place to share / see visualizations

@safijari wrote:

In my company’s Slack we have a channel dedicated to visualizations. We share visualizations that we may have been making while developing an algorithm, or maybe to explain some part of the product to a customer, or some times just for fun. As roboticists I imagine most of us think visually and rely heavily on visualizing our algorithms.

Can discourse be a good place for us to share such visualizations? Would it belong in general? Uncategorized? Should it have its own category? There’s certainly the possibility of it getting a bit spammy.

In conclusion: here’s the last visualization I shared at my company’s slack :grin:

Posts: 18

Participants: 5

Read full topic

by @safijari Jari Safi on October 08, 2019 05:47 PM

October 07, 2019
Announcing LaMa: An alternative localization and mapping package

@eupedrosa wrote:

Dear ROS users,

We would like to announce the release of the IRIS LaMa (Localization and Mapping) package.
It includes a framework for 3D volumetric grids (for mapping), a localization algorithm based on scan matching and two SLAM solution (an Online SLAM and a Particle Filter SLAM).

The main feature is efficiency. You can even run the Particle Filter SLAM in a Raspberry Pi.

We provide ROS integration with the iris_lama_ros package.

Fell free to try it and provide any feedback.

Posts: 9

Participants: 4

Read full topic

by @eupedrosa Eurico F. Pedrosa on October 07, 2019 01:25 PM

[meetings][webinar] How to Teach ROS

@TheConstruct wrote:

[Webinar] How to Teach ROS

Date&Time: 17 October, 2019 @ 6pm to 7 pm 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-size 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 @TheConstruct The Construct on October 07, 2019 01:09 PM

October 05, 2019
"upstream packages" becoming increasingly a problem

@gavanderhoorn wrote:

It could be unlucky sampling or a temporary surge, but we’ve had about 4 to 5 Q&As on ROS Answers in the past week alone where in the end it turned out the problems reported by the OP were caused by UpstreamPackages. Over the past few months (years?) there’s also always been a few each month.

While there is great value in those upstreamed packages (ever try using ROS on a armel or mips target and don’t want to wait 5 hours before everything is compiled?) they seem to be causing an increasing nr of problems for new users, leading to increased nrs of posts to ROS Answers.

I’m not at all advocating for getting them removed, but perhaps we need to inform or warn (new) users better or in a different way such that we can avoid them installing ros-desktop-full instead of ros-$distro-desktop-full (even more confusing are the Python packages: python-roslaunch vs ros-$distro-roslaunch).

An admonition is easily added to the installation tutorials, but perhaps there is someone here who might have a more creative idea.

After all: who pays attention to admonitions? We just copy-paste installation instructions into a terminal, and users who end up installing any of the upstream packages most likely haven’t read/seen/used any of the tutorials in the first place (as they don’t mention them), so they would not see those admonitions.

Posts: 9

Participants: 4

Read full topic

by @gavanderhoorn gavanderhoorn on October 05, 2019 04:16 PM

October 02, 2019
RFC on update of REP 153: rosdistro index format 4 - adding Python major version

@dirk-thomas wrote:

tl;dr: Adding the targeted Python major version for each ROS distribution.

REP 153 introduced the rosdistro index format 4 about a year ago: see the previous thread RFC on REP 153: rosdistro index format 4 In that format version we already introduced the following to allow future iterations without requiring a new format version (https://www.ros.org/reps/rep-0153.html#specification):

As of version 4 unknown keys should be ignored (instead of resulting in an error). This will allow future additions in a backward compatible way without the need to bump the version of the file.

With ROS Noetic spinning up and targeting Python 3 (see previous announcement Planning future ROS 1 distribution(s)) we want to add a new piece of information to the index-v4.yaml file. When bloom-ing package it needs to be decided which conditional dependencies of a package to be used. Variables like ROS_DISTRO and ROS_VERSION are already available - not the ROS_PYTHON_VERSION though.

To avoid hard coding a mapping of ROS distros to their targeted Python major version (potentially in multiple places) this update of REP 153 will add the Python major version to the index-v4.yaml file for each ROS distro instead. Please see the rep#207 for the details on the proposal as well as the actual change of the added metadata in rosdistro#22484.

Due to the future proof design of REP 153 this won’t affect users using the rosdistro Python package at all. Only if you want to access the new ros_version key the upcoming version 0.7.5 of the package is needed (which will contain the following change to expose the new key through the API: python-rosdistro).

Please provide your feedback on the REP pull request or if applicable on either of the other PRs. (Please do not reply in this discourse thread since the audience is very big and not everyone might be interested in the in-depth discussion of this topic.)

Your friendly ROS team

Posts: 1

Participants: 1

Read full topic

by @dirk-thomas Dirk Thomas on October 02, 2019 10:54 PM

Documentation updates improve ROS utilization and functionality

Lessons from UR driver updates reinforce importance of documentation

A key strength of the open-source community is the capacity to build on the knowledge of other developers who enable future advancements. Documentation plays a critical role in advancing understanding, which improves ROS utilization globally. This will be increasingly important as we move from ROS to ROS2 and document the various steps, including driver updates, necessary to execute projects.

Recent driver updates for a Universal Robots project helped demonstrate the importance of documentation to our team. In July 2019, Universal Robots updated their software for e-series and CB-series to 5.4 and 3.10. We were using the 5.4 software on UR 10e robots for a few different projects, and the ur_modern_driver [1] for ROS kinetic and melodic was no longer compatible due to this update. I updated the driver by investigating the release notes for 5.4.x.x [2] and the client_interface document [3].

UR10 E-series in the SwRI collaborative lab

UR10 E-series in the SwRI collaborative lab

To update the ROS driver for compatibility with software updates, I first identified what changes occurred and located appropriate software documentation for the hardware. The software documentation defined modules and variable types for the changes, which allowed for comparison with equivalent variables and modules in the current driver code. Without proper documentation from Universal Robots this would have been a much more difficult endeavor.

The ur_modern_driver specifically interacts with the client interface. Two variables were added to the 5.4 software client interface: a reserved byte in the Masterboard data sub package of Robot State Message to be used for internal UR use and a safety status value to the real time interface. The client interface document gave the types and sizes of these variables along with variables used in previous software versions.

The client interface for 5.3 and earlier had an internal UR int in Robot Mode Data I could compare to, and the safety status value could be compared to any of the other double variables in the previous driver’s RealTime interface. I used the search feature in QTCreator to find instances of these variables and added equivalent lines for the new ones. Then I used QTCreator’s debugger to track where new if statements and functions needed to be added to allow the driver to detect the new software version being used and access these new variables.

Working on this upgrade reinforced the necessity of good documentation. In general, the ur_modern_driver had more detailed documentation than many other ROS repos; however, it could still be improved. The README had no mention of the purpose of the use_lowbandwidth_trajectory_follower parameter in the launch files or the urXXe_bringup_joint_limited.launch file; both of these are useful when simulations are being overenthusiastic in their trajectory planning. I added documentation to the README to help others use these features to troubleshoot.

To update drivers, you will need to know what has been changed in the software, and you will ideally have access to a previous version of the driver. Because industrial hardware is intended to be reliable and accessible for multiple clients, there is often plenty of useful documentation if you can search with the correct terminology. Using the known changes and the documentation to compare with the previous driver code allowed me to update the driver fairly quickly so projects could move forward.

1https://github.com/ros-industrial/ur_modern_driver

2https://www.universal-robots.com/how-tos-and-faqs/faq/ur-faq/release-note-software-version-54xx/

3https://www.universal-robots.com/how-tos-and-faqs/how-to/ur-how-tos/remote-control-via-tcpip-16496/

by Rachel Wall on October 02, 2019 08:43 PM

[LIVE Class] How to Control Two-Arm Robots with Movelt!

@TheConstruct wrote:

ROS Developers LIVE-Class #68: How to Control Two-Arm Robots with Movelt!
Live Class Link: https://www.twitch.tv/events/noWTxKtYRF-LuiqUQnUW1A

LIVE DATE & TIME

Scheduled for October 8, 2019 @ 6pm - 7pm CEST

WHAT YOU WILL LEARN

In this class, you will learn how to launch a simulation of two-arm robots and how to control them using MoveIt! (https://moveit.ros.org)

Why is so important to learn this topic?

Trending in robot manipulators is to have multiarm robots. For example, many humanoids, mobile manipulators or collaborative robots.

But, what’s MoveIt! package?

It is a ROS package that allows the easy control of robotic arms, including inverse kinematics, and sensor information for obstacle avoidance.

The ROSject of this live class has been created by Christian Chavez and Ricardo Tellez from The Construct. You can use this ROSject (what is ROSject?) freely as long as you keep this notice.

In this class, we’ll learn:

  • How to configure a two arms simulation
  • How to launch two instances of MoveIt! so we can control each arm independently

Previous knowledge requirements

HOW TO JOIN THE CLASS

  • FREE event open for everyone, the only thing you may need to do is “set reminder” on our twitch channel.
  • We will share the full ROSject (containing robot simulation, notebook with instructions and code) with all the attendants at the beginning of the class. Remember to be on time.
  • In Live Classes, you will practice with the instructor at the same time, with the provided free ROS material.

If you missed the class, you can find the ROSject files and full-code used in the class at the Robot Ignite Academy: https://www.robotigniteacademy.com

Posts: 1

Participants: 1

Read full topic

by @TheConstruct The Construct on October 02, 2019 12:00 PM

ROS Metrics

@DLu wrote:

As a programmer, I think there’s something inherently pleasing about collecting and organizing data. Even more so when you can do it automatically. In that vein, let me introduce my latest nights-and-weekends side project: metrics.ros.org

The idea partially stemmed from this Discourse thread and my previous project ROS Answered. The core is to supercharge the standard Metrics report and graph trends over time.

Some observations:

Anyway, thanks to Tully for granting me access to the Discourse and Google Analytics APIs. I still want to get my hands on the underlying wiki data and the raw logs from http://packages.ros.org (hit me up OSU OSL). There’s lots more that can be gleaned from this data. The graphs I’ve made just scratch the surface. I look forward to using the data to help us understand and improve the ROS community/ecosystem.

Github Repo
related tweets

Send me a message if you want access to the aggregated database files.

Posts: 9

Participants: 7

Read full topic

by @DLu David!! on October 02, 2019 02:08 AM


Powered by the awesome: Planet