DS6.0 NvTracker DeepSORT Re-Id in NvDsBatchMeta

• Hardware Platform (Jetson / GPU)
GPU
• DeepStream Version
6.0
• JetPack Version (valid for Jetson only)
• TensorRT Version
8.0.1
• NVIDIA GPU Driver Version (valid for GPU only)
471.41
• Issue Type( questions, new requirements, bugs)
Question
• How to reproduce the issue ? (This is for bugs. Including which sample app is using, the configuration files content, the command line used and other details for reproducing)
• Requirement details( This is for new requirement. Including the module name-for which plugin or for which sample application, the function description)
Gst-nvtracker

With the new DS 6.0 release we’re able to use DeepSORT with custom a custom Re-Id implementation. While the tracker uses the Re-Id vectors internally to estimate similarities between detections, we require the Re-Id vectors futher down our pipeline. Is it possible to extract the Re-Id vectors as a part of the NvDsBatchMeta for further processing (or in any other way)?

Thanks,

/M

Please provide complete information as applicable to your setup.

• Hardware Platform (Jetson / GPU)
• DeepStream Version
• JetPack Version (valid for Jetson only)
• TensorRT Version
• NVIDIA GPU Driver Version (valid for GPU only)
• Issue Type( questions, new requirements, bugs)
• How to reproduce the issue ? (This is for bugs. Including which sample app is using, the configuration files content, the command line used and other details for reproducing)
• Requirement details( This is for new requirement. Including the module name-for which plugin or for which sample application, the function description)

1 Like

Do you mean “the Re-ID feature vectors”? Can you share more details why downstream plugin need it in your use case? Thanks.

Im not sure why they need it, but i’d imagine its to perform queryable REID with something like faiss, using the embedding output from the REID model.

It does sound like an interesting proposition. I too now wonder if this is possible.

Indeed - we require the Re-Id vectors for two purposes:

  • To try and fix any potential broken tracks
  • To do data association across multiple cameras

Thanks,

Thanks for sharing. I will check and feedback later.

Appreciated,

Perhaps a simple “Export Re-Id” property on the gst-nvtracker element could be set to allow for this behaviour?

Looking forward to your feedback,

/M

We will add the feature in the future release. Thanks for sharing your use case.

1 Like

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.