Repo symbol

slider_publisher repository

slider_publisher

ROS Distro
humble

Repository Summary

Description
Checkout URI https://github.com/oKermorgant/slider_publisher.git
VCS Type git
VCS Version ros2
Last Updated 2026-03-07
Dev Status MAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
slider_publisher 2.4.2

README

slider_publisher

This packages proposes a slider-based publisher node similar to the joint_state_publisher, but that can publish any message or service.

ROS Packages

Humble Build Status</td> </tr>
Jazzy Build Status</td> </tr>
Rolling Build Status</td> </tr> </tbody> </table> # Examples Many examples are given, especially * `ros2 launch slider_publisher example.launch file:=BasicTypes.yaml` for the 4 basic types * `ros2 launch slider_publisher example.launch file:=Twist.yaml` for timestamped Twist (cmd_vel) * `ros2 launch slider_publisher example.launch file:=tf.yaml` for a TF message * `ros2 launch slider_publisher example.launch file:=VelPose.yaml` for 2 topics (Twist + Pose) * `ros2 launch slider_publisher example.launch file:=MultiArray.yaml` for a topic with 4 floats * `ros2 launch slider_publisher add_two_ints.launch` for a service call (uses `demo_nodes_cpp server`) Array-based messages are also possible (nested arrays are not). The packages reduces to a single node that has to be called with an argument leading to a YAML file with the following structure (examples corresponding to the VelPose.yaml file): topic_to_be_published: type: full message or service type (geometry_msgs/Twist or geometry_msgs/msg/Twist) key_as_in_gui: (vx, can also be the message field) to: corresponding_message_field (linear.x if not used as the key or not unique field) min: slider minimum value (-1) max: slider maximum value (+1) default: slider default value (if not: (min+max)/2) other_key: ... other_topic_to_be_published: type... Hard-coded numeric values (bounds / constant values in messages) can be defined using fractions of pi. 3D rotations (ie quaternions) can be parameterized as roll / pitch / yaw (see `RPY.yaml`). While these fields are of course not part of a `Quaternion` message, the corresponding 3D rotation will be built and published. If the type is a service interface then the corresponding slider will call the service, after waiting for the server. ## Input controls Input will rely either on a checkbox (`Bool` type) or a text input. - Numeric types: if min/max values are provided, a slider will also be available - All types: if the default value is a list, a combobox will be used for the input, the first element of the list being the defalut value (see e.g. `tf.yaml` example) ## Parameters - `config` (string): this parameter has the same effect as the raw file argument, that is the path to the YAML configuration file - `rate` (double): publication rate (0-100 Hz)
Repo symbol

slider_publisher repository

slider_publisher

ROS Distro
jazzy

Repository Summary

Description
Checkout URI https://github.com/oKermorgant/slider_publisher.git
VCS Type git
VCS Version ros2
Last Updated 2026-03-07
Dev Status MAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
slider_publisher 2.4.2

README

slider_publisher

This packages proposes a slider-based publisher node similar to the joint_state_publisher, but that can publish any message or service.

ROS Packages

Humble Build Status</td> </tr>
Jazzy Build Status</td> </tr>
Rolling Build Status</td> </tr> </tbody> </table> # Examples Many examples are given, especially * `ros2 launch slider_publisher example.launch file:=BasicTypes.yaml` for the 4 basic types * `ros2 launch slider_publisher example.launch file:=Twist.yaml` for timestamped Twist (cmd_vel) * `ros2 launch slider_publisher example.launch file:=tf.yaml` for a TF message * `ros2 launch slider_publisher example.launch file:=VelPose.yaml` for 2 topics (Twist + Pose) * `ros2 launch slider_publisher example.launch file:=MultiArray.yaml` for a topic with 4 floats * `ros2 launch slider_publisher add_two_ints.launch` for a service call (uses `demo_nodes_cpp server`) Array-based messages are also possible (nested arrays are not). The packages reduces to a single node that has to be called with an argument leading to a YAML file with the following structure (examples corresponding to the VelPose.yaml file): topic_to_be_published: type: full message or service type (geometry_msgs/Twist or geometry_msgs/msg/Twist) key_as_in_gui: (vx, can also be the message field) to: corresponding_message_field (linear.x if not used as the key or not unique field) min: slider minimum value (-1) max: slider maximum value (+1) default: slider default value (if not: (min+max)/2) other_key: ... other_topic_to_be_published: type... Hard-coded numeric values (bounds / constant values in messages) can be defined using fractions of pi. 3D rotations (ie quaternions) can be parameterized as roll / pitch / yaw (see `RPY.yaml`). While these fields are of course not part of a `Quaternion` message, the corresponding 3D rotation will be built and published. If the type is a service interface then the corresponding slider will call the service, after waiting for the server. ## Input controls Input will rely either on a checkbox (`Bool` type) or a text input. - Numeric types: if min/max values are provided, a slider will also be available - All types: if the default value is a list, a combobox will be used for the input, the first element of the list being the defalut value (see e.g. `tf.yaml` example) ## Parameters - `config` (string): this parameter has the same effect as the raw file argument, that is the path to the YAML configuration file - `rate` (double): publication rate (0-100 Hz)
Repo symbol

