duan8/yolov5
2020-11-06 22:22:23 +08:00
..
CMakeLists.txt update yolov5 to v3.0 2020-11-06 22:22:23 +08:00
common.hpp update yolov5 to v3.0 2020-11-06 22:22:23 +08:00
gen_wts.py update yolov5 genwts 2020-11-06 21:35:02 +08:00
hardswish.cu update yolov5 to v3.0 2020-11-06 22:22:23 +08:00
hardswish.h update yolov5 to v3.0 2020-11-06 22:22:23 +08:00
logging.h implement yolov5s 2020-06-22 13:48:17 +08:00
README.md update yolov5 to v3.0 2020-11-06 22:22:23 +08:00
utils.h implement yolov5s 2020-06-22 13:48:17 +08:00
yololayer.cu yolov5s batchsize 2020-06-22 19:02:30 +08:00
yololayer.h yolov5s batchsize 2020-06-22 19:02:30 +08:00
yolov5.cpp update yolov5 to v3.0 2020-11-06 22:22:23 +08:00

yolov5

The Pytorch implementation is ultralytics/yolov5.

Currently, we support yolov5 v1.0(yolov5s only), v2.0 and v3.0.

Config

  • Choose the model s/m/l/x by NET macro in yolov5.cpp
  • Input shape defined in yololayer.h
  • Number of classes defined in yololayer.h
  • FP16/FP32 can be selected by the macro in yolov5.cpp
  • GPU id can be selected by the macro in yolov5.cpp
  • NMS thresh in yolov5.cpp
  • BBox confidence thresh in yolov5.cpp
  • Batch size in yolov5.cpp

How to Run, yolov5s as example

1. generate yolov5s.wts from pytorch implementation with yolov5s.pt

git clone https://github.com/wang-xinyu/tensorrtx.git
git clone https://github.com/ultralytics/yolov5.git
// download its weights 'yolov5s.pt'
cd yolov5
cp ../tensorrtx/yolov5/gen_wts.py .
// ensure the file name is yolov5s.pt and yolov5s.wts in gen_wts.py
python gen_wts.py
// a file 'yolov5s.wts' will be generated.

2. put yolov5s.wts into yolov5, build and run

mv yolov5s.wts ../tensorrtx/yolov5/
cd ../tensorrtx/yolov5
// ensure the macro NET in yolov5.cpp is s
mkdir build
cd build
cmake ..
make
sudo ./yolov5 -s             // serialize model to plan file i.e. 'yolov5s.engine'
sudo ./yolov5 -d  ../samples // deserialize plan file and run inference, the images in samples will be processed.

3. check the images generated, as follows. _zidane.jpg and _bus.jpg

More Information

See the readme in home page.