Skip to content
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

Combine visual descriptor and geometry distance in the data association part #272

Closed
PhmHiu opened this issue Jul 27, 2023 · 2 comments
Closed
Labels
help wanted Extra attention is needed

Comments

@PhmHiu
Copy link

PhmHiu commented Jul 27, 2023

Hi, I want to ask about the data association part. If I understand correctly, the current implementation of matching detections with initialized tracked objects are consider the distance function and reid distance function separately. The distance matrix is constructed solely on one function. The distance function is used first to match initialized tracked objects with detections, and this function only considers the motion. I am using a reid function to utilize the visual characteristics of objects but this function only uses to match unmatched initialized tracked objects with not yet initialized tracked objects. I ask this question because I face a situation where 2 objects intersect and there is only 1 bounding box, this bounding box can be mistakenly matched with the object that is hidden behind if using only the motion feature. Is there an implementation that combines visual descriptors into the distance? Thank you.

@PhmHiu PhmHiu added the help wanted Extra attention is needed label Jul 27, 2023
@aguscas
Copy link
Collaborator

aguscas commented Aug 4, 2023

Hello! Sorry for the late response. We don't currently have any out-of-the-box distance function that uses visual descriptors. However, you can always define a custom distance function taking a Detection and a TrackedObject instance that makes use of the attributes embedding (for the detection), and last_detection.embedding (for the tracked object). Remember that your tracked object also might have a list of several past detections in its attribute past_detections, so you can have the embeddings of those past detections at your disposal when defining your distance_function.

@PhmHiu
Copy link
Author

PhmHiu commented Aug 7, 2023

Thank you very much for your reply!

@PhmHiu PhmHiu closed this as completed Aug 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants