-
Notifications
You must be signed in to change notification settings - Fork 129
Add new LogicalDetectionData message to SensorData #440
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
Conversation
Since no one chimed in until now, marking it as ready for CCB review. However more involvement from sensor modeling group would probably be good (I've posted this PR by order of the SET Level project, where it comes from the sensor modeling side of things). |
Output from CCB meeting - 09.12.2020
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nothing major, just some minor linguistic/comments update
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Missing one comment update for sensor_id
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved during the CCB meeting 03.02.2021
Results from CCB meeting 03.02.2021
|
c3f135c
to
657aa49
Compare
LogicalDetectionData provides feature data in the virtual cartesian sensor coordinate system and is therefore suitable for fusion at the feature data level, whereas FeatureData is not. Signed-off-by: Pierre R. Mai <[email protected]> Signed-off-by: Rosenberger, Philipp <[email protected]>
657aa49
to
ed8433b
Compare
Signed-off-by: Rosenberger, Philipp <[email protected]> Signed-off-by: Pierre R. Mai <[email protected]>
ed8433b
to
c3c1df6
Compare
LogicalDetectionData provides feature data in the virtual cartesian
sensor coordinate system and is therefore suitable for fusion at the
feature data level, whereas FeatureData is not.
Signed-off-by: Pierre R. Mai [email protected]
This PR coming from the SETLevel4To5 project is partly related to #367, and tackles the issue that the current
FeatureData
interface is strictly limited to one physical detector/sensor, since the coordinate system is spherical. This makes it more or less impossible to transport fusioned data, which must necessarily reside in one common coordinate system. The naming also tries to align with DIS 23150 (further alignment might also recommend renaming ofFeatureData
, which is however not included in this PR so as to remain backward compatible for now).