yolov3 VS yolov5

Hey. I only have experience using the official repository, and only use Linux. Could you try the solutions here and see if it helps? https://github.com/ultralytics/yolov3/issues/1643

YOLOv3: https://github.com/ultralytics/yolov3

Each image has an XML file associated with it. The XML files have the corresponding labels and bounding boxes, so I can write a script to convert them into this form, and follow this tutorial on training custom data.

Ref https://www.youtube.com/watch?v=0GwnxFNfZhM https://github.com/ultralytics/yolov5 https://dev.to/gfstealer666/kaaraich-yolo-alkrithuemainkaartrwcchcchabwatthu-object-detection-3lef https://www.kaggle.com/datasets/devdgohil/the-oxfordiiit-pet-dataset/data

!git clone https://github.com/ultralytics/yolov5.git ## Navigate to the model %cd yolov5/ ## Install requirements !pip install -r requirements.txt ## Download the YOLOv5 model !wget https://github.com/ultralytics/yolov5/releases/download/v6.0/yolov5s.pt

Specifically what I did was take the coco128.yaml, added 6 new classes from Dataset A (which have already been converted to YOLO Darknet TXT), from index 0-5 and subsequently adjusted the indices of the other COCO classes. The I proceeded to train and validate on Dataset A for 20 epochs.

I am using the default YOLOv5m6 model here with sahi/yolov5 library for my object detection project. I want to change just some of labels - for example when YOLO detects a human, I want it to label the human as "threat", not "person". Is there any way I can do it just changing some code, or I should train the model from scratch by just changing labels?

You should add them without annotations. Go through this.

You are correct and if you check the firmware, it's yet another famous 3rd party project without attribution, namely https://github.com/ultralytics/yolov5

On one side, being a Linux user for 24 years now, it annoys me that they rip off code and claiming it as theirs again, thus violating licenses, but on the other thanks to k3d's exploit I'm able to tinker more with the machine and if needed do (selective) updates by hand then with a closed source system. It's not just "klipper", with klipper, fluidd and moonraker, it's also ffmpeg and mjpegstreamer. It's gonna be interesting since they also use a project that isn't just GPL, but APGL (in short "If your software gives service online, you have to publish the source code of it and any library that it borrows functions from.") - they use yolov5 (for AI).