-
-
Notifications
You must be signed in to change notification settings - Fork 598
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
Bad result with SFM, should I mirror y coordinates? #102
Comments
Thanks for the details! I think the fact that y and z are flipped shouldn't matter, because it will just be flipped in all estimated pose matrices as well (rendering-parameters). I think this might be an issue of the range of the values in the basis, and regularisation. Can you try to set the regularisation much higher? E.g. 1000x higher? I'm planning to test the BFM soon as well (next 1-3 weeks), hopefully then I'll discover this as well and have more time to look at it. |
I meant trying different regularisation weights for the BFM. Did it fix your issues? Are you using the correspondences from ibug2did.txt for the BFM or SFM? If you're using them for the SFM, then your drawing code is incorrect, as the correspondences are correct. If you're using them with the BFM, then you of course need to adjust the mappings as the BFM has completely different vertex ids. |
It seems to me like it's working fine. Can you draw the original 68 landmarks onto the image and then the fitted model, for example with |
In the second example, you definitely have to increase the regularisation. As for the first example, I think you may need to improve your landmark-vertex mappings? Also, the input renderings, are they created using a perspective camera? As eos uses a scaled orthographic camera model for most of its algorithms, I recommend the input data is also rendered/generated under orthographic projection. |
I mean the data you're running the fitting on. If you're running it on the example images/scans included in the BFM zip file, they may (or may not) be created with a perspective camera? I'm not sure about that, but if they are, eos's scaled orthographic camera model will not be able to estimate it too well, if the perspective effect is strong. You have to keep in mind what you're doing is fitting to landmarks. The shape will naturally not be so precise, as you only fit to sparse landmarks. So the corresponding 3D vertices should fit quite precisely to the landmarks, and everything else is "approximated" from the model. |
I see . It is not good enough with landmarks only. |
It may well be! It always depends on the use case :-) |
There were probably some mistakes in the old BFM2009 to eos converter scripts. I just commited a new and tested version: 7d918d9 I'll close this, as I don't think there is a specific issue with the eos library left here. Otherwise, feel free to re-open. |
I used BFM and SFM morphable model to do shape fitting without blendshape model. All without edge constrains. The fitting results (with different weight) is too bad for eos although I tried with different shape prior weights. I might made some mistakes ,but I haven't found the bug.
I think there might be two reasons:
BTW ,both used the normalized shape basis.
BFM mean model :
v -57239.015625 42965.6875 80410.125
v -57191.5859375 42698.578125 80437.9140625
v -57140.375 42431.98828125 80463.890625
v -57090.83203125 42095.953125 80453.8359375
v -57034.40234375 41760.921875 80440.7421875
v -56967 41365.0859375 80406.1171875
SFM mean model:
v -52.30980835213897 -52.65997675631559 -70.24066997426419
v -49.95127530552107 -58.01823217565432 -74.77978278239506
v -43.17182259840274 -64.8964190446127 -64.12540017016369
v -17.51681156632089 -80.23333476491459 -36.13685001099138
What should I do with this problem? Another question: which MM model is better (more data) for SFM and BFM?
The text was updated successfully, but these errors were encountered: