How can I compile yolov5m and my own yolov5 onnx to hef without quantization, optimization and nms

General
,
14

Forgot to update here - it was somewhat easy in the end but took a little guess work as to which file to update, especially given the confusing info message when parsing:

[info] Extracted ONNXRuntime meta-data for Hailo model (completion time: 00:00:00.34)
[info] NMS structure of yolov5 (or equivalent architecture) was detected. Default values of NMS anchors were loaded to NMS config json

that lead me down the road of updating the base/yolo.yaml file - however that wasn’t required at all.

The only file needing updated was the nms_config. I was looking for some key:value called anchor, but in the nms config these key:value pairs are in the "bbox_decoders" under "w" and "h"

The updated yolov5_nms_config.json now looks like this (bear in mind that I have a custom class number for my 2classes+background=3)

Updated file 
{
  "nms_scores_th": 0.001,
  "nms_iou_th": 0.6,
  "image_dims": [640, 640],
  "max_proposals_per_class": 80,
  "background_removal": false,
  "classes": 3,
  "bbox_decoders": [
      {
          "name": "bbox_decoder55",
          "w": [
              2.27344,
              2.77148,
              4.26172
          ],
          "h": [
              4.06250,
              6.73828,
              7.46484
          ],
          "stride": 8,
          "encoded_layer": "conv55"
      },
      {
          "name": "bbox_decoder63",
          "w": [
              4.53906,
              7.21875,
              6.37109
          ],
          "h": [
              11.07031,
              9.75000,
              15.98438
          ],
          "stride": 16,
          "encoded_layer": "conv63"
      },
      {
          "name": "bbox_decoder70",
          "w": [
              9.89844,
              11.42969,
              19.93750
          ],
          "h": [
              14.13281,
              23.01562,
              29.39062
          ],
          "stride": 32,
          "encoded_layer": "conv70"
      }
  ]
}

Unfortunately, the yolov5 also seems to have the same issue with nms and the overlapping boxes - but I’ll update regards to that in the other thread to keep this one on topic