You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the customizing datasets tutorial in the "Check the annotations of the customized dataset" part its written that:
The classes fields in your config file should have exactly the same elements and the same order with the A[8] in txt annotations. MMRotate automatically maps the uncontinuous id in categories to the continuous label indices, so the string order of name in categories field affects the order of label indices. Meanwhile, the string order of classes in config affects the label text during visualization of predicted bounding boxes.
What is the meaning of "The classes fields in your config file should have exactly the same elements and the same order with the A[8] in txt annotations"? that if my classes are classes=('a','b','c') then in every annotation file (e.g., annot_1.txt) the order of the annotations class a should be before b and b should be before c? if so then in the DOTA_1 dataset original annotations txt files there are lots of files that doesn't obey this rule (e.g., some annotations files contains ship before harbor while other annotations files contains harbor before ship)
In which file/s exactly can I find id, categories and name?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
In the customizing datasets tutorial in the "Check the annotations of the customized dataset" part its written that:
The
classesfields in your config file should have exactly the same elements and the same order with theA[8]in txt annotations. MMRotate automatically maps the uncontinuousidincategoriesto the continuous label indices, so the string order ofnameincategoriesfield affects the order of label indices. Meanwhile, the string order ofclassesin config affects the label text during visualization of predicted bounding boxes.classesfields in your config file should have exactly the same elements and the same order with theA[8]in txt annotations"? that if my classes areclasses=('a','b','c')then in every annotation file (e.g.,annot_1.txt) the order of the annotations classashould be beforebandbshould be beforec? if so then in the DOTA_1 dataset original annotations txt files there are lots of files that doesn't obey this rule (e.g., some annotations files containsshipbeforeharborwhile other annotations files containsharborbeforeship)id,categoriesandname?Beta Was this translation helpful? Give feedback.
All reactions