Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify Traffic Participant Inputs and Outputs #103

Merged
merged 1 commit into from
Feb 26, 2024
Merged

Clarify Traffic Participant Inputs and Outputs #103

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions doc/spec/model_types.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,8 +23,8 @@ This model type is used to model whole traffic participants, such as vehicles or
Traffic participant models may internally use environmental effect models, sensor models, or logical models as part of a modeled autonomous vehicle.
They may also be used to implement surrounding traffic in simplified ways.
Traffic participant models consume `osi3::SensorView` as input and produce `osi3::TrafficUpdate` as output.
They may also consume `osi3::TrafficCommand` as input to allow control by a scenario engine or other coordinating function.
They may also produce `osi3::TrafficCommandUpdate` as output to allow status responses to such control messages.
They may additionally consume `osi3::TrafficCommand` as input to allow control by a scenario engine or other coordinating function.
They may additionally produce `osi3::TrafficCommandUpdate` as output to allow status responses to such control messages.

Streaming update consumer models::
This model type receives a streaming update input for further processing.
Expand Down