-
Notifications
You must be signed in to change notification settings - Fork 12
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
question: how to run on custom data? #6
Comments
Hi, the model is subject-specific, e.g. the pre-trained skirt model will always generate skirt results in the given pose. So yes you need to retrain on the new data. Please refer to the |
@qianlim If I have a single pair of clothed mesh and its corresponding fitted unclothed SMPL mesh, can I then train the model with this single sample and can it generalize well to any unseen pose of the same SMPL and gives clothing deformations as per the same clothed mesh used in training? In short, is training using a single pose sufficient to generalize well on various unseen poses? If not, then what is the recommended amount of training, testing & validation samples required to yield a good model? |
Hi, training on a single pose won't make the model generalizable to unseen poses (as in this case the model doesn't have the knowledge how the shape should deform as the pose changes). The number of train/test examples we used in the paper depends on each outfit type in the CAPE data, but in general they are in the order of ~10^3 training frames that covers a sufficient amount of different poses (see the paper appendix A.3). |
hello, I have a custom clothed mesh and a fitted SMPL model of this mesh. I now want to generate the animations as shown in the example on this custom mesh. Should I retrain the model to work on this new data? If so how(the demo contains multiple npz files in test, train, and val but I have only one)? or Can I use the pre-trained model to run on custom meshes and generate the desired clothed animations. Thank you in advance
The text was updated successfully, but these errors were encountered: