demos VS ros2_tracing

ARG FROM_IMAGE=ros:foxy ARG OVERLAY_WS=/opt/ros/overlay_ws # multi-stage for caching FROM $FROM_IMAGE AS cacher # clone overlay source ARG OVERLAY_WS WORKDIR $OVERLAY_WS/src RUN echo "\ repositories: \n\ ros2/demos: \n\ type: git \n\ url: https://github.com/ros2/demos.git \n\ version: ${ROS_DISTRO} \n\ " > ../overlay.repos RUN vcs import ./ < ../overlay.repos # copy manifests for caching WORKDIR /opt RUN mkdir -p /tmp/opt && \ find ./ -name "package.xml" | \ xargs cp --parents -t /tmp/opt && \ find ./ -name "COLCON_IGNORE" | \ xargs cp --parents -t /tmp/opt || true # multi-stage for building FROM $FROM_IMAGE AS builder # install overlay dependencies ARG OVERLAY_WS WORKDIR $OVERLAY_WS COPY --from=cacher /tmp/$OVERLAY_WS/src ./src RUN . /opt/ros/$ROS_DISTRO/setup.sh && \ apt-get update && rosdep install -y \ --from-paths \ src/ros2/demos/demo_nodes_cpp \ src/ros2/demos/demo_nodes_py \ --ignore-src \ && rm -rf /var/lib/apt/lists/* # build overlay source COPY --from=cacher $OVERLAY_WS/src ./src ARG OVERLAY_MIXINS="release" RUN . /opt/ros/$ROS_DISTRO/setup.sh && \ colcon build \ --packages-select \ demo_nodes_cpp \ demo_nodes_py \ --mixin $OVERLAY_MIXINS # source entrypoint setup ENV OVERLAY_WS $OVERLAY_WS RUN sed --in-place --expression \ '$isource "$OVERLAY_WS/install/setup.bash"' \ /ros_entrypoint.sh # run launch file CMD ["ros2", "launch", "demo_nodes_cpp", "talker_listener.launch.py"]

Hello, I am doing my thesis in ros2, on linux with realtime preemt kernel and all the reccomended settings. The problem is, in older demo : https://github.com/ros2/demos/tree/rolling/pendulum_control Performance statistics got printed automatically, in a newer version :

Managed or lifecycle nodes make sense to me (see also design page). I've frequently used state machines for this sort of thing in the past, and it sounds like a good idea to have some infrastructure in place to avoid reproduction of effort.

I think that's probably the way to go. There are a couple of launch files like that, I guess that use tracetools_launch (see here in one of the pendulum_bringup launch files) to actually record some timing statistics.