You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe what is it that you need help with
The data we'd display to clients is a count of unique objects. I'm trying to workout how we'd manage deployment in terms of continuing to increase the counter. Do people tend to reset on an hourly / X-time basis or something like that? Or run it over segments of video Y minutes long?
Alternatively is it possible to simply always generate unique IDs (e.g. long hashes) instead of the count IDs. So that our database call could just be the number of those unique IDs?
The text was updated successfully, but these errors were encountered:
We don't have an easy way to reset the counter, but that's handled by a TrackedObjectFactory which you can access through tracker._obj_factory. In there you can find the count and the global_count which is only useful if you have multiple Tracker instances.
Regarding random IDs we don't have a way to support that, you could achieve it by forking this repo and modifying the ids returned here
Sorry that I can't help you more, resetting the counter sounds like a new feature we should include in a future version
Describe the situation you are working on
Object counting on a conveyor belt.
Describe what is it that you need help with
The data we'd display to clients is a count of unique objects. I'm trying to workout how we'd manage deployment in terms of continuing to increase the counter. Do people tend to reset on an hourly / X-time basis or something like that? Or run it over segments of video Y minutes long?
Alternatively is it possible to simply always generate unique IDs (e.g. long hashes) instead of the count IDs. So that our database call could just be the number of those unique IDs?
The text was updated successfully, but these errors were encountered: