Skip to content
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

Lidar rays as state input #45

Open
HosseinSheikhi opened this issue Jul 6, 2020 · 2 comments
Open

Lidar rays as state input #45

HosseinSheikhi opened this issue Jul 6, 2020 · 2 comments

Comments

@HosseinSheikhi
Copy link

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?

@LAXMEKS
Copy link

LAXMEKS commented Mar 6, 2021

yes i too have the same doubt.
how the vector value from lidar is considered in the input state?
here is my input state value.
Screenshot from 2021-02-27 10-22-17

@ROBOTIS-Will
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants