yolo3 INT8 conversion drops mAP incredibly #263
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
i changed conf_treshhold from 0.3 to 0.001 and tried calibration with 4951 images and still mAP is very bad compared to int8 of yolo4 , the mAP just increased for all models because of conf_tresh except that nothing changed and still bad for yolo3 int8. any suggestion or explanation for what causing that would be greatful. thanks
note : all other conversions for fp32 16 int8 for yolo3 and yolo4 are good and very close to published results
Hi @MohamedElsaeidy,
It is normal a drop of performance when going from float (even half precision) to int8. I do agree that the jump is very big. Here I can attach a chart with several comparison we did for a journal paper (still under review), in which you can find a lor of information about different platforms and network for all the data types.
Hope it helps.