7.0.0

Description

Abstract

• replace autoware_auto_xx_msgs with autoware_xx_msgs
• use only one source for /autoware/state
• finish supporting awf/autoware architecture_type ( traffic light for autoware_auto_perception_msgs )
• use awf/autoware/20240605 as default architecture_type

Background

Details

simple message migrations

• autoware_auto_vehicle_msgs -> autoware_vehicle_msgs
  • ControlModeReport.msg
  • GearReport.msg
  • SteeringReport.msg
  • TurnIndicatorsReport.msg
  • VelocityReport.msg
  • ControlModeCommand.srv
• autoware_auto_perception_msgs -> autoware_perception_msgs
  • TrackedObjects.msg
  • TrackedObject.msg
  • DetectedObjects.msg
  • DetectedObject.msg
  • ObjectClassification.msg
  • DetectedObjectKinematics.msg
  • Shape.msg

complicated message migrations

1 vs 1

before	after
autoware_auto_control_msgs/AckermannControlCommand	autoware_control_msgs/Control
autoware_auto_planning_msgs/PathWithLaneId	tier4_planning_msgs/PathWithLaneId
autoware_auto_map_msgs/HADMapBin	autoware_map_msgs/LaneletMapBin

others

before	after
autoware_system_msgs/AutowareState autoware_auto_system_msgs/AutowareState	autoware_system_msgs/AutowareState
autoware_auto_perception_msgs/TrafficSignalArray autoware_perception_msgs/TrafficSignalArray autoware_perception_msgs/TrafficLightGroupArray	autoware_perception_msgs/TrafficSignalArray autoware_perception_msgs/TrafficLightGroupArray

References

Destructive Changes

After this pull-request, scenario_simulator_v2 does not support autoware_auto_xx_msgs for interfaces.
To use with autoware_auto_xx_msgs, please use older versions of scenario_simulator_v2.

Known Limitations

None

Related Issues