The iSAFT SpaceWire Simulator / Recorder is an advanced Data Front End with traffic generation capabilities that simulates SpaceWire devices or Instruments, enabling S/C integration tests before the availability of Flight Models. It also constitutes a high performing, modern network traffic capture, recording and analysis tool for the.

This is one of the advanced CARLA features. It allows to record and reenact a simulation while providing with a complete log of the events happened and a few queries to ease the trace and study of those.
To learn about the generated file and its specifics take a look at this reference.

• Simulation playback:
  • Setting a time factor
• Queries:
  • Collisions
  • Blocked actors

Recording

Detox Recorder is a utility for recordings steps for a Detox test as you use your app in Simulator. After recording the test, add expectations that check if interface elements are in the expected state. SimFDR is a revolutionary product for flight simulator enthusiasts. It includes the world's most advanced digital Flight Data Recorder, which logs over 100 flight parameters (including payware aircraft system states) several times a second - and combines it with a cloud-based logbook that persists all of your flights and retains them forever. You can record a portion of the screen with built-in screenshot utility: Press Shift-Command-5 to show a control panel. Select a portion of the screen you want to record. That would be the iPhone simulator. Click to stop recording. A thumbnail will appear at the bottom right corner of the screen. You can edit it before saving.

All the data is written in a binary file on the server side only. However, the recorder is managed using the carla.Client.
To reenact the simulation, actors will be updated on every frame according to the data contained in the recorded file. Actors that appear in the simulation will be either moved or re-spawned to emulate the recording. Those that do not appear in the recording will continue their way as if nothing happened.

Important

By the end of the playback, vehicles will be set to autopilot, but pedestrians will stop at their current location.

The information registered by the recorder basically includes:

• Actors: Creation and destruction.
• Traffic lights: State changes.
• Vehicles and pedestrians: Position and orientation.

To start recording there is only need for a file name. Using , / or : characters in the file name will define it as an absolute path. If no path is detailed, the file will be saved in CarlaUE4/Saved.

To stop the recording, the call is also straightforward:

Note

As an estimate: 1h recording with 50 traffic lights and 100 vehicles takes around 200MB in size.

Simulation playback

A playback can be started at any point during a simulation only specifying the file name.

Additionally, this method allows for some parameters to specify which segment of the recording is reenacted:

Note

These parameters allows to recall an event and then let the simulation run free, as vehicles will be set to autopilot when the recording stops.

Setting a time factor

The time factor will determine the playback speed.

It can be changed any moment without stopping the playback, using the following API call:

Important

Over 2.0 position interpolation is disabled and just updated. Pedestrians' animations are not affected by the time factor.

For instance, with a time factor of 20x traffic flow is easily appreciated:

Recorded file

The details of a recording can be retrieved using a simple API call. By default, it only retrieves those frames where an event was registered, but setting the parameter show_all would return all the information for every frame. The specifics on how the data is stored are detailed in the recorder's reference.
The following example only would retrieve remarkable events:

• Opening information: map, date and time when the simulation was recorded.

• Frame information: any event that could happen (actor spawning/destruction, collisions...). The output contains the actor's ID and some additional information.

• Closing information: a summary of number of frames and total time recorded.

The output result should be similar to this one:

Queries

Collisions

In order to record collisions, vehicles must have a collision detector attached. The collisions registered by the recorder can be queried using arguments to filter the type of the actors involved in the collisions. For example, h identifies actors whose role_name = hero, usually assigned to vehicles managed by the user.
Currently, the actor types that can be used in the query are:

• h = Hero
• v = Vehicle
• w = Walker
• t = Traffic light
• o = Other
• a = Any

Note

The manual_control.py script automatically assigns the role_name of the vehicle to hero besides providing control over it.

The API call to query collisions requires two of the previous flags to filter the collisions. The following example would show collisions registered between vehicles and any other object:

The output summarizes time of the collision and type, ID and description of the actors involved. It should be similar to this one:

Important

As it is the hero or ego vehicle who registers the collision, this will always be Actor 1.

To understand how that collision happened, it could be a good idea to replay it just moments before the event:

In this case, the playback showed this:

Blocked actors

This query is used to detect vehicles that where stucked during the recording. An actor is considered blocked if it does not move a minimum distance in a certain time. This definition is made by the user during the query:

Note

Take into account that vehicles are stopped at traffic lights sometimes for longer than expected.

For the sake of comprehension, let's make an example to look for vehicles stopped (moving less than 1 meter during 60 seconds):

The output is sorted by duration, which states how long it took to stop being 'blocked' and move the min_distance:

In this example, the vehicle 173 was stopped for 336 seconds at time 36 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:

Sample python scripts

Simulator Record Screen

Some of the provided scripts in PythonAPI/examples facilitate the use of the recorder:

• start_recording.py: starts the recording. Optionally actors can be spawned at the beginning and duration of the recording set.

• start_replaying.py: starts the playback of a recording. Starting time, duration and actor to follow can be set.

Screen Recorder Simulator Ios

• show_recorder_file_info.py: shows all the information in the recording file.
  Two modes of detail: by default it only shows frames where some event is recorded. The second shows all information for all frames.

• show_recorder_collisions.py: shows recorded collisions between two actors of type A and B defined using a series of flags: -t = vv would show all collisions between vehicles.

• show_recorder_actors_blocked.py: shows a register for vehicles considered blocked. Actors are considered blocked when not moving a minimum distance in a certain time.

Now it is time to experiment for a while. Use the recorder to playback a simulation, trace back events, make changes to see new outcomes. Feel free to say your word in the CARLA forum about this matter: