Closed xenocloud7732 closed 1 year ago
@xenocloud7732 hi, have not supported uniformerv2 based on this model list.
@RunningLeon Thank you for your answer,I did read the document before and this model is not on the support list. The recognition rate of slowfast is currently somewhat poor
@xenocloud7732 Thanks for your feedback. We may include this in future work.
This issue is closed because it has been stale for 5 days. Please open a new issue if you have similar issues or you have any new updates now.
Checklist
Describe the bug
I am trying to use mmdeploy to convert the UniFormerV2 model to Tensorrt format.The current deploy file I am using is " \configs\mmaction\video-recognition\video-recognition_3d_tensorrt_static-224x224.py" in the mmdeploy project path. The file(video-recognition_3d_tensorrt_static-224x224.py) content is as follows
The config file of the model is “uniformerv2-base-p16-res224_clip_u8_kinetics400-rgb.py ” which is included in mmaction2 project.The path is“configs\recognition\uniformerv2\uniformerv2-base-p16-res224_clip_u8_kinetics400-rgb.py ”
The ckpt file of the model is “uniformerv2-base-p16-res224_clip_8xb32-u8_kinetics400-rgb_20230313-e29fc968.pth” which is download from openmmlab.
I don't know if UniFormerV2 currently supports deployment to Tensorrt in mmdeploy.So I tried using mmdeploy for conversion, but errors( "Expected all tensors to be on the same device, but found at least two devices, cuda:0 and cpu!") were exposed during the execution process.
Reproduction
python tools/deploy.py configs/mmaction/video-recognition/video-recognition_3d_tensorrt_static-224x224.py\ F:/open-mmlab/mmaction2/configs/recognition/uniformerv2/uniformerv2-base-p16-res224_clip_u8_kinetics400-rgb.py\ uniformerv2-base-p16-res224_clip_8xb32-u8_kinetics400-rgb_20230313-e29fc968.pth\ tests/data/arm_wrestling.mp4\ --work-dir mmdeploy_models/mmaction/uniformerv2\ --device cuda\ --show\ --dump-info
Environment
Error traceback