Thanks so much about releasing best SDK for jetson platforms.
Undoubtedly, many company is used this platform and SDK for customers, but we see two main problem in the DS.
First of all, the tracker isn’t open source, and all of companies can’t customize the DS’s trackers. One big problem of tracker is that:
When we have pgie followed by sgie and then tracker, and the tracker pull all of pgie and sgie objects and then tracks all of them, but in some scenarios we want to operate on some IDs or some objects, due to we want to tracker has same properties in the its config file:
In the real world scenarios and multi-streams cases, we have to set custom properties depend on environment and view of cameras. That’s mean, only one value for filtering out the obejcts doesn’t good work for all streams.
In the best way, the stream0, stream1 and stream2 work with pre-cluster-threshold=th0, roi-top-offset=value0… and pre-cluster-threshold=th1, roi-top-offset=value1… and pre-cluster-threshold=th2, roi-top-offset=value2… respectively.
Like this feature exist in the config file for pre-class, but It’s better to have per stream properties in the config file.