Certain classes in my object detection model are being mislabeled

Accelerated Computing Intelligent Video Analytics TAO Toolkit
1

Please provide the following information when requesting support.

• Hardware (T4/V100/Xavier/Nano/etc) Geforce rtx 3090
• Network Type Yolo_v4 (Detectnet_v2/Faster_rcnn/Yolo_v4/LPRnet/Mask_rcnn/Classification/etc)
• TLT Version (Please run “tlt info --verbose” and share “docker_tag” here) command not recognized
• Training spec file(If have, please share here) yolo_v4_train_resnet18_kitti.txt
• How to reproduce the issue ? (This is for errors. Please share the command line and the detailed log here.) NA

My object detection model, trained in yolo_v4 is showing a high detection rate. However, there are 3-4 object (classes) that are consistently mislabeled with the same label. I don’t think it is an incorrect detection but rather a mislabeling based on the consistency of the objects affected.

It seems that the class being mislabeled is always 2 classes apart from the class it is labeled for in the class mapping list. I should also mention that there are 120 classes which could possibly play into the equation, and that at this point I am training with only about 550 images.

I have tried a number of possible solutions with no success and I’m running out of ideas. Can you suggest some options I might check for possible solutions or questions I should consider?

Wayne

2

You may try more experiments. Such as,

  1. Use deeper backbone, such as, resnet50, etc.
  2. Use more training dataset
  3. Use other networks, such as DINO(https://docs.nvidia.com/tao/tao-toolkit/text/cv_finetuning/pytorch/object_detection/dino.html)
3

Morgan, Thanks for your help as always. I have been pursuing Dino, but also seeking a direct solution to my issue in Yolo_v4, and I found it. We had in advertently capitalized the first letter of 3 of our class names. This threw out proper alphabetizing of the class list which tfrecords did not correct. However, when I bypassed tfrecords to use a sequenced approach it corrected this issue and our mislabeling issue as well.

4

OK. Thanks for the info. Yes, in tfrecords generations, all the class names are set to lowercase.

5

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.