p71924506
/
carla
mirror of https://github.com/carla-simulator/carla.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

More corrections from PR

This commit is contained in:
bernatx 2019-07-05 17:24:50 +02:00 committed by Néstor Subirón
parent fc832d9d26
commit 3f2437b400
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
Docs/recorder_and_playback.md
View File

@ -242,7 +242,7 @@ client.replay_file("col3.log", 302, 0, 143)
![actor blocked](img/actor_blocked1.png)
As we can observe, there is an obstacle that is actually blocking the actor (see red vehicle in).
As we can observe, there is an obstacle that is actually blocking the actor (see red vehicle in the image).
Looking at another actor using:
```py
@ -251,7 +251,7 @@ client.replay_file("col3.log", 75, 0, 104)
![actor blocked](img/actor_blocked2.png)
It is worth noting that it is the same incident but with another vehicle involved in it (the police car in this case).
It is worth noting that it is the same incident but with another vehicle involved in it (i.e. the police car in this case).
The result is sorted by duration, so the actor that is blocked for more time comes first. By checking the vehicle with Id 173 at time 36 seconds, it is evident that it stopped for 336 seconds. To check the cause of it , it would be useful to check how it arrived to that situation by replaying a few seconds before the second 36:

6
Docs/recorder_binary_file_format.md
View File

@ -131,7 +131,7 @@ This packet records the position and orientation of all actors of type **vehicle
#### 3.8 Packet 7: TrafficLight
This packet records the state of all **traffic lights** in the scene. Which means to it stores the state (red, orange or green) and the time it is waiting to change to a new state.
This packet records the state of all **traffic lights** in the scene. Which means that it stores the state (red, orange or green) and the time it is waiting to change to a new state.
![state](img/RecorderTrafficLight.png)
@ -149,7 +149,7 @@ This packet records the animation of the walker. It just saves the **speed** of
### 4. Frame Layout
A frame consists on several packets, where all of them are optional, except the ones that have the **start** and **end** in that frame, that must be there always.
A frame consists of several packets, where all of them are optional, except the ones that have the **start** and **end** in that frame, that must be there always.
![layout](img/RecorderFrameLayout.png)
@ -167,7 +167,7 @@ The layout of the file starts with the **info header** and then follows a collec
Usually, it is a good idea to have all packets regarding events first, and then the packets regarding position and state later.
The event packets are optional, since they appear when they happen, so we could have a layout like this:
The event packets are optional, since they appear when they happen, so we could have a layout like this one:
![layout](img/RecorderLayoutSample.png)