Update README.md
Browse files
README.md
CHANGED
@@ -4,6 +4,8 @@ license: bsd-3-clause-clear
|
|
4 |
|
5 |
# LAFAN1 Retargeting Dataset
|
6 |
|
|
|
|
|
7 |
To make the motion of humanoid robots more natural, we redirected [LAFAN1](https://github.com/ubisoft/ubisoft-laforge-animation-dataset) motion capture data to [Unitree](https://www.unitree.com/)'s humanoid robots, supporting three models: [H1, H1_2](https://www.unitree.com/h1), and [G1](https://www.unitree.com/g1). This redirection was achieved through numerical optimization based on [Interaction Mesh](https://ieeexplore.ieee.org/document/6651585) and IK, considering end-effector pose constraints, as well as joint position and velocity constraints, to prevent foot slippage. It is important to note that the redirection only accounted for kinematic constraints and did not include dynamic constraints or actuator limitations. As a result, the robot cannot perfectly execute the redirected trajectories.
|
8 |
|
9 |
This database stores the redirected trajectories in CSV format. Each row in the CSV file corresponds to the original motion capture data for each frame, recording the configurations of all joints in the humanoid robot in the following order:
|
|
|
4 |
|
5 |
# LAFAN1 Retargeting Dataset
|
6 |
|
7 |
+
<video controls autoplay src="https://cdn-uploads.huggingface.co/production/uploads/67639932ad38702e6c8d16d9/V7InyG4CAh5NhUXILTK9b.mp4"></video>
|
8 |
+
|
9 |
To make the motion of humanoid robots more natural, we redirected [LAFAN1](https://github.com/ubisoft/ubisoft-laforge-animation-dataset) motion capture data to [Unitree](https://www.unitree.com/)'s humanoid robots, supporting three models: [H1, H1_2](https://www.unitree.com/h1), and [G1](https://www.unitree.com/g1). This redirection was achieved through numerical optimization based on [Interaction Mesh](https://ieeexplore.ieee.org/document/6651585) and IK, considering end-effector pose constraints, as well as joint position and velocity constraints, to prevent foot slippage. It is important to note that the redirection only accounted for kinematic constraints and did not include dynamic constraints or actuator limitations. As a result, the robot cannot perfectly execute the redirected trajectories.
|
10 |
|
11 |
This database stores the redirected trajectories in CSV format. Each row in the CSV file corresponds to the original motion capture data for each frame, recording the configurations of all joints in the humanoid robot in the following order:
|