We are working with DRIVE 9. The detections are pretty good but we are struggling with the tracker. Please take a look at https://imgur.com/6NdGLf6 to view the problem.
The tracker (or perhaps clusterer?) seems to be merging the boxes of the two depicted pedestrians. To produce this image, I reset all parameter settings to those found in the sample_object_detector_tracker sample from DRIVE 9. Note, however, that we’re not using the DNN from that example to do the detections; we’re using DriveNet. Also note that we’re not doing our own clustering but using the 2D box tracker’s internal clustering.
My next avenue of experimentation is to try to employ the clustering module separately, then add the result to the 2D box tracker using dwBoxTracker2D_addPreClustered(). But before doing so, it would really help to get some clarification on a few items:
- Can you provide any insight into the underlying cause of the two boxes depicted above being merged?
- The clusterer API takes a collection of input weights, one per input box. I can't find any description of their purpose in the documentation. What do these input weights do and what are reasonable defaults?
- The tracking API method dwBoxTracker2D_addPreClustered() takes a collection of dwTrackedBox2D instances while dwBoxTracker2D_add() simply takes a collection of dwBox2D instances. In the former case, what does the tracker do with the additional information (e.g. id and confidence) from dwTrackedBox2D?
Any help you could provide would be greatly appreciated…