Skip to content

Commit 91f26fe

Browse files
committed
Fixed Doxygen documentation
1 parent a4498a8 commit 91f26fe

16 files changed

+830
-830
lines changed

osi_common.proto

Lines changed: 81 additions & 81 deletions
Original file line numberDiff line numberDiff line change
@@ -4,169 +4,169 @@ option optimize_for = SPEED;
44

55
package osi;
66

7-
/**
8-
* The interface version number.
9-
*/
7+
///
8+
/// The interface version number.
9+
///
1010
message InterfaceVersion
1111
{
12-
// The field containing the version number. Should be left on default, not to be modified by sender. Increments will
13-
// happen as part of changes to the whole interface.
12+
/// The field containing the version number. Should be left on default, not to be modified by sender. Increments will
13+
/// happen as part of changes to the whole interface.
1414
optional uint32 major = 1 [default = 2];
1515
optional uint32 minor = 2 [default = 0];
1616
optional uint32 patch = 3 [default = 0];
1717
}
1818

19-
/**
20-
* A cartesian 3D vector for positions, velocities or accelerations.
21-
* Units are [m] for positions, [m/s] for velocities and [m/s^2] for accelerations.
22-
*/
19+
///
20+
/// A cartesian 3D vector for positions, velocities or accelerations.
21+
/// Units are [m] for positions, [m/s] for velocities and [m/s^2] for accelerations.
22+
///
2323
message Vector3d
2424
{
25-
// The x coordinate
25+
/// The x coordinate
2626
optional double x = 1;
2727

28-
// The y coordinate
28+
/// The y coordinate
2929
optional double y = 2;
3030

31-
// The z coordinate
31+
/// The z coordinate
3232
optional double z = 3;
3333
}
3434

35-
/**
36-
* A timestamp.
37-
* Names and types of fields chosen in accordance with google/protobuf/timestamp.proto to allow a possible switch in the
38-
* future. Definition of zero point in time differs and does not use Unix epoch.
39-
*/
35+
///
36+
/// A timestamp.
37+
/// Names and types of fields chosen in accordance with google/protobuf/timestamp.proto to allow a possible switch in the
38+
/// future. Definition of zero point in time differs and does not use Unix epoch.
39+
///
4040
message Timestamp
4141
{
42-
// The number of seconds since start of the simulation / system / vehicle. Unit: [s].
42+
/// The number of seconds since start of the simulation / system / vehicle. Unit: [s].
4343
optional int64 seconds = 1;
4444

45-
// The number of nanoseconds since the start of the last second. Unit: [ns].
45+
/// The number of nanoseconds since the start of the last second. Unit: [ns].
4646
optional int32 nanos = 2;
4747
}
4848

49-
/**
50-
* A 3D dimension, e.g. parameters of a 3D bounding box.
51-
* Units are all [m].
52-
*/
49+
///
50+
/// A 3D dimension, e.g. parameters of a 3D bounding box.
51+
/// Units are all [m].
52+
///
5353
message Dimension3d
5454
{
55-
// The width of the bounding box.
55+
/// The width of the bounding box.
5656
optional double width = 1;
5757

58-
// The length of the bounding box.
58+
/// The length of the bounding box.
5959
optional double length = 2;
6060

61-
//The height of the bounding box.
61+
///The height of the bounding box.
6262
optional double height = 3;
6363
}
6464

