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.

Sign up for GitHub

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

Jump to bottom

different scenarios #20

Open
HandsomeDragon3 opened this issue Jun 24, 2020 · 2 comments
Open

different scenarios #20

HandsomeDragon3 opened this issue Jun 24, 2020 · 2 comments

Comments

@HandsomeDragon3
Copy link

Would the scenarios of following, merging and stopping be taken into consideration?
Look forward to that , HAHA ~!
@fangedward
Copy link
Contributor

fangedward commented Jun 24, 2020 •
edited
Loading

This planner is lower level. It constructs a motion plan given a target trajectory. Following, merging, and stopping need to be implemented upstream in a behavioral planner, which we do not do.

@ICGog
Copy link
Contributor

ICGog commented Jun 24, 2020

We've started a behavioral planner in Pylot, but it does not yet do merging: https://github.com/erdos-project/pylot/blob/master/pylot/planning/behavior_planning_operator.py .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ICGog @HandsomeDragon3 @fangedward