-
Notifications
You must be signed in to change notification settings - Fork 29
Choosing labels based on their names for classification models #705
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
Open
jcchr
wants to merge
5
commits into
releases/v2.13.x
Choose a base branch
from
jchrapko/sorting_labels
base: releases/v2.13.x
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
45977ea
sorting labels alphabetically to preserve compatibility with modelapi
jcchr e35ea3c
unit tests correction
jcchr 7edbab2
handle two scenarios of sorting labels for classification models
jcchr fb048cc
readability of a code
jcchr 99c4896
styles correction
jcchr File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -309,9 +309,9 @@ def test_keypoint_to_prediction_converter(self, fxt_label_list_factory): | |
| [ | ||
| ( | ||
| ["1", "2"], | ||
| ["foo bar", "foo_bar"], | ||
| ["foo_bar", "foo_bar"], | ||
| {"label_ids": ["1", "2"], "labels": ["foo_bar", "foo_bar"]}, | ||
| ["foo bar1", "foo_bar2"], | ||
| ["foo_bar1", "foo_bar2"], | ||
| {"label_ids": ["1", "2"], "labels": ["foo_bar1", "foo_bar2"]}, | ||
|
Comment on lines
-312
to
+314
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. The purpose of this test case was to check an edge case where the label names are very similar and conflict after escaping (both |
||
| ), | ||
| ( | ||
| ["1", "2"], | ||
|
|
||
Oops, something went wrong.
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.
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.
What's wrong with
get_label_by_idx?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.
I remember that MAPI does not handle hierarchical classification in a consistent way, so we could not rely on the label indices. See related issue: open-edge-platform/geti#402.
Therefore, it is correct to use the label name for classification tasks. However, this means that we might get ambigous results if label are poorly named. For example,
foo barandfoo_bar, spaces are not supported by either MAPI or OV AFAIK, resulting in a name collision.