65-
/**
66-
* A 3D orientation, orientation rate or orientation acceleration.
67-
* Units are [rad] for orientation, [rad/s] for rates and [rad/s^2] for accelerations. The preferred angular range is
68-
* (-pi, pi]. See http://planning.cs.uiuc.edu/node102.html for a definition of the rotational order. The rotations are
69-
* to be performed roll first, then the pitch, and finally the yaw. Rotations are defined in the reference coordinate
70-
* frame around z (=yaw), y (=pitch) and x (=roll), not in the body frame of the object. Rotations with positive angles
71-
* are performed counter-clockwise.
72-
*
73-
* Roll/Pitch are 0 if objects xy-plane corresponds it's parent xy-plane.
74-
* Yaw is 0 if the x axis is parallel to the x axis of it's parent coordinate system.
75-
*/
65+
///
66+
/// A 3D orientation, orientation rate or orientation acceleration.
67+
/// Units are [rad] for orientation, [rad/s] for rates and [rad/s^2] for accelerations. The preferred angular range is
68+
/// (-pi, pi]. See http://planning.cs.uiuc.edu/node102.html for a definition of the rotational order. The rotations are
69+
/// to be performed roll first, then the pitch, and finally the yaw. Rotations are defined in the reference coordinate
70+
/// frame around z (=yaw), y (=pitch) and x (=roll), not in the body frame of the object. Rotations with positive angles
71+
/// are performed counter-clockwise.
72+
///
73+
/// Roll/Pitch are 0 if objects xy-plane corresponds it's parent xy-plane.
74+
/// Yaw is 0 if the x axis is parallel to the x axis of it's parent coordinate system.
75+
///
7676
message Orientation3d
7777
{
78-
// The roll angle/rate/acceleration.
78+
/// The roll angle/rate/acceleration.
7979
optional double roll = 1;
8080

81-
// The pitch angle/rate/acceleration.
81+
/// The pitch angle/rate/acceleration.
8282
optional double pitch = 2;
8383

84-
// The yaw angle/rate/acceleration.
84+
/// The yaw angle/rate/acceleration.
8585
optional double yaw = 3;
8686
}
8787

88-
/**
89-
* A common identifier.
90-
* Has to be unique among all simulated items at any given time. For ground truth, the identifier of an item (object,
91-
* lane, sign, etc.) must remain stable over its lifetime. Identifier values might be only be reused if the available
92-
* address space is exhausted and the specific values have not been in use for several timesteps. Sensor specific
93-
* tracking ids have no restrictions and should behave according to the sensor specifications.
94-
*/
88+
///
89+
/// A common identifier.
90+
/// Has to be unique among all simulated items at any given time. For ground truth, the identifier of an item (object,
91+
/// lane, sign, etc.) must remain stable over its lifetime. Identifier values might be only be reused if the available
92+
/// address space is exhausted and the specific values have not been in use for several timesteps. Sensor specific
93+
/// tracking ids have no restrictions and should behave according to the sensor specifications.
94+
///
9595
message Identifier
9696
{
97-
// The identifier's value.
97+
/// The identifier's value.
9898
optional uint64 value = 1;
9999
}
100100

101-
/**
102-
* Specifies the mounting position of a sensor. Details are specified in each instance where MountingPosition is used.
103-
*/
101+
///
102+
/// Specifies the mounting position of a sensor. Details are specified in each instance where MountingPosition is used.
103+
///
104104
message MountingPosition
105105
{
106-
// Offset position relative to specified reference coordinate system.
106+
/// Offset position relative to specified reference coordinate system.
107107
optional Vector3d position = 1;
108108

109-
// Orientation offset relative to specified reference coordinate system.
109+
/// Orientation offset relative to specified reference coordinate system.
110110
optional Orientation3d orientation = 2;
111111
}
112112

113-
/**
114-
* A polar representation for a point / vector in 3D space used for low level representations of radar detections.
115-
* Units are [m] for radial distance and [rad] for azimuth and elevation angles. If azimuth and elevation are zero, the
116-
* referenced point is directly in front / vector is pointing directly in the central viewing direction of the sensor.
117-
*/
113+
///
114+
/// A polar representation for a point / vector in 3D space used for low level representations of radar detections.
115+
/// Units are [m] for radial distance and [rad] for azimuth and elevation angles. If azimuth and elevation are zero, the
116+
/// referenced point is directly in front / vector is pointing directly in the central viewing direction of the sensor.
117+
///
118118
message Polar3d
119119
{
120-
// The radial distance.
120+
/// The radial distance.
121121
optional double distance = 1;
122122

123-
// The azimuth (horizontal) angle.
123+
/// The azimuth (horizontal) angle.
124124
optional double azimuth = 2;
125125

126-
// The elevation (vertical) angle.
126+
/// The elevation (vertical) angle.
127127
optional double elevation = 3;
128128
}
129129

