-
Notifications
You must be signed in to change notification settings - Fork 128
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
Add new message for sub-bounding boxes #732
Conversation
4206564
to
58ecd44
Compare
It was unlcear which pivot point the Position definition represents in relation to the dimension and rotation. Added a comment, that it is the center of the BoundingBox. For Type "TYPE_OTHER", there was no possibility to express the object more detailed. I introduced a string type to describe it. This other_object_type offers the possibility to reduce the Type enum and split it up an an additional PR to update it later on. This type should not be in conflict to other current approaches harmonizing object type definition. Through the other_object_type filed, the overall SubBoundingBox approach is already usable. @pmai Why did my DCO fail again? :.( |
CCB 2024-01-29: Type enum should be reviewed (e.g. by @PhRosenberger, @thomassedlmayer, @pmai) esp. w.r.t. sensor modeling needs and a minimum list should be proposed. If no such list emerges, then having no enums, but also dropping the string fallback (as e.g. model_reference can already be used as a last effort fallback) would be the preferred way forward. Will be re-reviewed at next CCB. |
24dfdbb
to
12ef6dc
Compare
CCB 2024-02-26: Small addition of examples for TYPE_DOOR in the context of vehicles to be added by @pmai, otherwise is ready for merge as-is. |
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.
Besides the comment on the doors, I approve this PR.
9230083
to
7d8e37b
Compare
Signed-off-by: Nicholas Dunning <Nicholas.Dunning@bmw.de>
Signed-off-by: Nicholas Dunning <Nicholas.Dunning@bmw.de>
Add information regarding the handling of side mirrors and the definition of the bounding box. Signed-off-by: Pierre R. Mai <pmai@pmsf.de>
Signed-off-by: Pierre R. Mai <pmai@pmsf.de>
- Clarified the position definition. - Added a "other_object_type" sting to define object types, which are not part of the Type definition enum. - Reduced the Type field, because of compatibility reason. There is a general approach to harmonize object type definitions. So the definition should not get in conflict to that approach. Signed-off-by: Thomas Hempen <thomas.hempen@carissma.eu>
Signed-off-by: Thomas Hempen <thomas.hempen@carissma.eu>
Signed-off-by: Thomas Hempen <thomas.hempen@carissma.eu>
Signed-off-by: Thomas Hempen <thomas.hempen@carissma.eu>
Signed-off-by: Thomas Hempen <thomas.hempen@carissma.eu>
Signed-off-by: Thomas Hempen <thomas.hempen@carissma.eu>
Signed-off-by: Thomas Sedlmayer <tsedlmayer@pmsfit.de>
Signed-off-by: Thomas Hempen <thomas.hempen@carissma.eu>
Removed invalid tabs. Signed-off-by: Thomas Hempen <thomas.hempen@carissma.eu>
Signed-off-by: Pierre R. Mai <pmai@pmsf.de>
7d8e37b
to
7e81917
Compare
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.
Reviewed with critical comment v3.7.0
@PhRosenberger
This PR is a continuation of #695 (and #685) with fixed history. It proposes the addition of bounding box sub-sections to BaseMoving and BaseStationary objects, to help sub-divide and classify different parts of the overall object structure.