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
So these configurations in logic/tracker.yaml may not make any difference.
tracker_type: bytetrack # tracker type, ['botsort', 'bytetrack'] change this to select trackertrack_high_thresh: 0.25# threshold for the first associationtrack_low_thresh: 0.1# threshold for the second associationnew_track_thresh: 0.25# threshold for init new track if the detection does not match any trackstrack_buffer: 30# buffer to calculate the time when to remove tracksmatch_thresh: 0.8# threshold for matching tracksfuse_score: True # Whether to fuse confidence scores with the iou distances before matching# min_box_area: 10 # threshold for min box areas(for tracker evaluation, not used for now)# BoT-SORT settingsgmc_method: sparseOptFlow # method of global motion compensation# ReID model related thresh (not supported yet)proximity_thresh: 0.5appearance_thresh: 0.25with_reid: False
The text was updated successfully, but these errors were encountered:
lizi-Margin
changed the title
Small Issue: 'model.predict' may not parse tracker's configuration
Not a Issue: 'model.predict' may not parse tracker's configuration
Feb 8, 2025
According to the source code of Ultralytics, the method 'model.predict' may not parse tracker's configuration, though this won't cause any problem.
So these configurations in logic/tracker.yaml may not make any difference.
The text was updated successfully, but these errors were encountered: