Skip to content

Commit 05a1cff

Browse files
caspar-aipmai
authored andcommitted
Use a common StatePoint definition
For all trajectory-like objects. Signed-off-by: Caspar de Haes <caspar.dehaes@five.ai>
1 parent 9ada7a1 commit 05a1cff

File tree

3 files changed

+31
-55
lines changed

3 files changed

+31
-55
lines changed

osi_common.proto

Lines changed: 30 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -461,3 +461,33 @@ message BaseMoving
461461
//
462462
repeated Vector2d base_polygon = 7;
463463
}
464+
465+
//
466+
// \brief The StatePoint definition
467+
//
468+
// A reference to a time and pose. Typically used in a repeated field to define
469+
// a trajectory.
470+
//
471+
// \note The StatePoint definition does not define mandatory fields.
472+
// The context defines how and what fields are used. For example, in some cases
473+
// only the pose variables are relevant and the timestamp is ignored.
474+
//
475+
message StatePoint
476+
{
477+
// The timestamp of a StatePoint
478+
//
479+
// \note Zero time point does not need to coincide with the UNIX epoch.
480+
//
481+
optional Timestamp timestamp = 1;
482+
483+
// Position in the global coordinate system.
484+
//
485+
// \note Remark: The definition of the reference point follows the
486+
// specification of the \c BaseMoving message.
487+
//
488+
optional Vector3d position = 2;
489+
490+
// Orientation in the global coordinate system.
491+
//
492+
optional Orientation3d orientation = 3;
493+
}

osi_trafficcommand.proto

Lines changed: 0 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -119,36 +119,6 @@ message TrafficAction
119119
optional TeleportAction teleport_action = 12;
120120
}
121121

122-
//
123-
// \brief The StatePoint definition
124-
//
125-
// \note The StatePoint definition does not define mandatory fields.
126-
// The context defines how and what fields are used.
127-
// For example: FollowPathAction does not use timestamp in contrast to
128-
// FollowTrajectoryAction.
129-
//
130-
message StatePoint
131-
{
132-
// The timestamp of a StatePoint
133-
//
134-
// \note Zero time point does not need to coincide with the UNIX epoch.
135-
//
136-
optional Timestamp timestamp = 1;
137-
138-
// Position in the global coordinate system.
139-
//
140-
// The position refers to the center (x,y,z) of the bounding box.
141-
//
142-
// \note Remark: The definition of the reference point follows the
143-
// specification of the \c BaseMoving message.
144-
//
145-
optional Vector3d position = 2;
146-
147-
// Orientation in the global coordinate system.
148-
//
149-
optional Orientation3d orientation = 3;
150-
}
151-
152122
//
153123
// \brief The action header
154124
//

osi_trafficupdate.proto

Lines changed: 1 addition & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -71,30 +71,6 @@ message TrafficUpdate
7171
// behaviours without performing prediction for all external traffic
7272
// participants.
7373
//
74-
repeated FutureTrajectoryNode future_trajectory = 2;
75-
76-
//
77-
// \brief The future node is a single point in time as part of a future
78-
// trajectory which defines the pose, velocity, acceleration, etc. at
79-
// that point.
80-
// See the FutureTrajectory message for details and context.
81-
//
82-
message FutureTrajectoryNode
83-
{
84-
// The future timestamp for the trajectory node. Zero time is arbitrary
85-
// but must be identical for all messages. Zero time does not need to
86-
// coincide with the UNIX epoch. Recommended is the starting time point of
87-
// the simulation.
88-
//
89-
// \note This must be in the future compared to the timestamp in the top
90-
// level traffic update message.
91-
//
92-
optional Timestamp timestamp = 1;
93-
94-
// Traffic participant data for the future trajectory node.
95-
//
96-
// \note Dimensions and base polygon are ignored.
97-
optional BaseMoving future_point = 2;
98-
}
74+
repeated StatePoint future_trajectory = 2;
9975
}
10076
}

0 commit comments

Comments
 (0)