-
Notifications
You must be signed in to change notification settings - Fork 16
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
I think this ObjectDetection2DSet Comment May be Incorrect #324
Comments
This comment is "correct", but a previous incarnation of the object detector was populating the message incorrectly. The newest Yolo detector that we have added should now be populating this field correctly. |
@derkmed Checking in if this explanation was sufficient to close this issue or if there is still something to be resolved. |
Got it. I will double check @Purg . So, each row should correspond to a detected object indicated via one-hot vector. Is that correct? |
Yes, but the vector is not specifically constrained to be one-hot: it is a per-class confidence vector. Some detector implementations may choose to populate this vector in a one-hot fashion. |
angel_system/ros/angel_msgs/msg/ObjectDetection2dSet.msg
Line 45 in 49c9391
When subscribing to topics that publish this message, I did not read a flattened matrix. Instead I read a vector of confidence scores corresponding to the label_vec.
The text was updated successfully, but these errors were encountered: