Skip to content

add moving direction to moving object classification #508

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

Closed
wants to merge 3 commits into from

Conversation

0815-code
Copy link
Contributor

@0815-code 0815-code commented Apr 17, 2021

Signed-off-by: Schloemicher, Thomas AVL,AT thomas.schloemicher@avl.com

#### Reference to a related issue in the repository
Add a reference to a related issue in the repository.

Add a description

Adding moving direction to moving object classification to have a high level sematic information of the overall moving direction of a moving object whether it is oncoming, moving in the same direction or crossing.

Some questions to ask:
What is this change?
What does it fix?
Is this a bug fix or a feature? Does it break any existing functionality or force me to update to a new version?
How has it been tested?

Take this checklist as orientation for yourself, if this PR is ready for the Change Control Board:

  • My suggestion follows the style and contributors guidelines.
  • I have taken care about the documentation.
  • I have done the DCO signoff.
  • My changes generate no errors when passing CI tests.
  • I have successfully implemented and tested my fix/feature locally.
  • Appropriate reviewer(s) are assigned.

If you can’t check all of them, please explain why.
If all boxes are checked or commented and you have achieved at least one positive review, you can assign the label ReadyForCCBReview!

Signed-off-by: Schloemicher, Thomas AVL,AT <thomas.schloemicher@avl.com>
@0815-code 0815-code added FeatureRequest Proposals which enhance the interface or add additional features. TrafficParticipants The group in the ASAM development project working on traffic participants. SensorModeling The Group in the ASAM development project working on sensor modeling topics. labels Apr 17, 2021
@0815-code 0815-code self-assigned this Apr 17, 2021
@0815-code 0815-code linked an issue Apr 17, 2021 that may be closed by this pull request
Signed-off-by: Schloemicher, Thomas AVL,AT <thomas.schloemicher@avl.com>
@0815-code 0815-code force-pushed the feature/tp/add_moving_direction_info_#507 branch from 265b6e2 to 069c58a Compare April 18, 2021 15:31
osi_object.proto Outdated
{
// Moving direction is unkown.
//
MOVING_DIRECTION_UNKOWN = 1;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Start with 0 counting up, that is the reason for the fail i think.

Signed-off-by: Schloemicher, Thomas AVL,AT <thomas.schloemicher@avl.com>
repeated double assigned_lane_percentage = 2;
repeated double assigned_lane_percentage = 2;

// Classification of the general moving direction of a moving object depeding on the relative yaw orientation between host vehicle and moving object.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

depending

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggestion:
// Classification of the general moving direction of a moving object depeding on the relative yaw orientation to the host vehicle.
And: what if hostvehicle_id is not set?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ThomasSchloemicherAVL please comment


// Moving object is moving in the same direction.
//
MOVING_DIRECTION_IN_SAME_DIRECTION = 1;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So yaw angle delta -45° to +45°?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ThomasSchloemicherAVL please comment

@kmeids
Copy link

kmeids commented Jan 14, 2022

@ThomasSchloemicherAVL any update from your side on this topic?
And do you need to discuss this in the SensorModelilng group?

@clemenshabedank
Copy link
Contributor

OSI CCB 09.05.2022:

  • It might makes sense to just introduce this information in SensorData (Detected object).
  • Could be a good topic for v3.6.

@clemenshabedank clemenshabedank added this to the V4.0.0 milestone May 9, 2022
@thomassedlmayer
Copy link
Contributor

@0815-code Is this still a priority? Can we close this or do you want to work on it?

@thomassedlmayer thomassedlmayer moved this to Waiting for feedback in Sensor Modeling Apr 30, 2025
@thomassedlmayer
Copy link
Contributor

Closing this PR due to inactivity. Feel free to reopen or create a new one if you'd like to continue the discussion or address the feedback.

@github-project-automation github-project-automation bot moved this from Waiting for feedback to Done in Sensor Modeling May 14, 2025
@thomassedlmayer thomassedlmayer moved this from Done to Dismissed in Sensor Modeling May 14, 2025
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. SensorModeling The Group in the ASAM development project working on sensor modeling topics. TrafficParticipants The group in the ASAM development project working on traffic participants.
Projects
Status: Dismissed
Development

Successfully merging this pull request may close these issues.

Moving direction information in moving object classification
5 participants