slider_publisher repository

slider_publisher

ROS Distro
kilted

Repository Summary

Description
Checkout URI https://github.com/oKermorgant/slider_publisher.git
VCS Type git
VCS Version ros2
Last Updated 2026-03-07
Dev Status MAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
slider_publisher 2.4.2

README

slider_publisher

This packages proposes a slider-based publisher node similar to the joint_state_publisher, but that can publish any message or service.

ROS Packages

Humble Build Status</td> </tr>
Jazzy Build Status</td> </tr>
Rolling Build Status</td> </tr> </tbody> </table> # Examples Many examples are given, especially * `ros2 launch slider_publisher example.launch file:=BasicTypes.yaml` for the 4 basic types * `ros2 launch slider_publisher example.launch file:=Twist.yaml` for timestamped Twist (cmd_vel) * `ros2 launch slider_publisher example.launch file:=tf.yaml` for a TF message * `ros2 launch slider_publisher example.launch file:=VelPose.yaml` for 2 topics (Twist + Pose) * `ros2 launch slider_publisher example.launch file:=MultiArray.yaml` for a topic with 4 floats * `ros2 launch slider_publisher add_two_ints.launch` for a service call (uses `demo_nodes_cpp server`) Array-based messages are also possible (nested arrays are not). The packages reduces to a single node that has to be called with an argument leading to a YAML file with the following structure (examples corresponding to the VelPose.yaml file): topic_to_be_published: type: full message or service type (geometry_msgs/Twist or geometry_msgs/msg/Twist) key_as_in_gui: (vx, can also be the message field) to: corresponding_message_field (linear.x if not used as the key or not unique field) min: slider minimum value (-1) max: slider maximum value (+1) default: slider default value (if not: (min+max)/2) other_key: ... other_topic_to_be_published: type... Hard-coded numeric values (bounds / constant values in messages) can be defined using fractions of pi. 3D rotations (ie quaternions) can be parameterized as roll / pitch / yaw (see `RPY.yaml`). While these fields are of course not part of a `Quaternion` message, the corresponding 3D rotation will be built and published. If the type is a service interface then the corresponding slider will call the service, after waiting for the server. ## Input controls Input will rely either on a checkbox (`Bool` type) or a text input. - Numeric types: if min/max values are provided, a slider will also be available - All types: if the default value is a list, a combobox will be used for the input, the first element of the list being the defalut value (see e.g. `tf.yaml` example) ## Parameters - `config` (string): this parameter has the same effect as the raw file argument, that is the path to the YAML configuration file - `rate` (double): publication rate (0-100 Hz)
Repo symbol

slider_publisher repository

slider_publisher

ROS Distro
rolling

Repository Summary

Description
Checkout URI https://github.com/oKermorgant/slider_publisher.git
VCS Type git
VCS Version ros2
Last Updated 2026-03-07
Dev Status MAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
slider_publisher 2.4.2

README

slider_publisher

This packages proposes a slider-based publisher node similar to the joint_state_publisher, but that can publish any message or service.

ROS Packages

