yolov5 VS tensorflow

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).

To get up to speed with TensorFlow, check their quickstart Support TensorFlow on GitHub ⭐

Explore here.

Part of the major userbase pull in GitHub revolves around hosting a considerable number of popular projects including Angular, React, Kubernetes, cpython, Ruby, tensorflow, and well even the software that powers this site Forem.

Right but that's not an inherent GPU determinism issue. It's a software issue.

https://github.com/tensorflow/tensorflow/issues/3103#issueco... is correct that it's not necessary, it's a choice.

Your line of reasoning appears to be "GPUs are inherently non-deterministic don't be quick to judge someone's code" which as far as I can tell is dead wrong.

Admittedly there are some cases and instructions that may result in non-determinism but they are inherently necessary. The author should thinking carefully before introducing non-determinism. There are many scenarios where it is irrelevant, but ultimately the issue we are discussing here isn't the GPU's fault.

and things like y = layers.ELU()(y) work as expected. I wanted to see a list of the available layers so I went to the Tensorflow GitHub repository and to the keras directory. There's a warning in that directory that says:

Exactly what language do you think TensorFlow is written in? :)

You can use Tensorflow's deep learning API for this.

Since you've specifically mentioned ML, here's Tenserflow's GitHub. I'm sure a quick glance through that will change your mind.