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
Currently we don't have an easy way to enable/disable optical flow in our pipeline.
Easily enable/disable with launchscript parameter
Detections should have a flag to indicate to downstream processing if this is directly from YOLO or from tracking. Time since last YOLO hit could also be a useful metric.
As part of this would be nice if Optical flow is something we can turn on/off without interrupting anything. All downstream pieces can be configured to ignore detections from tracking, and can operate with just normal YOLO hits so we can just bypass it.
The text was updated successfully, but these errors were encountered:
Currently we don't have an easy way to enable/disable optical flow in our pipeline.
As part of this would be nice if Optical flow is something we can turn on/off without interrupting anything. All downstream pieces can be configured to ignore detections from tracking, and can operate with just normal YOLO hits so we can just bypass it.
The text was updated successfully, but these errors were encountered: