馃悰 HOTA: fix numpy error when either ground truth or tracks are empty. - #107
Open
OlivierLDff wants to merge 1 commit into
Open
馃悰 HOTA: fix numpy error when either ground truth or tracks are empty.#107OlivierLDff wants to merge 1 commit into
OlivierLDff wants to merge 1 commit into
Conversation
fixes a bug where a numpy error occurred when one of the shape dimensions of the data was 0. This was causing the potential matches between IDs in each timestep to not be counted correctly. The fix introduced by if len(gt_ids_t) and len(tracker_ids_t): ensures that the potential matches are only counted if both gt_ids_t and tracker_ids_t are non-empty, which prevents the numpy error from occurring. This ensures that the potential matches are calculated correctly, resulting in more accurate tracking results.
OlivierLDff
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fixes a bug where a numpy error occurred when one of the shape dimensions of the data was 0. This was causing the potential matches between IDs in each timestep to not be counted correctly. The fix introduced by if len(gt_ids_t) and len(tracker_ids_t): ensures that the potential matches are only counted if both gt_ids_t and tracker_ids_t are non-empty, which prevents the numpy error from occurring. This ensures that the potential matches are calculated correctly, resulting in more accurate tracking results.