Kenji Miyake's profile - activity

We use https://github.com/autowarefoundation/ros2_socketcan with PCAN.

Asked at https://github.com/ros2-gbp/velodyne_simulator-release/issues/1.

I see, thank you! I'll create an issue. Maybe https://github.com/ros2-gbp/velodyne_simulator-release is another good pla

I see, thank you! I'll create an issue. Maybe https://github.com/ros2-gbp/velodyne_simulator-release is another good pla

It's not released to Rolling as well. $ docker run --rm -it arm64v8/ros:rolling $ apt update >/dev/null 2>&1

Thank you for your comment! But seeing it's released to Foxy and Galactic, I guess there is some release issue. So I bel

Why velodyne_description isn't released for arm64? Seeing these URLs, it seems not released. http://packages.ros.org/r

You can write like this. geometry_msgs::build<geometry_msgs::msg::Point>().x(p.x).y(p.y).z(p.z); See this issue

I believe it would be available from Humble! https://github.com/ros2/launch_ros/pull/235

I'm not sure whether this would help you, but if you use colcon, COLCON_PREFIX_PATH can be used to know sourced workspac

I think you can use SetParameter in this case. https://github.com/tier4/AutowareArchitectureProposal_launcher/blob/8cd

Thank you for adding your star so soon! :-) Please remember that this is tested only with our limited use cases yet.

Seeing existing ROS packages, it seems there are some rules for formatting package.xml.

• There should be a new line between mandatory and optional tags.
• There should be a new line when the depend type has changed.

However, I couldn't find the rules in REP 149. (I'm sorry if I overlooked them.)

Where are the rules written? Although I can guess it from package_format3.xsd, I want a more clear explanation.

Also, is there any way to check the rule automatically? I think ament_xmllint doesn't support it.

We developed https://github.com/tier4/pre-commit-hooks-ros to automatically format package.xml.

We added https://github.com/tier4/pre-commit-hooks-ros to automatically format package.xml.

@Jason1923 Yes, it's for ROS1. This does the equivalent things in ROS2. register-python-argcomplete --shell fish ros2

You can use https://github.com/edc/bass to do that. bass source /opt/ros/galactic/setup.bash Also, if you launch fish

It's automatically evaluated in the launch phase, so generally, you don't have to care about it. If you'd like to print

Where are the recommended formatting rules of package.xml? Seeing existing ROS packages, it seems there are some rules f

Hello, I've used parameter overrides in ROS1. It's useful if we can use it in ROS2 as well. http://wiki.ros.org/roslaunch/Tutoria...

So I'd like to know:

1. whether it's supported or not
2. (if not supported) is it possible to implement it using Python launch API

As for 2, I think it's possible if we can:

• iterate all actions defined in previous contexts
• filter action by some conditions
• override filtered action's attribute

It's similar to what I asked in #q375384. Is it possible to do such a thing?

Hello, I'd like to know whether it's possible to refer to the actions defined in launch A, from launch B.

For example, considering the case of: - start publisher after 5 seconds wait - launch subscriber after publisher started

pubsub.launch.py

from launch import LaunchDescription
from launch.actions import RegisterEventHandler
from launch.actions.timer_action import TimerAction
from launch.event_handlers import OnProcessStart
from launch_ros.actions import Node


def generate_launch_description():
    publisher = Node(
        package="examples_rclcpp_minimal_publisher",
        executable="publisher_lambda",
        output="screen",
    )

    launch_publisher_after_timer = TimerAction(period=5.0, actions=[publisher])

    subscriber = Node(
        package="examples_rclcpp_minimal_subscriber",
        executable="subscriber_lambda",
        output="screen",
    )

    subscriber_handler = RegisterEventHandler(
        event_handler=OnProcessStart(
            target_action=publisher,
            on_start=[
                subscriber,
            ],
        )
    )

    return LaunchDescription([launch_publisher_after_timer, subscriber_handler])

This of course works as expected. However, if I split this into two launch files, sub.launch.py doesn't work correctly. (I know my usage is wrong.)

pub.launch.py(imports are omitted)

def generate_launch_description():
    publisher = Node(
        package="examples_rclcpp_minimal_publisher",
        executable="publisher_lambda",
        output="screen",
    )

    launch_publisher_after_timer = TimerAction(period=5.0, actions=[publisher])

    return LaunchDescription([launch_publisher_after_timer])

sub.launch.py(imports are omitted)

def generate_launch_description():
    publisher = Node(
        package="examples_rclcpp_minimal_publisher",
        executable="publisher_lambda",
        output="screen",
    )

    subscriber = Node(
        package="examples_rclcpp_minimal_subscriber",
        executable="subscriber_lambda",
        output="screen",
    )

    subscriber_handler = RegisterEventHandler(
        event_handler=OnProcessStart(
            target_action=publisher,
            on_start=[
                subscriber,
            ],
        )
    )

    return LaunchDescription([subscriber_handler])

pubsub.launch.xml

<launch>
  <include file="./pub.launch.py"/>
  <include file="./sub.launch.py"/>
</launch>

So my question is, can I use publisher Node defined in pub.launch.py as target_action in sub.launch.py? I guess it's possible if there is a method to iterate all actions defined in other launch files and then filter by name.

Thank you in advance.

In ROS1, this page says that services

• should be used for remote procedure calls that terminate quickly
• should never be used for longer running processes

I'm not sure the specific amount of "long", but I guess this is because services were synchronous in ROS1, am I correct?

Now I think services became asynchronous in ROS2 and this page doesn't say we shouldn't use services for long tasks. Also, seeing this page, I think the point of selecting services or actions are

• whether we cancel tasks
• whether we need feedback

So I guess we can use services for a bit long tasks now. For example, suppose that there is a task that takes 30 seconds, and we don't need to know the progress and don't need to cancel it.

Is it okay to use services for the task? Or are any problems?

What are the criteria for selecting services or actions? Did they change in ROS2 due to asynchronous services? In ROS1,