Mxnet | 96.5 | 95.6 | 90.4
Ours | 95.6 | 94.6 | 88.5
My professors would be so mad if I submitted data like this. I already can hear "What are the units? Seconds? So yours are by one second better? Error margin? Percent? So yours is worse?"
I get that this is a very specific information for a specific audience. People who stumble on this repo should know what is that.
However we can all be better at presenting our data.
Professors will rail against imprecision to undergrads and young graduate students but they use it all the time in real life.
I can already hear my professors saying "stop commenting on style, what do you have to say about substance?"
https://medium.com/@jonathan_hui/map-mean-average-precision-...
"So this is precision? 0 to 1? 1 being totally accurate? And you got 96.5? I assume it is percentage?"
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.
Figures like precision and recall are often expressed either as 66% or 0.66. Confusion really isn't that big a problem.
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.