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

question about carla simulation #168

Closed
EcustBoy opened this issue May 27, 2023 · 4 comments
Closed

question about carla simulation #168

EcustBoy opened this issue May 27, 2023 · 4 comments

Comments

@EcustBoy
Copy link

Hi author, I tried to evaluation my own model in carla simulator with town05_short routes, I follow the instructions to use transfuser-2021 branch code and launch simulation, but it seems the route waypoints aren't spawned correctly, I plot town05_short waypoints in map:
image
you can see some start or goal waypoint is out of drivable area, such that the ego car may block during simulation because it thinks it reach the final goal but actually not. I'm sure I directly copy the raw route xml files as you suggest from transfuser-2021 (And when I visualize town05_long route xml files, it seems normal.)

So I wanna ask have you met such strange problem? Is it possible due to carla version? (I notice your project use carla-0.9.10 while I use carla-0.9.12).

This bug really makes me very confused , I'll thanks much for your reply~

@Kait0
Copy link
Collaborator

Kait0 commented May 27, 2023

I would first make sure this isn't a visualization problem.
I think the leaderboard client projects waypoints in the route file onto the nearest lane.
You can visualize the route in CARLA by seeting --debug 1 in the leaderboard_evaluator.py arguments.

@EcustBoy
Copy link
Author

EcustBoy commented May 28, 2023

I would first make sure this isn't a visualization problem. I think the leaderboard client projects waypoints in the route file onto the nearest lane. You can visualize the route in CARLA by seeting --debug 1 in the leaderboard_evaluator.py arguments.

Thanks for your reply~~ I'm quite sure this isn't a visualization code bug, because I copy transfuser-2022 visualization code and I also check each start and goal waypoints coordinates value from the xml file on global map, some waypoints are indeed not in a valid drivable range.

Although client can projects waypoints in the route file onto the nearest lane and client will treat the projected waypoint as a goal, but as I think obviously this is not reasonable. I'm not sure if there's something wrong with the official town05_short file :-) At least I didn't find any bug in my own code.

So I ‘d like to know if you encountered such an exception during the simulation? Is your simulation car normally completing the entire route? (I mean running exactly from start coordinates to goal coordinates descripted by the route xml files)

I'll thanks much for your answer

@Kait0
Copy link
Collaborator

Kait0 commented May 30, 2023

The route xml files are autogenerated and don't necessarily start or end on the road (as said CARLA will project the points to the road).
The agent gets the projected points as input not the original xml data, so this isn't really a problem.
I don't think there is a bug in your code, these route files are just not so clean.

@EcustBoy
Copy link
Author

The route xml files are autogenerated and don't necessarily start or end on the road (as said CARLA will project the points to the road). The agent gets the projected points as input not the original xml data, so this isn't really a problem. I don't think there is a bug in your code, these route files are just not so clean.

Thanks for your answer~~ I think I can continue my testing on town05_short routes, while I still think such route generation method is a bit strange haha :-)

@Kait0 Kait0 closed this as completed May 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants