-
Notifications
You must be signed in to change notification settings - Fork 32
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
unexpected output of exported torchscript on real robot #7
Comments
Sorry for the late reply. There is something wrong with the export script, we already fixed it. Please try again. And please notice that in this implementation, projected_gravity is a unit vector only indicates direction, not similar to (0,0,-9.81). Please also make sure that you do all the pre-process of observations exactly the same as compute_observations. |
Thanks for your fix.
I tried python deployment but it's too slow and only 20Hz control frequency (actually I don't know how to optimize python code). So I export ONNX model as torchcript export |
|
could you please share your deploy code ? friend. |
policy training
interation 1500
play policy in simulation
unitree go1 was walking nicely in environment.
step observation order and information
total 45 numbers
from unitree_legged_sdk
from unitree_legged_sdk
example:(0,0,9.81)
joint_pos = (joint_pos_real - default_joint_pos) * joint_pos_scale
default_joint_pos=[0.1000, 0.8000, -1.5000, -0.1000, 0.8000, -1.5000, 0.1000, 1.0000, -1.5000, -0.1000, 1.0000, -1.5000]
joint_pos_scale=1.0
joint_vel = joint_vel_real * joint_vel_scale
joint_vel_scale = 0.05
model input information
using exported torchscript.
model input tensor size : 45 * 6 = 270
6 step observations, from lastest to oldest, the first 45 values is the latest observation.
unexpected policy output
real robot condition: stand on ground and model output was not executed on real robot; velocity commands were all set to 0.
actions
increased very quickly and became very largethe following is the observations.
The text was updated successfully, but these errors were encountered: