-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Patch trackeval for enabling multi class eval #2128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Patch trackeval for enabling multi class eval #2128
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull Request Overview
This PR patches the TrackEval library to enable multi-class object tracking evaluation by expanding support from pedestrian-only to 80 COCO classes. The changes modify the MOT challenge evaluation framework to accept arbitrary object classes and update default configurations accordingly.
- Creates a comprehensive patching script to modify TrackEval's MOT challenge dataset handler
- Updates evaluation initialization to automatically apply the patch before running evaluations
- Changes default class configurations from pedestrian-only to all 80 COCO classes
Reviewed Changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| boxmot/utils/trackeval_patch.py | New patching script that modifies TrackEval to support multi-class evaluation with COCO classes |
| boxmot/engine/val.py | Integrates patch application into evaluation initialization and removes redundant import |
| boxmot/engine/cli.py | Updates default classes from [0] to range(80) for COCO classes and fixes variable name typos |
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
No description provided.