feat: Grouping the traffic lights#902
Conversation
The individual bulbs of a traffic light rarely function as standalone signals. Rather, they form a unit consisting of two or three bulbs that convey a specific instruction to the driver. The introduction of the group_id defines a unique assignment of the lights. It replaces heuristics—such as those based on position and orientation—that were previously necessary in the user software. Signed-off-by: Michael Plass <Michael.Plass@partner.bmw.de>
|
Thank you @plass-bertrandt for posting this! @pmai and @jdsika I would appreciate something like this in the next OSI standard (version 3.9). Grouping traffic lights has been a recurring problem whenever we have integrated traffic agents using OSI. Typically the grouping should be known by the simulation engine (at least lights are grouped in OpenDRIVE). It would be good if the simulation engine could forward this information e.g. to traffic agents. I like the proposed solution since it is quite simple, but am open to other possibilities on how to represent this information. |
Hi @pmai and @jdsika, |
Reference to a related issue in the repository
TrafficLight rework proposal. #754
Add a description
The individual bulbs of a traffic light rarely function as standalone signals. Rather, they form a unit consisting of two or three bulbs that convey a specific instruction to the driver.
The introduction of the group_id defines a unique assignment of the lights. It replaces heuristics—such as those based on position and orientation—that were previously necessary in the user software.
Some questions to ask:
Take this checklist as orientation for yourself, if this PR is ready for the Change Control Board:
If you can’t check all of them, please explain why.
If all boxes are checked or commented and you have achieved at least one positive review, you can assign the label ReadyForCCBReview!