as stated in the repo, its "mAP result values" https://medium.com/@jonathan_hui/...

AndrewThrowaway · on Aug 19, 2020

Don't get me wrong. I totally get it. But my professor is saying:

"So this is precision? 0 to 1? 1 being totally accurate? And you got 96.5? I assume it is percentage?"

nl · on Aug 20, 2020

It says "mAP result values on the WIDERFACE validation dataset:"

If your professor is working in on object detection they know what mAP is - all the major datasets use it as their standard evaluation criteria.

AndrewThrowaway · on Aug 20, 2020

So is it mAP of 0.956 or 95.6? Why not 956?

nl · on Aug 20, 2020

Not to be rude, but if you can't work that out you shouldn't be working on this. I'm sure the author would take a pull request, but but it really sounds like you are nitpicking.

Figures like precision and recall are often expressed either as 66% or 0.66. Confusion really isn't that big a problem.

AndrewThrowaway · on Aug 20, 2020

Not rude at all because I am totally nitpicking.

If you would write mAP: 0.9 or mAP (%): 90 or similar my "professor" would be OK with that.

I guess general rule in science (or maybe engineering) is to define units. I have no doubt that e.g. when you are building rockets (or maybe model airplanes) you would know that e.g. velocity is in m/s. Until somebody thinks in some other way and things blow up.

I just wanted to make some fun comment about missing units and that is it. I have no doubt that anybody browsing that repo would not be confused about mAP being 95.6.