Humble Build Status</td> </tr>
Jazzy Build Status</td> </tr>
Rolling Build Status</td> </tr> </tbody> </table> # Examples Many examples are given, especially * `ros2 launch slider_publisher example.launch file:=BasicTypes.yaml` for the 4 basic types * `ros2 launch slider_publisher example.launch file:=Twist.yaml` for timestamped Twist (cmd_vel) * `ros2 launch slider_publisher example.launch file:=tf.yaml` for a TF message * `ros2 launch slider_publisher example.launch file:=VelPose.yaml` for 2 topics (Twist + Pose) * `ros2 launch slider_publisher example.launch file:=MultiArray.yaml` for a topic with 4 floats * `ros2 launch slider_publisher add_two_ints.launch` for a service call (uses `demo_nodes_cpp server`) Array-based messages are also possible (nested arrays are not). The packages reduces to a single node that has to be called with an argument leading to a YAML file with the following structure (examples corresponding to the VelPose.yaml file): topic_to_be_published: type: full message or service type (geometry_msgs/Twist or geometry_msgs/msg/Twist) key_as_in_gui: (vx, can also be the message field) to: corresponding_message_field (linear.x if not used as the key or not unique field) min: slider minimum value (-1) max: slider maximum value (+1) default: slider default value (if not: (min+max)/2) other_key: ... other_topic_to_be_published: type... Hard-coded numeric values (bounds / constant values in messages) can be defined using fractions of pi. 3D rotations (ie quaternions) can be parameterized as roll / pitch / yaw (see `RPY.yaml`). While these fields are of course not part of a `Quaternion` message, the corresponding 3D rotation will be built and published. If the type is a service interface then the corresponding slider will call the service, after waiting for the server. ## Input controls Input will rely either on a checkbox (`Bool` type) or a text input. - Numeric types: if min/max values are provided, a slider will also be available - All types: if the default value is a list, a combobox will be used for the input, the first element of the list being the defalut value (see e.g. `tf.yaml` example) ## Parameters - `config` (string): this parameter has the same effect as the raw file argument, that is the path to the YAML configuration file - `rate` (double): publication rate (0-100 Hz)
No version for distro github showing humble. Known supported distros are highlighted in the buttons above.
Repo symbol

slider_publisher repository

slider_publisher

ROS Distro
humble

Repository Summary

Description
Checkout URI https://github.com/oKermorgant/slider_publisher.git
VCS Type git
VCS Version ros2
Last Updated 2026-03-07
Dev Status MAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
slider_publisher 2.4.2

README

slider_publisher

This packages proposes a slider-based publisher node similar to the joint_state_publisher, but that can publish any message or service.

ROS Packages

Humble Build Status</td> </tr>
Jazzy Build Status</td> </tr>
Rolling Build Status</td> </tr> </tbody> </table> # Examples Many examples are given, especially * `ros2 launch slider_publisher example.launch file:=BasicTypes.yaml` for the 4 basic types * `ros2 launch slider_publisher example.launch file:=Twist.yaml` for timestamped Twist (cmd_vel) * `ros2 launch slider_publisher example.launch file:=tf.yaml` for a TF message * `ros2 launch slider_publisher example.launch file:=VelPose.yaml` for 2 topics (Twist + Pose) * `ros2 launch slider_publisher example.launch file:=MultiArray.yaml` for a topic with 4 floats * `ros2 launch slider_publisher add_two_ints.launch` for a service call (uses `demo_nodes_cpp server`) Array-based messages are also possible (nested arrays are not). The packages reduces to a single node that has to be called with an argument leading to a YAML file with the following structure (examples corresponding to the VelPose.yaml file): topic_to_be_published: type: full message or service type (geometry_msgs/Twist or geometry_msgs/msg/Twist) key_as_in_gui: (vx, can also be the message field) to: corresponding_message_field (linear.x if not used as the key or not unique field) min: slider minimum value (-1) max: slider maximum value (+1) default: slider default value (if not: (min+max)/2) other_key: ... other_topic_to_be_published: type... Hard-coded numeric values (bounds / constant values in messages) can be defined using fractions of pi. 3D rotations (ie quaternions) can be parameterized as roll / pitch / yaw (see `RPY.yaml`). While these fields are of course not part of a `Quaternion` message, the corresponding 3D rotation will be built and published. If the type is a service interface then the corresponding slider will call the service, after waiting for the server. ## Input controls Input will rely either on a checkbox (`Bool` type) or a text input. - Numeric types: if min/max values are provided, a slider will also be available - All types: if the default value is a list, a combobox will be used for the input, the first element of the list being the defalut value (see e.g. `tf.yaml` example) ## Parameters - `config` (string): this parameter has the same effect as the raw file argument, that is the path to the YAML configuration file - `rate` (double): publication rate (0-100 Hz)
Repo symbol

slider_publisher repository

slider_publisher

ROS Distro
galactic

Repository Summary

Description
Checkout URI https://github.com/oKermorgant/slider_publisher.git
VCS Type git
VCS Version ros2
Last Updated 2026-03-07
Dev Status MAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
slider_publisher 2.4.2

README

slider_publisher

This packages proposes a slider-based publisher node similar to the joint_state_publisher, but that can publish any message or service.

ROS Packages

