Feat/core/CBioU tracker

[AlexBodner]

What does this PR do?

Adding CBIoU tracker as wrapper of IoU variants BIoU and BoTsort without cmc (which would be original bytetrack).

Still missing the metrics

Type of Change

• New feature (non-breaking change that adds functionality)

Testing

• I have tested this change locally
• I have added/updated tests for this change

Test details:

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code where necessary, particularly in hard-to-understand areas
• My changes generate no new warnings or errors
• I have updated the documentation accordingly (if applicable)

Additional Context

[Copilot]

Pull request overview

Adds a new CBIoU tracker as a BoT-SORT-derived tracker that disables CMC and uses Buffered IoU for association, then exposes it through the package API and shared tracker test coverage.

Changes:

• Adds CBIoUTracker implementation and package entry point.
• Exports CBIoU from trackers.
• Extends tracker registration/shared behavior tests and adds CBIoU-specific tests.

Reviewed changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 6 comments.

Show a summary per file

File	Description
src/trackers/core/cbiou/tracker.py	Implements the CBIoU tracker wrapper around BoT-SORT with BIoU and CMC disabled.
src/trackers/core/cbiou/__init__.py	Adds the new CBIoU package.
src/trackers/__init__.py	Exposes CBIoUTracker from the top-level package.
tests/core/shared_ids.py	Adds cbiou to shared tracker IDs and separates IoU-configurable trackers.
tests/core/test_trackers.py	Excludes CBIoU from the configurable-IoU test.
tests/core/test_registration.py	Includes CBIoU in registration/search-space coverage.
tests/core/test_cbiou_tracker.py	Adds CBIoU-specific construction, warning, association, and search-space tests.

[Borda]

Let's mark as resolved the comment which you already addressed, so we know what is left

[Copilot]

Pull request overview

Copilot reviewed 12 out of 12 changed files in this pull request and generated 5 comments.

Comments suppressed due to low confidence (2)

docs/trackers/comparison.md:187

• The comparison page lists enable_cmc: false under the C-BIoU configuration, but CBIoUTracker.init does not accept an enable_cmc parameter (CMC is always disabled internally). Remove this key from the example config (or reword it as a note) to avoid suggesting an invalid constructor argument.

      high_conf_det_threshold: 0.6
      track_activation_threshold: 0.7
      buffer_ratio_first: 0.3
      buffer_ratio_second: 0.5
      enable_cmc: false

docs/trackers/comparison.md:367

• The comparison page lists enable_cmc: false under the C-BIoU configuration, but CBIoUTracker.init does not accept an enable_cmc parameter (CMC is always disabled internally). Remove this key from the example config (or reword it as a note) to avoid suggesting an invalid constructor argument.

      high_conf_det_threshold: 0.36
      track_activation_threshold: 0.83
      buffer_ratio_first: 0.23
      buffer_ratio_second: 0.33
      enable_cmc: false

[tstanczyk95]

If you say "paper b1" here, you might provide the link to the reference section below: ## Reference
Same for "paper b2" below.

[AlexBodner]

do we have to provide the reference every time we mention it?

[tstanczyk95]

Should we consider some warning for the user if ultimately self.buffer_ratio_first becomes higher or equal to self.buffer_ratio_second?

[AlexBodner]

dont think so, it is just recommended by paper authors, but like you pointed over Slack, if it works better or the user sees fit using a higher threshold first should be fine

[tstanczyk95]

Nice test to demonstrate, but it actually safe? And not too number/case-specific?

[AlexBodner]

it is very specific, but it tests what we want right? what seems off to you?