130-
/**
131-
* The base attributes of object or similar that is stationary.
132-
* This includes the StationaryObject, TrafficSign, TrafficLight, RoadMarking messages.
133-
*/
130+
///
131+
/// The base attributes of object or similar that is stationary.
132+
/// This includes the StationaryObject, TrafficSign, TrafficLight, RoadMarking messages.
133+
///
134134
message BaseStationary
135135
{
136-
// The 3D dimension of the landmark (bounding box):
136+
/// The 3D dimension of the landmark (bounding box):
137137
optional Dimension3d dimension = 1;
138138

139-
// The reference point for position and rotation (orientation): center (x, y, z) of bounding box.
139+
/// The reference point for position and rotation (orientation): center (x, y, z) of bounding box.
140140
optional Vector3d position = 2;
141141

142-
// The relative orientation of the landmark w.r.t its parent frame.
142+
/// The relative orientation of the landmark w.r.t its parent frame.
143143
optional Orientation3d orientation = 3;
144144
}
145145

146-
/**
147-
* The base attributes of each object that is moving.
148-
* This includes the MovingObject messages.
149-
*/
146+
///
147+
/// The base attributes of each object that is moving.
148+
/// This includes the MovingObject messages.
149+
///
150150
message BaseMoving
151151
{
152-
// The 3D dimension of the object (bounding box):
152+
/// The 3D dimension of the object (bounding box):
153153
optional Dimension3d dimension = 1;
154154

155-
// The reference point for position and rotation (orientation): center (x, y, z) of bounding box.
155+
/// The reference point for position and rotation (orientation): center (x, y, z) of bounding box.
156156
optional Vector3d position = 2;
157157

158-
// The relative orientation of the object w.r.t its parent frame.
158+
/// The relative orientation of the object w.r.t its parent frame.
159159
optional Orientation3d orientation = 3;
160160

161-
// The relative velocity of the object w.r.t. its parent frame and parent velocity.
162-
// Obviously, the velocity becomes global/absolute if the parent frame does not move.
161+
/// The relative velocity of the object w.r.t. its parent frame and parent velocity.
162+
/// Obviously, the velocity becomes global/absolute if the parent frame does not move.
163163
optional Vector3d velocity = 4;
164164

165-
// The relative acceleration of the object w.r.t. its parent frame and parent acceleration.
166-
// Obviously, the acceleration becomes global/absolute if the parent frame is not accelerating.
165+
/// The relative acceleration of the object w.r.t. its parent frame and parent acceleration.
166+
/// Obviously, the acceleration becomes global/absolute if the parent frame is not accelerating.
167167
optional Vector3d acceleration = 5;
168168

169-
// The relative orientation rate of the object w.r.t. its parent frame and parent orientation rate.
170-
// Obviously, the orientation rate becomes global/absolute if the parent frame is not rotating.
169+
/// The relative orientation rate of the object w.r.t. its parent frame and parent orientation rate.
170+
/// Obviously, the orientation rate becomes global/absolute if the parent frame is not rotating.
171171
optional Orientation3d orientation_rate = 6;
172172
}

osi_datarecording.proto

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -6,30 +6,30 @@ import "osi_sensordata.proto";
66

77
package osi;
88

9-
/**
10-
* (Time) Series of SensorData messages that may be used for data recording or internal buffering by some sensor models.
11-
*/
9+
///
10+
/// (Time) Series of SensorData messages that may be used for data recording or internal buffering by some sensor models.
11+
///
1212
message SensorDataSeries
1313
{
14-
// List of sensor data messages for subsequent timesteps.
14+
/// List of sensor data messages for subsequent timesteps.
1515
repeated SensorData sensor_data = 1;
1616
}
1717

18-
/**
19-
* List of SensorData interface copies, one for each sensor in the vehicle.
20-
* Can be used to bundle output of multiple sensors in one transmission.
21-
*/
18+
///
19+
/// List of SensorData interface copies, one for each sensor in the vehicle.
20+
/// Can be used to bundle output of multiple sensors in one transmission.
21+
///
2222
message SensorDataList
2323
{
24-
// List of sensor data for multiple sensors at a specific timestep.
24+
/// List of sensor data for multiple sensors at a specific timestep.
2525
repeated SensorData sensor = 1;
2626
}
2727

28-
/**
29-
* List of sensors where each element contains a time series of SensorData messages.
30-
*/
28+
///
29+
/// List of sensors where each element contains a time series of SensorData messages.
30+
///
3131
message SensorDataSeriesList
3232
{
33-
// List of sensor data for multiple sensors at subsequent timesteps.
33+
/// List of sensor data for multiple sensors at subsequent timesteps.
3434
repeated SensorDataSeries sensor = 1;
3535
}

0 commit comments

Comments
 (0)