Skip to content

Conversation

@pmai
Copy link
Contributor

@pmai pmai commented Mar 27, 2018

This is relevant for e.g. sensor fusion models that merge multiple
SensorData inputs into one SensorData output.

This is relevant for e.g. sensor fusion models that merge multiple
SensorData inputs into one SensorData output.
@pmai pmai added the FeatureRequest Proposals which enhance the interface or add additional features. label Mar 27, 2018
@pmai pmai added this to the v3.0.0 milestone Mar 27, 2018
@pmai pmai self-assigned this Mar 27, 2018
@pmai pmai requested a review from a user March 27, 2018 13:26
@ghost
Copy link

ghost commented Mar 27, 2018

I am actually a bit confused by the "RadarSensorViewConfiguration" copy. I thought we only need a few values from that in every time step?

@pmai
Copy link
Contributor Author

pmai commented Mar 27, 2018

The overhead of the config view is very slight compared to the radar data itself, and without the config information the raw data does not necessarily make sense: Consider the CameraSensorView data, which is just raw binary data, with the format completely described in the config. This also aids in getting the right data for multiple views, since they contain the configs...

@ghost ghost merged commit c4862a9 into master Mar 27, 2018
@ghost ghost deleted the feature/repeatable-sensorview branch March 27, 2018 14:30
This pull request was closed.
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.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants