-
Notifications
You must be signed in to change notification settings - Fork 644
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
Tracking_eval refactor #660
Tracking_eval refactor #660
Conversation
68de50f
to
68e06c5
Compare
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.
lgtm!
assert set(class_range.keys()) == set(TRACKING_NAMES), "Class count mismatch." | ||
|
||
assert set(class_range.keys()) == set(tracking_names), "Class count mismatch." | ||
global TRACKING_NAMES |
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.
why you need to define it as global
rather than just use self.tracking_names
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.
assert tracking_name in TRACKING_NAMES, 'Error: Unknown tracking_name %s' % tracking_name |
It is needed here, and I donot want to change
TrackingBox
to include extra things.
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.
okay, then it's better to define this global variable at the beginning of this file, since it's shared by the 2 classes.
…into APF-2610/move_tracking_names_to_config_file
This PR moves the fields TRACKING_NAMES, PRETTY_TRACKING_NAMES and TRACKING_COLORS from constants.py to the config json file. This way users can use the tracking eval code on custom datasets with different classes.