-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[Docs] RTMPose3D #3167
Comments
I opened the same issue. The effort of this group is huge, however, installing and using their APIs can be a daunting experience |
Maybe I am misunderstanding you guys but isnt that the file linked in the README at the projects folder? It is a different version (the date is never at the end of the file) but it seems to be the same otherwise. The name does atleast correspont with the config file "configs/rtmw3d-l_8xb64_cocktail14-384x288.py" given in the usage example in that README. Though even with that I cant get it running sooooo. Yeah anyways, maybe it helps? Good Luck to you guys! |
@GaetanoDibenedetto I had similar issue. Can you provide me idea on solving this if you have any solutions? |
@GaetanoDibenedetto I used the provided checkpoint in project directory. Replace it in the provided command. |
How do I know which packages/versions I need of mmcv, numpy, torch, mmpose, mmengine etc...? And I have trouble with the last .pth (the checkpoint). I tried to download it from the repo from the table (the l version) and copied it into my local repo but it didnt work. |
This is what i have right now, but I have several issues with conflicting package-versions... python demo/body3d_img2pose_demo.py ^ |
@SumitxThokar Could you please explain again in more detail how to run this model? |
📚 The doc issue
In the usage section, there is a command to try the model, but there is no clear reference to where these files can be found. The file rtmdet_m_640-8xb32_coco-person.py can be easily found via a Google search, but how can the rtmw3d-l_cock14-0d4ad840_20240422.pth file be located?
Suggest a potential alternative/fix
No response
The text was updated successfully, but these errors were encountered: