Skip to content

Commit 88f9141

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 2918b18 commit 88f9141

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
@@ -457,3 +457,33 @@ message BaseMoving
457457
//
458458
repeated Vector2d base_polygon = 7;
459459
}
460+
461+
//
462+
// \brief The StatePoint definition
463+
//
464+
// A reference to a time and pose. Typically used in a repeated field to define
465+
// a trajectory.
466+
//
467+
// \note The StatePoint definition does not define mandatory fields.
468+
// The context defines how and what fields are used. For example, in some cases
469+
// only the pose variables are relevant and the timestamp is ignored.
470+
//
471+
message StatePoint
472+
{
473+
// The timestamp of a StatePoint
474+
//
475+
// \note Zero time point does not need to coincide with the UNIX epoch.
476+
//
477+
optional Timestamp timestamp = 1;
478+
479+
// Position in the global coordinate system.
480+
//
481+
// \note Remark: The definition of the reference point follows the
482+
// specification of the \c BaseMoving message.
483+
//
484+
optional Vector3d position = 2;
485+
486+
// Orientation in the global coordinate system.
487+
//
488+
optional Orientation3d orientation = 3;
489+
}

osi_trafficcommand.proto

Lines changed: 0 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -100,36 +100,6 @@ message TrafficAction
100100
optional EndActionsAction end_actions_action = 7;
101101
}
102102

103-
//
104-
// \brief The StatePoint definition
105-
//
106-
// \note The StatePoint definition does not define mandatory fields.
107-
// The context defines how and what fields are used.
108-
// For example: FollowPathAction does not use timestamp in contrast to
109-
// FollowTrajectoryAction.
110-
//
111-
message StatePoint
112-
{
113-
// The timestamp of a StatePoint
114-
//
115-
// \note Zero time point does not need to coincide with the UNIX epoch.
116-
//
117-
optional Timestamp timestamp = 1;
118-
119-
// Position in the global coordinate system.
120-
//
121-
// The position refers to the center (x,y,z) of the bounding box.
122-
//
123-
// \note Remark: The definition of the reference point follows the
124-
// specification of the \c BaseMoving message.
125-
//
126-
optional Vector3d position = 2;
127-
128-
// Orientation in the global coordinate system.
129-
//
130-
optional Orientation3d orientation = 3;
131-
}
132-
133103
//
134104
// \brief The action header
135105
//

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)