ros-controls / ros-controls/ros2_controllers

Create alternative to std_msgs/Float64MultiArray in ForwardCommandController & family

Open
#157 18 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted persistent
Dominant language
C++
Stars
834
Forks
530
Avg merge
18h 3m
Merged PRs (30d)
19

Description

Problem:

std_msgs/Float64MultiArray is deprecated.

# This was originally provided as an example message.
# It is deprecated as of Foxy
# It is recommended to create your own semantically meaningful message.
# However if you would like to continue using this please use the equivalent in example_msgs.

# Please look at the MultiArrayLayout message definition for
# documentation on all multiarrays.

MultiArrayLayout  layout        # specification of data layout
float64[]         data          # array of data

https://github.com/ros2/common_interfaces/blob/foxy/std_msgs/msg/Float64MultiArray.msg

Proposal:

Create (an) alternative in control_msgs. This could be a set of messages with a single joint interface type, one supporting multiples, or one message that has a field for the joint interface type and one that is fully dynamic --- (dynamic joint states??).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the deprecated std_msgs/Float64MultiArray definition and its MultiArrayLayout documentation, then inspect the control_msgs area where the alternative would belong. Compare the proposed single-interface, multi-interface, and dynamic joint-state message options. Done means an agreed semantically meaningful control_msgs alternative is specified and added.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
robotics
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
32/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.