Humble Build Status</td> </tr>
Jazzy Build Status</td> </tr>
Rolling Build Status</td> </tr> </tbody> </table> # Examples Many examples are given, especially * `ros2 launch slider_publisher example.launch file:=BasicTypes.yaml` for the 4 basic types * `ros2 launch slider_publisher example.launch file:=Twist.yaml` for timestamped Twist (cmd_vel) * `ros2 launch slider_publisher example.launch file:=tf.yaml` for a TF message * `ros2 launch slider_publisher example.launch file:=VelPose.yaml` for 2 topics (Twist + Pose) * `ros2 launch slider_publisher example.launch file:=MultiArray.yaml` for a topic with 4 floats * `ros2 launch slider_publisher add_two_ints.launch` for a service call (uses `demo_nodes_cpp server`) Array-based messages are also possible (nested arrays are not). The packages reduces to a single node that has to be called with an argument leading to a YAML file with the following structure (examples corresponding to the VelPose.yaml file): topic_to_be_published: type: full message or service type (geometry_msgs/Twist or geometry_msgs/msg/Twist) key_as_in_gui: (vx, can also be the message field) to: corresponding_message_field (linear.x if not used as the key or not unique field) min: slider minimum value (-1) max: slider maximum value (+1) default: slider default value (if not: (min+max)/2) other_key: ... other_topic_to_be_published: type... Hard-coded numeric values (bounds / constant values in messages) can be defined using fractions of pi. 3D rotations (ie quaternions) can be parameterized as roll / pitch / yaw (see `RPY.yaml`). While these fields are of course not part of a `Quaternion` message, the corresponding 3D rotation will be built and published. If the type is a service interface then the corresponding slider will call the service, after waiting for the server. ## Input controls Input will rely either on a checkbox (`Bool` type) or a text input. - Numeric types: if min/max values are provided, a slider will also be available - All types: if the default value is a list, a combobox will be used for the input, the first element of the list being the defalut value (see e.g. `tf.yaml` example) ## Parameters - `config` (string): this parameter has the same effect as the raw file argument, that is the path to the YAML configuration file - `rate` (double): publication rate (0-100 Hz)
Repo symbol

slider_publisher repository

slider_publisher

ROS Distro
iron

Repository Summary

Description
Checkout URI https://github.com/oKermorgant/slider_publisher.git
VCS Type git
VCS Version ros2
Last Updated 2026-03-07
Dev Status MAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
slider_publisher 2.4.2

README

slider_publisher

This packages proposes a slider-based publisher node similar to the joint_state_publisher, but that can publish any message or service.

ROS Packages

Humble Build Status</td> </tr>
Jazzy Build Status</td> </tr>
Rolling Build Status</td> </tr> </tbody> </table> # Examples Many examples are given, especially * `ros2 launch slider_publisher example.launch file:=BasicTypes.yaml` for the 4 basic types * `ros2 launch slider_publisher example.launch file:=Twist.yaml` for timestamped Twist (cmd_vel) * `ros2 launch slider_publisher example.launch file:=tf.yaml` for a TF message * `ros2 launch slider_publisher example.launch file:=VelPose.yaml` for 2 topics (Twist + Pose) * `ros2 launch slider_publisher example.launch file:=MultiArray.yaml` for a topic with 4 floats * `ros2 launch slider_publisher add_two_ints.launch` for a service call (uses `demo_nodes_cpp server`) Array-based messages are also possible (nested arrays are not). The packages reduces to a single node that has to be called with an argument leading to a YAML file with the following structure (examples corresponding to the VelPose.yaml file): topic_to_be_published: type: full message or service type (geometry_msgs/Twist or geometry_msgs/msg/Twist) key_as_in_gui: (vx, can also be the message field) to: corresponding_message_field (linear.x if not used as the key or not unique field) min: slider minimum value (-1) max: slider maximum value (+1) default: slider default value (if not: (min+max)/2) other_key: ... other_topic_to_be_published: type... Hard-coded numeric values (bounds / constant values in messages) can be defined using fractions of pi. 3D rotations (ie quaternions) can be parameterized as roll / pitch / yaw (see `RPY.yaml`). While these fields are of course not part of a `Quaternion` message, the corresponding 3D rotation will be built and published. If the type is a service interface then the corresponding slider will call the service, after waiting for the server. ## Input controls Input will rely either on a checkbox (`Bool` type) or a text input. - Numeric types: if min/max values are provided, a slider will also be available - All types: if the default value is a list, a combobox will be used for the input, the first element of the list being the defalut value (see e.g. `tf.yaml` example) ## Parameters - `config` (string): this parameter has the same effect as the raw file argument, that is the path to the YAML configuration file - `rate` (double): publication rate (0-100 Hz)
No version for distro melodic showing humble. Known supported distros are highlighted in the buttons above.
Repo symbol

