Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Port ' autoware_gnss_poser ' from Autoware Universe to Autoware Core #142

Open
5 of 7 tasks
liuXinGangChina opened this issue Dec 31, 2024 · 1 comment
Open
5 of 7 tasks
Assignees
Labels

Comments

@liuXinGangChina
Copy link

liuXinGangChina commented Dec 31, 2024

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

As part of Autoware Core implementation activity discussed in this thread, I will be porting autoware_gnss_poser from Autoware Universe to Autoware Core.

Purpose

Port autoware_gnss_poser from Autoware Universe to Autoware Core to make autowre-core functional

Possible approaches

Port dependent packages from Universe to Core.

Definition of done

  • Refactor Readme file according to migration guidance
  • Replace Tire4 Msg dependence with Autoware Msg
  • Create draft pr
  • Pr merged
@liuXinGangChina
Copy link
Author

  1. except for some msg depend on package "autoware_core_component_interface_specs", which will be solved by this pr, node can pass complie process with no error
  2. i will upload a draft pr for this node "autoware_gnss_poser "

@liuXinGangChina liuXinGangChina moved this from To Triage to Blocked in Software Working Group Jan 3, 2025
@liuXinGangChina liuXinGangChina changed the title Port ' autoware_gnss_poser ' and 'autoware_universe_utils' from Autoware Universe to Autoware Core Port ' autoware_gnss_poser ' from Autoware Universe to Autoware Core Jan 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Blocked
Development

No branches or pull requests

1 participant