Closed aleksandrkim61 closed 4 years ago
Have you seen the model occupy more and more memory when running the cascade_mask_rcnn_x101_32x4d_fpn_1x_nuim.py model?
If you are asking me:
I did not monitor resources when running it, so cannot tell you for sure.
Nevertheless, I do not think there is any reason for the model to retain anything in memory between runs. Perhaps, you should check if you have memory leaks elsewhere in your code? Storing intermediate results in global variables or maintaining metrics for logging could be a culprit.
Thank you for working on detection models for NuImages!
I've tried using a couple of them on pictures from NuImages following the synchronous code here without any changes. The output images have good detections/segmentations but the labels are incorrect. It looks like the [0-10] int labels do not match string labels in the models'
CLASSES
field here. I have tried two models:cascade_mask_rcnn_x101_32x4d_fpn_1x_nuim.py
andmask_rcnn_r101_fpn_1x_nuim.py
Unrelated: What is the reasoning to include NuImages configs in MMDetection3D instead of MMDetection? These models/configs only operate on 2D images and might be more suitable for the 2D detection repository. I am guessing this was done to reuse NuScenes files you have for 3D models. If you intend on keeping it this way, perhaps it would be good to mention this in the README so new users will use the 2D API to work with these models? As a first-time user, I initially looked into documentation for the 3D API.