-
Notifications
You must be signed in to change notification settings - Fork 8
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
Update readme #17
Comments
The driving log image also needs to be updated. |
@MaxJohnsen So the latest version can runs on which version of carla? 0.9.x? |
Hi, this repository only works for Carla 0.8.*. For 0.9.5, we use this repository: https://github.com/MaxJohnsen/carla It is, however, not appropriately documented - so it may be hard to navigate in the code. It is mainly used to capture data and to test the models we have trained. Anything specific you are trying to achieve? |
See https://github.com/MaxJohnsen/carla/tree/master/PythonAPI/custom for the custom code we have written. |
@MaxJohnsen Thanks very much. I want to capture data on my agent. But I don't know how to write the custom control rule to control the my agent. So I want to learnt it on your code. Thanks! And I have a question about what's the driving rule of the car when it runs on 'autopilot' mode? I know you are familiar about Carla, maybe you can help me... Thanks! |
I am happy to help. Just tell me if there is something about the code that is unclear. Carla currently have two separated autopilots: When the server autopilot is active, the carla server (i.e, the c++ code) controls the hero vehicle, and overrides any control commands sent to the server. When you spawn other (non-player) vehicles in carla, they are all controlled by this server autopilot. Currently, you cannot control this autopilot in any way. It will determine it's route randomly realtime. With the latest carla versions, the developer introduced a client autopilot written in Python. This autopilot receives information about the world from the server, and calculates a control signal based on a a route calculated by a A* algorithm (given a start and destination waypoint). You can customize this autopilot to fit your need, but be aware that the autopilot is not complete, and doesn't work as good as the server autopilot in all situations. The most important thing is that you set a fixed FPS for the server, so that the client are able to calculate control signals with the required frequency for stable driving. Maybe we should move this dialog to email instead? My email is [email protected]. |
@MaxJohnsen Thank you! I have already contacted you by email. |
Hello do you have updated it for 0.9.11 0r 0.9.10 ? |
@MaxJohnsen Can i ask you some questions about the code? |
Of course! |
can i have your email? |
|
README.md is not updated with the latest changes from the model driver repository.
The text was updated successfully, but these errors were encountered: