You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have encountered an issue with the exported skeleton model where the model segments appear to intersect. The involved program components are register_star, infer_skeleton, and pose_skeleton.
I'm considering a potential workaround and need some guidance: Is it possible to manually edit the skeleton model to resolve the intersection problem and then use this modified model as an input for the pose_skeleton function? Would this approach create any unforeseen issues? Looking forward to your insights.
The text was updated successfully, but these errors were encountered:
We don't have a loss to avoid those specific interpenetrations. You could edit the final skeleton mesh to correct for those interpenetrations.
If you edit the lying down inferred skeleton before reposing, it should help for the spine, but no guarranty that the scapula will not intersect with the thorax at all after reposing.
I think a way to do would be to add a loss to avoid interpenetration between the scapula and the thorax by fitting ellipsoids to them.
Can you specify what you mean with "Not in the correct position" ?
We do have light interpenetrations between the ribs and the skin in some poses as our rib cage is rigid.
For T12 and Rib 12, their relative position is the one that was in the template we used from Anatomy Transfer.
I have encountered an issue with the exported skeleton model where the model segments appear to intersect. The involved program components are register_star, infer_skeleton, and pose_skeleton.
I'm considering a potential workaround and need some guidance: Is it possible to manually edit the skeleton model to resolve the intersection problem and then use this modified model as an input for the pose_skeleton function? Would this approach create any unforeseen issues? Looking forward to your insights.
The text was updated successfully, but these errors were encountered: