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.

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

Sensor view should optionally include calculated obstruction values #543

Open
caspar-ai opened this issue Jun 29, 2021 · 0 comments · May be fixed by #548
Open

Sensor view should optionally include calculated obstruction values #543

caspar-ai opened this issue Jun 29, 2021 · 0 comments · May be fixed by #548
Assignees
Labels
FeatureRequest Proposals which enhance the interface or add additional features. TrafficParticipants The group in the ASAM development project working on traffic participants.

Comments

@caspar-ai
Copy link
Contributor

caspar-ai commented Jun 29, 2021

Describe the feature

A simulation system can often, by the nature of the information it already has available, calculate much more cheaply certain derived sensor data. Being able to pass this information downstream to other components to allow them to avoid expensive calculations is beneficial to the overall performance of a system.

In particular, how "visible" a ground truth object is fits this pattern. It would therefore be useful if OSI provided a way for those derived values to be passed around.

Describe the solution you would like

"Obstruction data" added as an optional field for each specific sensor view message (RadarSensorView, LidarSensorView, etc.).

Obstruction data includes at least occlusion and truncation data.

Describe alternatives you have considered

  • It could be directly included in GroundTruth messages but the values need to be calculated per-sensor
  • It could be included in SensorData but this is about raw sensor data rather than detections generated from the sensor

Describe the backwards compatibility

No issues with backwards compatibility, the new fields are optional.

@caspar-ai caspar-ai added FeatureRequest Proposals which enhance the interface or add additional features. TrafficParticipants The group in the ASAM development project working on traffic participants. labels Jun 29, 2021
@caspar-ai caspar-ai self-assigned this Jun 29, 2021
@caspar-ai caspar-ai linked a pull request Jul 2, 2021 that will close this issue
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
FeatureRequest Proposals which enhance the interface or add additional features. TrafficParticipants The group in the ASAM development project working on traffic participants.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant