Improbable-AI / walk-these-ways

Sim-to-real RL training and deployment tools for the Unitree Go1 robot.
https://gmargo11.github.io/walk-these-ways/
Other
492 stars 129 forks source link

Fix required package versions of `params_proto` and `numpy`. #6

Closed Weizhe-Chen closed 1 year ago

Weizhe-Chen commented 1 year ago

Dear Gabriel,

I just wanted to express my gratitude for your wonderful library. Kudos to your great work!

I encountered a couple of issues while running python scripts/test.py after following the instructions for installation. Specifically, I received the following errors:

  1. ImportError: cannot import name 'PrefixProto' from 'params_proto'.
  2. AttributeError: module 'numpy' has no attribute 'float'.

I was able to resolve these issues by upgrading params_proto and downgrading numpy with the following commands:

  1. pip install --upgrade params_proto.
  2. pip install "numpy<1.24".

It might be helpful to include the specific versions of these packages, as well as the Python version, in the setup.py file to prevent similar issues for other users.

Sincerely, Weizhe

Weizhe-Chen commented 1 year ago

Actually I need to install this specific version: pip install "params_proto==2.10.0"

gmargo11 commented 1 year ago

I'm glad you like the library, Weizhe!

Thank you for letting me know about the dependency issue. I've updated the versions of some packages and added numpy as a dependency in new commit b912dac. These new versions seem to work for me, but do let me know if you still run into an error.

Best, Gabe

Weizhe-Chen commented 1 year ago

Hi Gabe,

Thank you for the update! The new setup.py file has the following conflicting dependencies.

ERROR: Cannot install go1-gym because these package versions have conflicting dependencies.

The conflict is caused by:
    gym 0.14.0 depends on cloudpickle~=1.2.0
    jaynes 0.9.2 depends on cloudpickle==1.3.0

To fix this you could try to:
1. loosen the range of package versions you've specified
2. remove package versions to allow pip attempt to solve the dependency conflict

Best, Weizhe

Weizhe-Chen commented 1 year ago

Relaxing the range of package versions can solve this issue:

'jaynes>=0.9.2',
'gym>=0.14.0',