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 found the state (the input to the deep-Q network) in the ROS2 version weird and confusing. As the documentation says and what is implemented in ROS 1 versions, the state supposed to be a vector by size 26 including 24 rays of lidar. However, in the ROS2 implementation, just min range and arg min of the lidar are extracted and the state is just a vector by size 4! Could you please explain what is going on?
The text was updated successfully, but these errors were encountered:
Sorry about the discrepancy between the eManual descriptions and the ROS2 source code.
The ROS2 code had been modified to use the distance and angle of the goal position, and those of the nearest obstacle (from the scan data) as an input state o.
I'm currently reviewing the machine learning code as well as the documentations.
Thank you.
I found the state (the input to the deep-Q network) in the ROS2 version weird and confusing. As the documentation says and what is implemented in ROS 1 versions, the state supposed to be a vector by size 26 including 24 rays of lidar. However, in the ROS2 implementation, just min range and arg min of the lidar are extracted and the state is just a vector by size 4! Could you please explain what is going on?
The text was updated successfully, but these errors were encountered: