Datasets:

Modalities:
Text
Formats:
json
Languages:
English
ArXiv:
Libraries:
Datasets
Dask
License:
PurpleSand commited on
Commit
14f6800
Β·
verified Β·
1 Parent(s): 720dd2b

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +122 -3
README.md CHANGED
@@ -1,3 +1,122 @@
1
- ---
2
- license: cc-by-nc-4.0
3
- ---
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ license: cc-by-nc-4.0
3
+ language:
4
+ - en
5
+ ---
6
+ # COMMAND Dataset
7
+
8
+ This is the README for the **COMMAND** dataset.
9
+
10
+ ## Dataset Structure
11
+
12
+ The **COMMAND_dataset** is organized as follows:
13
+ ```
14
+ COMMAND_dataset/
15
+ β”œβ”€ README.md # Documentation for the dataset
16
+ β”œβ”€ map_asset/ # Directory containing map assets
17
+ β”‚ β”œβ”€ map_list.yml # Information of all maps
18
+ β”‚ └─ maps/ # Folder containing individual maps
19
+ β”‚ └─ <map_name>/ # Folder for a specific map
20
+ β”‚ β”œβ”€ .png # Image representation of the map
21
+ β”‚ └─ .yml # Map info (for ROS map server)
22
+ β”œβ”€ bagfiles/ # Directory containing ROS bagfiles
23
+ β”‚ └─ .bag # ROS bagfile with unique identifier
24
+ β”œβ”€ scenarios/ # Directory containing scenario information
25
+ β”‚ β”œβ”€.json # Scenario schema
26
+ └─ └─.npy # Sketch instructions
27
+ ```
28
+ ---
29
+
30
+ ## Dataset Overview
31
+ ### Statistics
32
+
33
+ | Environment | Office (sim_office) | Street (Road) (sim_street_road) | Street (Sidewalk) (sim_street_sidewalk) | Orchard (sim_orchard) |
34
+ |--------------------|---------------------|---------------------------------|-----------------------------------------|-----------------------|
35
+ | Count | 2,253 | 400 | 402 | 262 |
36
+ | Avg. Time | 31s | 57s | 103s | 172s |
37
+ | Avg. Distance | 32.8m | 80.4m | 150.0m | 191.6m |
38
+ | Avg. FD (P / M) | 1.05 / 1.77 | 0.97 / 2.02 | 3.03 / 3.50 | 1.91 / 3.76 |
39
+ | % of Misleading | 31% | 51% | 50% | 39% |
40
+
41
+ **Note:** These values differ slightly from the paper because the data version history is missing.
42
+
43
+ ## Directory Details
44
+
45
+ ### `map_asset/`
46
+
47
+ - **`map_list.yml`**: Contains metadata about all maps in the dataset.
48
+ - **`maps/`**: Holds individual map folders. Each folder typically includes:
49
+ - **`.png`**: An image representation of the map.
50
+ - **`.yml`**: Detailed map information (compatible with the [ROS map server](http://wiki.ros.org/map_server)).
51
+
52
+ ### `bagfiles/`
53
+
54
+ - Contains ROS bagfiles, each identified by a unique UUID (e.g., **`<uuid>.bag`**).
55
+
56
+
57
+ ### `scenarios/`
58
+
59
+ - **`<uuid>.json`**: Scenario schema file describing the scenario.
60
+ - **`<uuid>.npy`**: Scenario annotations(sketch instructions). It contains a list of (y, x) pixel coordinates on the corresponding `sketch_map_name` map image.
61
+
62
+ ---
63
+
64
+ ### Topics in ROS Bagfiles
65
+ 1. **`/clock`**
66
+ - **Message Type**: `rosgraph_msgs/msg/Clock`
67
+ - **Description**: Publishes the current simulated time in a ROS system. Useful for synchronizing sensor data and events in simulation.
68
+
69
+ 2. **`/cmd_vel`**
70
+ - **Message Type**: `geometry_msgs/msg/Twist`
71
+ - **Description**: Represents commanded linear and angular velocities for a robot, typically used to drive mobile robots (e.g., differential drive, holonomic platforms).
72
+
73
+ 3. **`/imu`**
74
+ - **Message Type**: `sensor_msgs/msg/Imu`
75
+ - **Description**: Provides data from an Inertial Measurement Unit, including orientation (as a quaternion), angular velocity (radians/second), and linear acceleration (m/sΒ²). Often used for state estimation and control feedback.
76
+
77
+ 4. **`/joy`**
78
+ - **Message Type**: `sensor_msgs/msg/Joy`
79
+ - **Description**: Reports the state of joystick (gamepad) axes and buttons, enabling teleoperation or manual input to the robot.
80
+
81
+ 5. **`/odom`**
82
+ - **Message Type**: `nav_msgs/msg/Odometry`
83
+ - **Description**: Offers an estimate of the robot’s position and velocity in free space. It is ground-truth data in simulation.
84
+
85
+ 6. **`/rgb_front/camera_info`, `/rgb_left/camera_info`, `/rgb_right/camera_info`**
86
+ - **Message Type**: `sensor_msgs/msg/CameraInfo`
87
+ - **Description**: Contains intrinsic and extrinsic parameters of a camera.
88
+
89
+ 7. **`/rgb_front/compressed`, `/rgb_left/compressed`, `/rgb_right/compressed`**
90
+ - **Message Type**: `sensor_msgs/msg/CompressedImage`
91
+ - **Description**: Encoded image data (JPEG/PNG) from a camera feed.
92
+
93
+ 8. **`/tf`**
94
+ - **Message Type**: `tf2_msgs/msg/TFMessage`
95
+ - **Description**: Provides a odom to base_link transform.
96
+
97
+ ### Schema of Scenario JSON
98
+ - **`semantic_uuid`**: A unique identifier for the scenario. It is a combination of the map name, the scenario name, and either β€œprecise” or β€œmisleading,” followed by the scenario number.
99
+ - **`map_name`**: The name of the map where the scenario is located.
100
+ - **`sketch_map_name`**: The name of the map where the sketch instructions are provided.
101
+ - **`start`**: The starting point of the robot. This can be a specific point or a random point.
102
+ - **`end`**: The ending point of the robot, predefined in annotated maps.
103
+ - **`drive_map_name`**: The name of the map that the robot uses for navigation, usually an occupancy map.
104
+ - **`model_guideline`**: Instructions for the robot to follow during the scenario. These will serve as input to the model for training.
105
+
106
+ Example
107
+
108
+ ```json
109
+ {
110
+ "semantic_uuid": "sim_office/coffee_delivery/precise/3/42",
111
+ "map_name": "sim_office",
112
+ "sketch_map_name": "annotated_occupancy_map",
113
+ "start": "(random)",
114
+ "end": "4",
115
+ "drive_map_name": "occupancy_map",
116
+ "model_guideline": "You are an indoor food-serving robot.\n\nYou must follow these driving instructions:\n1. You must avoid collisions.\n2. You should prioritize reaching the final destination.\n3. You should follow the Trajectory Instruction.\n a. If the Trajectory Instruction cannot be followed due to any obstacles, you should deviate to bypass the obstacle.\n b. You should try to evade any identifiable obstacles.\n4. You should maintain a constant driving speed."
117
+ }
118
+ ```
119
+
120
+ ---
121
+ license: cc-by-nc-4.0
122
+ ---