@@ -53,10 +53,11 @@ message Route
53
53
//
54
54
// \brief A segment of a logical lane.
55
55
//
56
- // \note The #LogicalLaneSegment allows that #start_s > #end_s.
57
- // If #start_s < #end_s, then the traffic agent should traverse the
56
+ // \note The \link LogicalLaneSegment logical lane segments\endlink allows that
57
+ // start_s > end_s.
58
+ // If start_s < end_s, then the traffic agent should traverse the
58
59
// segment in the logical lane's reference line definition direction.
59
- // If # end_s > # start_s, then the traffic agent should traverse the
60
+ // If end_s > start_s, then the traffic agent should traverse the
60
61
// segment in the opposite of the logical lane's reference line
61
62
// definition direction.
62
63
//
@@ -87,14 +88,14 @@ message Route
87
88
//
88
89
// Each time there is a successor-predecessor relation between the logical
89
90
// lanes along the route (i.e. a logical lane ends, and is continued by another
90
- // logical lane, e.g. at a junction border), a new #RouteSegment starts. The
91
- // #RouteSegment then lists the logical lane segments that can be used to
91
+ // logical lane, e.g. at a junction border), a new route segment starts. The
92
+ // route segment then lists the logical lane segments that can be used to
92
93
// travel through this space of the road.
93
94
//
94
95
// Together, the listed logical lane segments should form a continuous area,
95
96
// where the traffic agent can move freely. These will mostly be parallel
96
97
// lanes, though lanes may overlap (e.g. if one lane splits into two on a
97
- // junction). In general, the logical lane segments in a #RouteSegment will
98
+ // junction). In general, the logical lane segments in a route segment will
98
99
// have the same length, though there are exceptions (e.g. if a lane widening
99
100
// occurs, the newly appearing lane will have a shorter length).
100
101
//
0 commit comments