Closed bheijden closed 3 years ago
This line should not explicitly reference python3 but just python. It will likely work on both melodic and noetic then (will start in python 2 in melodic and python 3 in noetic).
Edit: maybe you also need to run rosdep for moveit?
Changing to python2 seems problematic with the current implementation, as the node requires gym and is note entirely written in python2 compatible code unfortunately.
Currently, as a work around to get it working on melodic is to change the shebang in: https://github.com/eager-dev/eager/blob/0375222635b914b485b426d089498a90bbee32a4/eager_process_safe_actions/src/eager_process_safe_actions/safe_actions_node.py#L1
with python2
. This will break Noetic support so it is a hacky work around for Melodic.
Also, this requires commenting out all the gym related stuff: https://github.com/eager-dev/eager/blob/0375222635b914b485b426d089498a90bbee32a4/eager_process_safe_actions/src/eager_process_safe_actions/safe_actions.py#L4 https://github.com/eager-dev/eager/blob/0375222635b914b485b426d089498a90bbee32a4/eager_core/src/eager_core/action_processor.py#L6
and explicitly supplying the preprocessor with a new action_space, instead of inferring it from the node: https://github.com/eager-dev/eager/blob/0375222635b914b485b426d089498a90bbee32a4/examples/ur5e_example/scripts/example_custom_env.py#L24
I have the similar problem, how did you solve it? Thanks. @bheijden
When running the SafeActionsProcessor in ROS melodic (with Anaconda3 virtual env), I get the following two error messages.
The first one does not seem to be critical. Do you have this one too @jelledouwe ?
The second error message below seems to break the node. This seems to be an issue related to python3 & python2 support with ROS Melodic (related issue). @AlexanderKeijzer Do you get this error message as well (you are also using ROS melodic without having it compiled specifically with Python3 support)?
Complete terminal output