Yolov5 DeepSort Pytorch Versions Save

BoxMOT: pluggable SOTA tracking modules for segmentation, object detection and pose estimation models

v10.0.55

2 months ago
  • Per class tracking now enabled for create_tracker
  • Tag and release naming fixed

v{10.0.54}

2 months ago

All trackers inherit BaseTracker

v10.0.52

2 months ago
  • Added scripts for ultra fast experimentation by pre-generating detections and embeddings such that they can later be fed to any tracking method.
  • Added possibility to pass embeddings to all trackers.
  • ~3x CI pipeline speedup by using parallelization and pregenerated detections and embeddings

v10.0.51

4 months ago

with_reid argument was added to BoTSORT by @Kevin111369. Usage:

tracker = BoTSORT(
    model_weights = None,
    device = 'cuda:0',
    fp16 = True,
    with_reid = True,  # true for motion + ReID association, false for only motion association
) 

v10.0.50

4 months ago

A centroid-based association method has been added to OCSORT and DeepOCSORT. This may be best suited for small AND/OR fast moving objects

from boxmot import OCSORT

tracker = OCSORT(
    asso_func="centroid",
    iou_threshold=0.3  # use this to set the centroid threshold that match your use-case best
)

v10.0.49

4 months ago

A centroid-based association method has been added. This may be best suited for small AND/OR fast moving objects

v10.0.48

4 months ago

HybridSort numpy datatypes fix by @florian-fischer-swarm

v10.0.47

5 months ago

The KF adapter contained some minor bugs. All orginal KF from their respective repositories are now used instead.

v10.0.46

6 months ago

BoTSORT improvements by @Justin900429 in https://github.com/mikel-brostrom/yolo_tracking/pull/1192:

  • Integration of a Fusing Option
  • Optimization of Optical Flow Computation

v10.0.45

6 months ago

Increase reid mutlibackend preprocessing robustness by clipping the detections to ((0, w), (0, h)) by @Justin900429 in https://github.com/mikel-brostrom/yolo_tracking/pull/1187. This error may arise if the detector generates bboxes that ends outside the input image. It happens when the detector has been trained, not following best practices (clean up your ground truth, clip the output of the model...).