-
Notifications
You must be signed in to change notification settings - Fork 423
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mmdet adapter #1545
Mmdet adapter #1545
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think the code itself looks good although I'm not very familiar with using COCOEval and MMdetection, so I might have missed something.
The only obvious issues are with the docstrings. I commented on things that I thought were against our "standard" (although I may be mistaken and we may not have a standard in some cases...). Also, there are a few instances where lists (e.g. for COCO dictionary keys) are not rendered properly on the docs website although I'm not sure the format to get these to render properly.
Couple of questions:
- Would it be possible to test the MAP torchmetrics? I can imagine this be very difficult, but if it ever gets messed with in the future, it would be nice to be able to tell if it broke. A simple test like checking identical outputs results in a mAP of 1 may even be helpful.
- Are there references for the model output for both training and testing? Also, a definition for the mmedetection batch (is the test definition sufficient?)? If you think it would be appropriate to add these details to the code, I think it would make it a lot easier to use. If not, let's at least record somewhere
Co-authored-by: Landan Seguin <landan@mosaicml.com>
Co-authored-by: Landan Seguin <landan@mosaicml.com>
Co-authored-by: Landan Seguin <landan@mosaicml.com>
Co-authored-by: Landan Seguin <landan@mosaicml.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
- Question on the
ImportError
for torchvision in the MAP metric - Copying the map dict docstrings in the
eval_forward()
function - Nits (feel free to ignore as you see fit)
Approving as a peace offering 😁
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: Landan Seguin <landan@mosaicml.com>
Co-authored-by: Landan Seguin <landan@mosaicml.com>
Co-authored-by: Landan Seguin <landan@mosaicml.com>
Co-authored-by: Landan Seguin <landan@mosaicml.com>
Co-authored-by: Landan Seguin <landan@mosaicml.com>
mmdet adapter, tested with yolox and faster-rcnn.
MAP metric, taken from torchmetrics 0.6.0 (last working version)
allowed dict literals in our pre-hook config to accommodate mmdet configs.
maskrcnn/instance segmentation works for some models but needs more testing. Decided not to mention it in these docs as I'm not sure if all/most models work.