Getting tracker internal state information

Is there a way to extract any of the following from the NvMultiObjectTracker library?

  • Kalman filter state (velocity, position, noise estimates)
  • Data association state (IoU, Re-ID, visual similarity)
  • Learned correlation filters and filter responses for NvDCF

I’ve found a similar question in Tracker logging which suggests adding some of this as a feature, has anything changed since?

To give some additional motivation for wanting this information – having access to any of this information would make debugging tracker issues significantly easier. Lacking this means that tracker parameter tuning is very difficult because one can’t get any insight into which tracker components are underperforming or causing issues.

There is no update from you for a period, assuming this is not an issue anymore. Hence we are closing this topic. If need further support, please open a new one. Thanks

Here is nvtracker output in currently implementation: Gst-nvtracker — DeepStream documentation 6.4 documentation

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