ROS 2 / JAZZY
autoware_motion_velocity_planner
Manifest version: 1.9.0 · Upstream repository ID: autoware_core
Purpose and upstream context
Topics explicitly mentioned in the upstream description: message and service interfaces.
Roles declared in the manifest: interface
What to test before changing versions
Upstream marks this as an interface package used by other releases. Before changing a message or service definition, rebuild the listed consumers and check that publishers and receivers use matching interfaces.
Execution (31): autoware_agnocast_wrapper · autoware_internal_debug_msgs · autoware_internal_planning_msgs · autoware_map_msgs
Runtime consumers in upstream release manifests (including unindexed packages): 1 · autoware_core_planning
- Upstream license declarations
- Apache License 2.0
- Build type
- ament_cmake
- Release repository version
- 1.9.0-1
- member_of_group
- rosidl_interface_packages
Selection evidence, excluding generic scaffolding and test fixtures
- Qualifying runtime consumers
- 1
- Non-generic runtime dependencies
- 29
- Of these, released ROS dependencies
- 27
- Other repositories supplying these ROS dependencies
- 9
Direct dependency declarations
These are manifest declarations, not installed packages. A generic depend applies to build, export and execution. Evaluate conditions and version bounds in the target environment. An unindexed name can be a system dependency key.
Build and export (34)
Execution (31)
Testing (4)
Documentation (0)
No matching record in this snapshot
Group references (0)
No matching record in this snapshot
Direct dependency declarations · Not declared or not confirmed (15)
rosidl_default_generators· Released; no detail page in this catalogament_cmake_auto· Released; no detail page in this catalogautoware_cmake· Released; no detail page in this catalogeigen3_cmake_module· Released; no detail page in this catalogautoware_utils_logging· Released; no detail page in this catalogautoware_utils_rclcpp· Released; no detail page in this catalogautoware_utils_system· Released; no detail page in this catalogeigen· Not a released name in this snapshot; check rosdep or the source workspacegrid_map_core· Released; no detail page in this cataloglibboost-dev· Not a released name in this snapshot; check rosdep or the source workspacerosidl_default_runtime· Released; no detail page in this catalogament_cmake_ros· Released; no detail page in this catalogament_lint_auto· Released; no detail page in this catalogautoware_lint_common· Released; no detail page in this catalogautoware_test_utils· Released; no detail page in this catalog
Which packages directly depend on it?
Counts cover direct declarations in this snapshot only. They are neither install counts nor the full transitive impact.
Build and export (0)
No matching record in this snapshot
Execution (1)
Testing (0)
No matching record in this snapshot
Documentation (0)
No matching record in this snapshot
Verify in your Jazzy environment
In a configured Jazzy shell, confirm the distribution and inspect the installed prefix, manifest and registered executables. Libraries and interface packages may list no executables. These commands are for local checks, not CHINZY deployment or benchmark results.
printenv ROS_DISTRO
ros2 pkg prefix autoware_motion_velocity_planner
ros2 pkg xml autoware_motion_velocity_planner
ros2 pkg executables autoware_motion_velocity_plannerDownload verification checklist (CSV) ↓Jazzy distribution source
· Jazzy · 43a0316dfc39