slider_publisher repository

slider_publisher

ROS Distro
humble

Repository Summary

Description
Checkout URI https://github.com/oKermorgant/slider_publisher.git
VCS Type git
VCS Version ros2
Last Updated 2026-03-07
Dev Status MAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
slider_publisher 2.4.2

README

slider_publisher

This packages proposes a slider-based publisher node similar to the joint_state_publisher, but that can publish any message or service.

ROS Packages

Humble Build Status</td> </tr>
Jazzy Build Status</td> </tr>
Rolling Build Status</td> </tr> </tbody> </table> # Examples Many examples are given, especially * `ros2 launch slider_publisher example.launch file:=BasicTypes.yaml` for the 4 basic types * `ros2 launch slider_publisher example.launch file:=Twist.yaml` for timestamped Twist (cmd_vel) * `ros2 launch slider_publisher example.launch file:=tf.yaml` for a TF message * `ros2 launch slider_publisher example.launch file:=VelPose.yaml` for 2 topics (Twist + Pose) * `ros2 launch slider_publisher example.launch file:=MultiArray.yaml` for a topic with 4 floats * `ros2 launch slider_publisher add_two_ints.launch` for a service call (uses `demo_nodes_cpp server`) Array-based messages are also possible (nested arrays are not). The packages reduces to a single node that has to be called with an argument leading to a YAML file with the following structure (examples corresponding to the VelPose.yaml file): topic_to_be_published: type: full message or service type (geometry_msgs/Twist or geometry_msgs/msg/Twist) key_as_in_gui: (vx, can also be the message field) to: corresponding_message_field (linear.x if not used as the key or not unique field) min: slider minimum value (-1) max: slider maximum value (+1) default: slider default value (if not: (min+max)/2) other_key: ... other_topic_to_be_published: type... Hard-coded numeric values (bounds / constant values in messages) can be defined using fractions of pi. 3D rotations (ie quaternions) can be parameterized as roll / pitch / yaw (see `RPY.yaml`). While these fields are of course not part of a `Quaternion` message, the corresponding 3D rotation will be built and published. If the type is a service interface then the corresponding slider will call the service, after waiting for the server. ## Input controls Input will rely either on a checkbox (`Bool` type) or a text input. - Numeric types: if min/max values are provided, a slider will also be available - All types: if the default value is a list, a combobox will be used for the input, the first element of the list being the defalut value (see e.g. `tf.yaml` example) ## Parameters - `config` (string): this parameter has the same effect as the raw file argument, that is the path to the YAML configuration file - `rate` (double): publication rate (0-100 Hz)
Repo symbol

slider_publisher repository

slider_publisher

ROS Distro
noetic

Repository Summary

Description
Checkout URI https://github.com/oKermorgant/slider_publisher.git
VCS Type git
VCS Version ros1
Last Updated 2022-12-19
Dev Status MAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Packages

Name Version
slider_publisher 1.1.1

README

slider_publisher

This package proposes a slider-based publisher node similar to the joint_state_publisher, but that can publish any type of message.

Several examples are given:

  • roslaunch example.launch for timestamped Twist (cmd_vel)
  • roslaunch example.launch file:=Twist.yaml for non-timestamped Twist
  • roslaunch example.launch file:=VelPose.yaml for 2 topics (Twist + Pose)
  • roslaunch example.launch file:=MultiArray.yaml for a topic with 4 floats
  • roslaunch gazebo_service.launch for a service call (uses gazebo_msgs)

Only numerical types or their derivatives can be publisher (ie there is no text input to change such value on-the-fly). Array-based messages are also possible for numerical values.

The packages reduces to a single node that has to be called with an argument leading to a YAML file with the following structure (examples corresponding to the VelPose.yaml file):

topic_to_be_published:
    type: full message or service type               (geometry_msgs/Twist or geometry_msgs/msg/Twist to specify it is a message)
    key_as_in_gui:                        (vx)
        to: corresponding_message_field   (linear.x)
        min: slider minimum value         (-1)
        max: slider maximum value         (+1)
        default: slider default value     (if not: (min+max)/2)
    other_key:
        ...
other_topic_to_be_published:
    type...

Hard-coded numeric values (bounds / constant values in messages) can be defined using fractions of pi.

3D rotations (ie quaternions) can be parameterized as roll / pitch / yaw (see RPY.yaml). While these fields are of course not part of a Quaternion message, the corresponding 3D rotation will be built and published.

If the type is a service interface then the corresponding slider will call the service, after waiting for the server.

Parameters

  • ~rate (default 10): the rate of publication