Samuel Mohebban

when you say old how many releases prior? Roughly Your code works, so does it default to another forward if there is not a model name present in the file...

Thanks for the reply and all your help. We have just restarted our simulation using the new netscale factor. I will keep you updated on our results when comparing this...

@marcoslucianops after heavy digging I found that it may not have to do with your new code but rather the deepstream version (specifically TensorRT). See my conversation here https://forums.developer.nvidia.com/t/detections-change-in-deepstream-6-2/257280/7 From...

here are more results I found today  ``` [property] gpu-id=0 net-scale-factor=0.0039215697906911373 model-color-format=0 onnx-file=/model.onnx model-engine-file=/model.engine labelfile-path=/labels.txt batch-size=1 network-mode=2 num-detected-classes=2 interval=0 gie-unique-id=1 process-mode=1 network-type=0 cluster-mode=2 infer-dims=3;544;960 maintain-aspect-ratio=1 symmetric-padding=1 force-implicit-batch-dim=1 workspace-size=9000 parse-bbox-func-name=NvDsInferParseYolo...

The dataset we are using is not COCO as its internal to our company. We have an internal tool that calculates TP/TN/FP/FN. In the graph above, TN and FN are...

[resultsGitHub.xlsx](https://github.com/marcoslucianops/DeepStream-Yolo/files/11899151/resultsGitHub.xlsx) Here are results. I noticed there was an issue with how I ran int8 in the previous export so please use this file when analyzing int8. Each sheet corresponds...

@marcoslucianops bringing this back up as we are seeing this issue again. We were able to get about the same performance by lowering thresholds using .onnx, when the same model...

@landskris were you able to find anything related to this issue? Im seeing a ton of matching issues as well