Same MMPose/MMDeploy setup in two locations, one works, one fails. #2414
Unanswered
korneliaWatson
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I'm training MMPose on a custom keypoint detection task. I have repository setup in two locations, let's call them location A (with GPU) and location B (without GPU).
Codebase and mm* dependencies are exactly the same in both locations.
However,
KeyError: 'CocoPersonFront is not in the mmpose::dataset registry. Please check whether the value of
CocoPersonFrontis correct or it was registered as expected. More details can be found at https://mmengine.readthedocs.io/en/latest/advanced_tutorials/config.html#import-the-custom-module'
.I compared all modified files and they are exactly the same (I use a script to perform changes so they should be the same). I can't figure out why location B errors.
Another problem I have been experiencing...
As I managed to train a model in location A, I wanted to prepare a separate inference script with the use of MMDeploy, as per example here.
In location A, my inference script works.
In location B, I get the following error:
I looked at
meta_data
variable, and in location A it is present, in location B it is indeedNone
.I begin to think that this variable is linked to the training process as the only difference between location A and location B is that I managed to train a model in location A but not in B. Is that the case? If so, it would suggest that it is not possible to decouple mmpose such that inference can be done without processes done for and during model training?
Beta Was this translation helpful? Give feedback.
All reactions