Skip to content

planning/control component is dependent on the packages outside of planning/control component #8805

Open
@youtalk

Description

@youtalk

Checklist

  • I've read the contribution guidelines.
  • I've searched other issues and no duplicate issues were found.
  • I've agreed with the maintainers that I can plan this task.

Description

autowarefoundation/autoware#5194 found that the planning/control component is dependent on the following packages outside of the planning/control component.

  • map/map_loader
  • map/autoware_map_projection_loader
  • sensing/autoware_pcl_extensions
  • sensing/autoware_pointcloud_preprocessor

Since the dependencies will no longer follow a parent-child relationship, the components become tightly coupled.

Purpose

Ensure that there are no dependency packages spanning across components. Connections between components should depend only on the core packages or the autoware.universe/common packages.

Possible approaches

Ensure that there are no dependency packages spanning across components. Connections between components should depend only on the core packages or the autoware.universe/common packages.

Definition of done

The planning/control packages will no longer directly depend on the following packages.

  • map/map_loader
  • map/autoware_map_projection_loader
  • sensing/autoware_pcl_extensions
  • sensing/autoware_pointcloud_preprocessor

Metadata

Metadata

Assignees

Labels

component:controlVehicle control algorithms and mechanisms. (auto-assigned)component:mapMap creation, storage, and loading. (auto-assigned)component:planningRoute planning, decision-making, and navigation. (auto-assigned)component:sensingData acquisition from sensors, drivers, preprocessing. (auto-assigned)

Type

No type

Projects

Status

In Progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions