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

Porting F1Tenth Launch to from Autoware.Auto to Autoware.Universe #50

Open
3 of 13 tasks
mitsudome-r opened this issue Oct 13, 2022 · 1 comment
Open
3 of 13 tasks
Assignees
Labels

Comments

@mitsudome-r
Copy link
Member

mitsudome-r commented Oct 13, 2022

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

This issue is used to track porting efforts to support F1Tenth in Autoware.Universe.

Final goal is to have Autoware.Universe able to run F1Tenth with the following command:

ros2 launch autoware_launch autoware.launch.xml map_path:=$HOME/f1tenth_map vehicle_model:=f1tenth sensor_model:=f1tenth_sensor

Purpose

Port F1Tenth related packages from Autoware.Auto to Autoware.Universe

Possible approaches

Port and refactor packages from Autoware.Auto.

Definition of done

  • port vehicle interface package for vesc Feature: Vehicle Interface autoware.universe#1451
  • port recordreplay_planner package Port Record Replay Planner autoware.universe#1159
  • create vehicle_description(i.e. vehicle parameters) and vehicle_launch(vesc driver launch) package for F1Tenth
  • create sensor_description(i.e. urdf) and sensor_launch(sensor drivers launch) package for F1Tenth
  • add F1Tenth dependency to repos
  • add F1Tenth map launch package
  • add F1Tenth localization launch package
  • add F1Tenth perception launch package (optional)
  • add F1Tenth planning launch package
  • update documentation with F1Tenth launch tutorial
@stale
Copy link

stale bot commented Jan 2, 2023

This pull request has been automatically marked as stale because it has not had recent activity.

@stale stale bot added the stale label Jan 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants