DriveWorks SDK Reference
3.0.4260 Release
For Test and Development only

/dvs/git/dirty/gitlab-master_av/dw/sdk/tools/recorder/apps/chop/README-chop.md
Go to the documentation of this file.
1 # Copyright (c) 2017-2019, NVIDIA CORPORATION. All rights reserved.
2 
3 @page dwx_recording_chopping_tool Recording Chopping Tool
4 
5 This tool is available on the x86 Host System and NVIDIA DRIVE<sup>&trade;</sup> OS Linux.
6 
7 A tool for clipping recorded data. Allows to cut information from input recordings
8 based on given timestamp or event range.
9 
10 @note SW Release Applicability: This tool is available in both <b>NVIDIA DriveWorks</b> and <b>NVIDIA DRIVE Software</b> releases.
11 
12 # Usage
13 
14  ./chop [--config=path_to_json_config_file]
15  [--camera=path_to_camera_data]
16  [--camera-out=output_path]
17  [--timestamp_file=path_to_file_containing_timestamps]
18  [--gps=path_to_gps_data]
19  [--gps-out=output_path]
20  [--imu=path_to_imu_data]
21  [--imu-out=output_path]
22  [--can=path_to_can_data]
23  [--can-out=output_path]
24  [--lidar=path_to_lidar_data]
25  [--lidar-out=output_path]
26  [--radar=path_to_radar_data]
27  [--radar-out=output_path]
28  [--timestamp_start=start_timestamp_value]
29  [--timestamp_end=end_timestamp_value]
30  [--event_start=start_event_index]
31  [--event_end=end_event_index]
32  [--num_events=number_of_events_to_capture]
33  [--force-create-seek]
34  [--disable-output-verification]
35  [--ignore-missing-timestamp]
36 
37 # Examples
38 
39  ./chop --camera=/path_to_video --timestamp_file=/path_to_existing_timestamp_file --num_events=20
40  Capture the first 20 frames from provided video. Cut associated timestamp file.
41 
42  ./chop --camera=/path_to_video.h264 --ignore-missing-timestamp --num_events=20
43  Capture the first 20 frames from provided video. Force cut of the video file only and ignore missing timestamp file.
44 
45  ./chop --lidar=/lidar_file --radar=/radar_file --timestamp_start=1506453354917264
46  Cut all lidar and radar packets starting timestamp 1506453354917264 to the end of the stream.
47 
48  ./chop --can=/can_file --timestamp_start=1506453354917264 --num_events=50
49  Chop 50 can messages starting from timestamp 1506453354917264.
50 
51  ./chop --imu=/imu_file --event_start=10 --event_end=11
52  Capture events 10 and 11.
53 
54  ./chop --imu=/imu_file --event_start=10 --event_end=11 --num_events=20
55  Capture 20 events from event 10. --event_end argument is ignored.
56 
57  ./chop --config=/path_to_config_file
58  Chop recordings listed in provided config file, or create template config if specified file does not exist.
59 
60 # Configuration file
61 
62 Template configuration file looks like:
63 
64 ```
65 {
66  "version": "0.1",
67  "timestamp_start": 0,
68  "timestamp_end": 0,
69  "event_start": 0,
70  "event_end": 0,
71  "num_events": 0,
72 
73  "camera" : [
74  {
75  "input_file": "",
76  "output_file": "",
77  "timestamp_file": ""
78  }
79  ],
80 
81  "can" : [
82  {
83  "input_file": "",
84  "output_file": ""
85  }
86  ],
87 
88  "gps" : [
89  {
90  "input_file": "",
91  "output_file": ""
92  }
93  ],
94 
95  "imu" : [
96  {
97  "input_file": "",
98  "output_file": ""
99  }
100  ],
101 
102  "lidar" : [
103  {
104  "input_file": "",
105  "output_file": ""
106  }
107  ],
108 
109  "radar" : [
110  {
111  "input_file": "",
112  "output_file": ""
113  }
114  ]
115 }
116 ```
117 
118 Parameters provided in configuration file are always primary with respect to those specified in command line.
119 That means if the range specified in both command line and configuration file the latter are chosen even if
120 they incorrect or zero. Thus if you want to use first variant then completely remove corresponding sections
121 from json config.
122 
123 # Limitations
124 
125 - For H264/H265/mp4 videos the interval is adjusted to start from the previous IDR frame and end at the next IDR frame.
126 - Chopping H264/H265 videos requires AUD units
127 - NMEA ASCII gps recordings are no longer supported